A.5 Organizational controls

A.5.36 Compliance with policies, rules and standards for information security

Not mandatory by default – decided in your SoA

What it means in plain language

Regularly check that your own policies, rules and standards are actually being followed.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

An organisation can have well-written policies while everyday configurations and work practices contradict them. Compliance checks identify that gap before a customer review, incident or independent audit exposes it. Their value comes from testing specific internal rules against actual behaviour, distinguishing approved exceptions from unmanaged departures, and ensuring the people responsible for operations address the findings rather than merely acknowledge them.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Managers attest that their teams comply with policy without examining a sample of access decisions, system settings or other relevant operating evidence.
  • Technical compliance scans produce repeated failures, but no process assigns ownership or confirms that corrective changes resolve the underlying deviation.
  • An exception has no expiry, scope or accountable approver, making it impossible to distinguish accepted temporary deviation from a permanently ignored rule.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Translate the most significant policies into checkable criteria with the relevant operational owners. Identify evidence sources and sampling methods appropriate to each rule. For example, compare a password configuration with the approved authentication standard rather than asking whether a policy exists.
  • Schedule checks according to exposure, recent changes and previous failures. Combine technical assessments with process sampling and staff discussion where automation cannot show the full picture. Record the period and scope examined so a small sample is not presented as universal assurance.
  • Log deviations with the policy reference, observed condition, affected scope and owner. Decide whether immediate correction, risk acceptance or a corrective-action investigation is needed. Escalate unresolved material issues through management rather than repeatedly reporting the same red status without a decision.
  • Verify closure using fresh evidence from the affected process or system. Review whether repeated deviations indicate an unrealistic rule, insufficient training or a wider control failure. Keep policy changes controlled; weakening a rule solely to clear a finding is not evidence of effective risk management.

What an auditor will ask to see

  • A policy-compliance review plan with defined criteria, responsible reviewers and a risk-based rationale for the frequency and scope of technical and procedural checks.
  • Completed samples or configuration comparisons showing what was examined, the observed result, identified deviations and the limits of the assessment performed.
  • A traceable issue and exception record linking policy departures to approved decisions, corrective work, follow-up testing and escalation of unresolved significant exposure.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.36. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with 9.2 — Internal audit and 10.2 — Nonconformity and corrective action. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.