By Diana Kelley, Burton Group Analyst
Compliance tools purport to present a snapshot of a company's current state of compliance with a variety of different regulations. Keep in mind, however, that much of the legislation pertains to appropriate risk management and business controls; not to prescriptive security settings on systems.
The lack of prescription means that companies must perform risk analysis and create their own prescriptive guidance. Reading through the actual requirements is a great place to start. Commonly-accepted control frameworks, such as COSO, CobiT, ISO 17799 and ITIL, can also be referenced as a starting point from which the key stakeholders -- executives, auditors, IT administrative staff and any other employees involved in the compliance process -- can obtain guidance and insight.
If your enterprise is planning to use a vendor-supplied template for compliance reporting, ask the vendor how the compliance policies were created and how easy it is to customize them. Because regulations aren't prescriptive, most vendors use one of the control frameworks mentioned above as a baseline for the compliance templates. They may even augment the template with information from lawyers, auditors and customers. These templates can be a great guide, but don't rely on them out of the box, even if the template is quite detailed and based on an accepted framework. It will need additional tuning from your IT and security staff.
Bottom line: proceed with caution. If the tuning work isn't done upfront, dashboards can quickly become "garbage in/garbage out."
|