On a scale of 1-5, how would you rate your organization’s ability to successfully protect your organization's operational network (OT) and IT network from a cyber attack?

Security & GRCCrisis Management

1. We are not at all prepared.3%

2. We are somewhat prepared.35%

3. We are moderately prepared.21%

4. We are generally prepared.33%

5. We are highly prepared.6%

348 PARTICIPANTS
3.3k viewscircle icon3 Upvotescircle icon3 Comments
Sort by:
VP of Technologya year ago

I think this is one of those questions where answering the question alone, is like challenging the criminal hacking world to give your IT/OT a try. Most of the information one needs to start is associated right here with your answers and your user profile.

VP, Director of Cyber Incident Response in Finance (non-banking)4 years ago

While we might consider ourselves highly prepared, we don't for a minute think that we're immune.

Lightbulb on3
Vice President of Information and Security in Manufacturing4 years ago

As prepared we are today, we need to make sure we are also prepared for what's come tomorrow. We want to have all the tools available for Zero-Day Attacks but that's where our remediation plan comes in.

Lightbulb on2

Content you might like

What are the biggest technical challenges preventing organizations from being able to use their existing data to enable digital transformation?

Finding data and putting it to good use13%

Controlling the security and privacy of data45%

Understanding how data is currently being used20%

All of the above19%

None of the above1%

View Results

Has cryptocurrency helped to facilitate the ransomware market?

Yes80%

No15%

Unsure4%

View Results

Which cybersecurity metrics do you currently use with your board?

Read More Comments

What do you do to recover quickly from early missteps in a new role? How can you keep initial mistakes from coloring perceptions when you’re still trying to establish your reputation at a new organization?

Does someone have advice on how they have balanced the risk/reward as it relates to introducing Open-Source Software to organization? My org is dipping its toe into the OSS world and the architecture and risk governance teams are looking to get ahead of these requests by coming up with policies and standards for OSS technology being brought into our environment. To clarify, this is not for software development and CI/CD pipelines, SDLC etc. This is for installing solutions that already exist out there (Zabbix, GreyLog, Prometheus etc.) into the organization's environment. We are looking to provide a balance on the obvious risk with the ability to move fast (like everyone else now).