Week 10 CYBR 650 Blog
Action Plans
This week I finished up creating my Action Plan for the
Harry and Mae case study in my Current Trends in Cybersecurity course. This is
the culmination of many weeks analyzing assets, threats, and vulnerabilities
for the simulated enterprise. We delivered an action plan, detailing the steps
recommended to fix some of the vulnerabilities. As I was detailing these steps
I realized how incredibly complex and difficult some of these actions actually
are. For academic purposes, some of this information can be handwaved as we are
understanding the process, not necessarily all of the project management
projection of some of these tasks we were detailing.
For example, recommending that an organization move from no
password policy to two-factor authentication briefs very well, but it can be
incredibly complex, expensive, and time consuming. At many points during the
drafting of the Action Plan I felt like the employee in the above Dilbert
cartoon.
Deeper Analysis of
Recommendations
An action plan has to take more into account that the “most
secure” solution. Can the company afford the initial cost and time delay? Can
the technically execute the upgrade, and most importantly, can they sustain
operations once the system is fielded? The action plan should be robust and
answer these types of questions, or at least hint that they need answering. You
might have to recommend that they look at hiring additional staff, maybe even
detail the specifics required. So, in essence an action plan might recommend
many courses of action for each risk or way forward. Instead of the most secure
solution and nothing else, maybe give the most secure, the most bang for their
buck, and maybe a middle road solution - one that balances overall security
with other factors for the organization you are analyzing.
| https://searchnetworking.techtarget.com/photostory/4500267797/Five-essential-network-security-topics-and-trends-to-watch/3/Most-end-users-would-bypass-IT-security-policies-they-dislike |
I know it’s almost sacrilegious to say this, but maybe the
most secure solution isn’t always the best. Over complicating systems above the skill levels of the staff they hired may be even
worse than doing nothing. Once security becomes too complicated or overwhelming
users seek ways to work around it…thus negating the controls you put in place
and opening up completely new unassessed risks.
Comments
Post a Comment