Managing Policy Exceptions and Compensating Controls

CISM · Information Security Program · By Super Admin

Learn how organizations handle exceptions to security policies and use compensating controls to manage risk when standard requirements cannot be met.

The Need for Exception Processes in Security Frameworks

When adopting new security policies, standards, and procedures, organizations should also provide a mechanism for exceptions to those rules. Inevitably, unforeseen circumstances will arise that require a deviation from the requirements. The policy framework should lay out the specific requirements for receiving an exception and the individual or committee with the authority to approve exceptions. Without a formal exception process, organizations risk either rigidly applying requirements in situations where they are impractical or allowing informal, undocumented deviations that create unmanaged risk.

The state of Washington uses an exception process that requires the requestor to document several specific items: the standard or requirement that requires an exception, the reason for noncompliance with the requirement, the business and/or technical justification for the exception, the scope and duration of the exception, the risks associated with the exception, a description of any supplemental controls that mitigate the risks associated with the exception, a plan for achieving compliance, and identification of any unmitigated risks. This comprehensive documentation requirement ensures that exceptions are granted deliberately and with full awareness of the associated risks.

Compensating Controls: An Alternative Path to Risk Management

Many exception processes require the use of compensating controls to mitigate the risk associated with exceptions to security standards. The Payment Card Industry Data Security Standard (PCI DSS) includes one of the most formal compensating control processes in use today. PCI DSS sets out three criteria that must be met for a compensating control to be satisfactory: the control must meet the intent and rigor of the original requirement; the control must provide a similar level of defense as the original requirement such that the compensating control sufficiently offsets the risk that the original PCI DSS requirement was designed to defend against; and the control must be "above and beyond" other PCI DSS requirements.

The general idea is that a compensating control finds alternative means to achieve an objective when the organization cannot meet the original control requirement. Although PCI DSS offers a very formal process for compensating controls, the use of compensating controls is a common strategy in many different organizations, even those not subject to PCI DSS. Compensating controls balance the fact that it simply is not possible to implement every required security control in every circumstance with the desire to manage risk to the greatest feasible degree.

Practical Application and Remediation Planning

A practical example of a compensating control involves an organization that needs to run an outdated version of an operating system on a specific machine because software necessary to run the business will only function on that operating system version. Most security policies would prohibit using the outdated operating system because it might be susceptible to security vulnerabilities. The organization could choose to run this system on an isolated network with either very little or no access to other systems as a compensating control.

In many cases, organizations adopt compensating controls to address a temporary exception to a security requirement. In those cases, the organization should also develop remediation plans designed to bring the organization back into compliance with the letter and intent of the original control. This combination of a formal exception process, documented compensating controls, and a remediation plan provides a structured approach to managing situations where full compliance is temporarily or permanently impractical.

Key takeaways

  • The policy framework should lay out specific requirements for receiving an exception and the individual or committee with authority to approve exceptions.
  • PCI DSS requires that compensating controls meet the intent and rigor of the original requirement and be above and beyond other PCI DSS requirements.
  • Organizations adopting compensating controls for temporary exceptions should also develop remediation plans to return to compliance.
0.0 (0 ratings)

Discussion (0)

No discussion on this article yet — be the first to comment.

Please sign in to join the discussion.