Throughout the year, and especially at audit time, security and IT operations staff have to jump through hoops to make sure they are collecting evidence, performing to established procedures, on top of their day to day firefighting and project work. All in the name of "Compliance" routines. For what? To pass an audit? In the rush to get this evidence collected and abide by the "documented procedures", what is getting missed or isn't getting done? What is the cost to your operations and hence, your bottom line? What is the cost to your overall security posture?
So how can you keep ahead of the changing compliance landscape, avoid all of this running around to meet "compliance", operate in a cost effective manner, and still manage adequate and effective information security controls?
Here are some thoughts:
Build a security program whose output is compliance.
This is a fundamental and is essential. If you develop a strong security program from the top down, you can easily map compliance requirements to that security framework. This includes the "tone at the top" management commitment to an information security program. Clear directives in the form of information security policies establish the security direction for everyone in the organization. Establishing these mandates within an organization will get everyone headed in the right direction, and get them out of the "run around, the auditor's here" mindset. It just becomes part of the way you do business.
Develop your security program around a control framework suitable for your organization.
There are several choices here, and you don't have to reinvent the wheel. NIST SP800-30, ITIL, COBIT, and other IT control frameworks can all be customized to fit your specific needs, industry, and security program maturity. Don't be afraid of adjusting them to be user-friendly in your environment. Creating a solid way of tracking your security controls will pay off big dividends in the long run. Without an adequate way of tracking your security (and IT) controls, you really don't have the clarity of what controls you have in place, and perhaps more importantly, why you have them in the first place.
Map security controls within your control framework to (fill in the blank here) compliance requirements.
This is the biggie. By tying in your security control activities to compliance requirements, you should be able to effectively address any compliance requirement that comes up. And when those change, or new ones are added, guess what? All you have to do is update your framework. Sure, there may be adjustments to policies, procedures, etc, but those are manageable. If you already have a control in place that wasn't previously covered by the compliance requirement, great! You've already been doing that control activity, so just update the framework to include the new compliance mappings.
If you don't know where you are going, any road will get you there.
Get help. Seriously, if you don't know where you are, where you are going, or how to get there, get help. Critical Assets, for example, can help you with all of the above and much more. Our security professionals have years of experience in a wide variety of vertical markets and industries. We can help.