Cylance Strengthens Executive Team with New CIO, CMO and CPO

Cylance is pleased to announce the appointment of Grant Johnson as Chief Marketing Officer (CMO) and Kumud Kalia as Chief Information Officer (CIO). The company also promoted Eric Cornelius to Chief Product Officer (CPO).

Johnson and Kalia bring decades of leadership experience at global enterprise technology organizations. Cornelius has over a decade of experience as a trusted security practitioner and product builder.

“Cylance’s long-term vision to protect every person and device is only possible if we continue to bolster a best-in-class leadership team,” said Stuart McClure, Chairman and CEO at Cylance.

“Grant and Kumud bring a stellar track record of executive leadership and the expertise required to propel our mission and build on our proven strategy. Not only are the new executives critical to our success, we are also recognizing Eric’s exemplary product and innovation leadership. Today, our executive team is stronger than ever as we establish Cylance as the global leader in endpoint protection.”

As CMO, Johnson will lead Cylance’s global marketing strategy and execution, reporting to Daniel Doimo, President and COO. Previously, Johnson was CMO at Kofax, a robotic process automation company. Johnson led Kofax’s marketing efforts during its growth from a private company through its IPO on Nasdaq and a rollup and integration of a $700 million software portfolio.

During his extensive career, Johnson also held senior marketing roles at Pegasystems, Guidance Software, FileNet Corporation, FrontBridge and Symantec and developed substantial expertise in global market expansion, product line extension and customer acquisition to help drive rapid revenue growth.

“Cylance’s commitment to protecting every endpoint from the most advanced threats is redefining cybersecurity across every vertical,” Johnson said. “As Cylance emerges as the global leader in endpoint protection, I am excited to help drive the next phase of Cylance’s growth.”

As CIO, Kalia will be responsible (Read more...)

*** This is a Security Bloggers Network syndicated blog from Cylance Blog authored by The Cylance Team. Read the original post at: