It’s all Greek to me!

Breaches begin with people, not protocols.

We’ve all been there. You’re sitting in a meeting or talking with your IT Director and you’re smacked in the face with technical jargon and cybersecurity language. Unless you work in IT or the cyber market, you probably stare and nod in agreement as your eyes glaze over with thoughts of lunch.

Truth is, though we all need to be aware of and apply cybersecurity protocols, not everyone needs to take a deep dive into its dark corners. Effective communication via a common language makes it easier for the individual to understand and implement these practices. Let’s be honest: we are much more likely to obey rules when we understand them and how they benefit us.

Most C-level officers don’t have the time or inclination to study cybersecurity and they don’t want to wade through the techy talk. Naturally, they understand the importance of safeguarding their investments, but need information presented using a language they understand: business. Cyber professionals need to express cybersecurity concerns in terms of business risks, priorities, and investments – not technologies.

Safety concept: Closed Padlock on digital background

Even some of the smartest and best equipped corporate officers don’t understand the full impact of cybersecurity issues, much less how to fix them. They need a clear presentation of the business impacts of cyber risks. Common language is key to embedding cybersecurity into organization culture, but it’s not all on the IT Department. As much as IT professionals need to tailor their message to the person, the individual needs to ask questions. Effective communication keeps our servers secure and you out of the land of alphabet soup.

AUTHOR: NED MERRILL (FRM. VICE PRESIDENT AND DIRECTOR OF PROPOSALS)

Edward (Ned) Merrill joined Edwards in 2014 as Vice President of Solutions and Director of Proposals. In this position, Ned is directly responsible for solutioning across the Edwards’ four Strategic Business Units and proposal activities. He is accountable for Lean/Agile management, as well as the development and implementation of the Edwards’ Agile Portfolio Methodology.