What is the most overlooked step in a cybersecurity plan?

3.3k viewscircle icon1 Upvotecircle icon8 Comments
Sort by:
Senior Information Security Manager in Software4 years ago

Testing, and that the plan must be regularly updated.
Regularly could mean quarterly or more often.

Lightbulb on3
Director of Technology in Government4 years ago

Overlooking physical security in your CyberSecurity plan could leave a major gap in your CyberSecurity posture.

Lightbulb on1
CIO / Managing Partner in Manufacturing5 years ago

Getting senior executives fully on board and understanding it.

Fractional CIO in Services (non-Government)5 years ago

Communicating it in a way that makes sense to your people.

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

This is an excellent question.  I think it's the maintenance of the plan itself.  Because even if you document the plan, and the processes to address the response, each security incident is unique enough that it will require you to update the processes involved.  So the moment you publish your plan, it's already out of date!

1 Reply
no title4 years ago

Absolutely. I would say actually following it, and keeping it up to date and current, are the biggest challenges. Too many organizations create a plan, the stick it on a shelf until the next annual audit rolls around. It does you no good if you don't actually follow through from the plan.

Lightbulb on2

Content you might like

Always required – Security must formally review and approve every change request.

Required for security-impacting changes – Security reviews only changes flagged as having potential security implications. Please comment : Who decides which changes require security review and which do not ? Is this determination manual or automated? How do you avoid gaps or oversights in this process ?100%

Not required – Security does not review changes submitted CAB/RAB by other teams.

Risk-based or automated – Security involvement is determined by a tiered model or automated risk scoring within ITSM.

View Results

Strongly agree11%

Agree69%

Neutral14%

Disagree3%

Strongly disagree

View Results