I worked for a consulting company specializing in Security Training and Consulting practice for Fortune 100 companies. Our motto is “The Best Defense is Good Practice”. The old adage “practices make perfect” rings especially true in the security field. There are always going to be security vulnerabilities and exploits, we can never patch all the holes. However, if we have a well defined security process as the starting point (good practice), we can continue to practice and improve our security posture against new challenges (best defense).
Once we’ve recognized the need to integrate security process as part of the strategic IT goals, we need to ensure that we can break down that top level strategic goals into tactical and operational goals. These goals will need to be clearly defined and aligned to business goals. In my opinion, this is a CTQ (Six Sigma Concept – Critical To Quality) milestone because we need the ability to measure ROI on security process and security service delivery to our management and business units. This is where ITIL and other related frameworks can help. At minimal, these best practice guidelines have a defined process of enumerating metrics associated with delivering an IT service. After all, if we don’t know what we have and what processes are involved, how are we to measure and monitor our progress?
When we have defined the security metrics, we can measure and present ROI analysis more readily to the management. After all, companies are in the business of making money and having numbers and stats will significantly increased our chance of getting the C-level sponsorship and budget $$ we need to implement the security controls.
In my experience, to gain management buy-in/budget is often the longest phase of the security project life cycle. It is a daunting process and we (IT security practitioners) need to get better at making the business value proposition.
Once I’ve conquered the management buy-in/budget phase, I can be assured that I will have the appropriate resource to follow our defined security process and to implement the project the ‘right’ way. Otherwise, I often found myself and my team taking shortcuts in our own security process just to meet the resource constraint. In every project that I had worked on, I always remind myself and often repeat these four words: PLAN, DO, CHECK, ACT (The Deming Cycle).
The other benefits for getting the management buy-in as part of the security process is the accountability and cooperation. Once management has approved the project charter, they are ultimately accountable for the success of the project. It is at the best interest of the entire organization to see the project succeed. The motivation and cooperation for both IT and non-IT in this kind of environment is dramatically different when everyone cares about the project.
I’ve been in projects where everyone is excited about the new security process and the associated changes such as new record retention policy and log management requirements when we have the blessing and $$ to properly reward users for doing the right thing. On the flip side, the consequence for non-compliance is more effective coming from the top management team.
In conclusion, in my opinion, for an organization to assimilate security process as part of their corporate DNA will require security practitioners to spend more time in front of the board room than in the computer room.
Concepts mentioned & websites:
Make sure you visit our main site.
Share This