A.5 Organizational controls

A.5.37 Documented operating procedures

Not mandatory by default – decided in your SoA

What it means in plain language

Document operating procedures for IT and security tasks and make them available to the people who need them.

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

Critical operational knowledge is fragile when it depends on one experienced administrator remembering the right sequence. Documented procedures make tasks repeatable and help deputies recover services without improvising under pressure. Their value depends on matching the real environment, explaining safety checks and escalation points, and being accessible during the conditions in which the procedure is most likely to be needed.

Common auditor findings to check for

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

  • A recovery runbook references retired systems or unavailable credentials, and nobody has tested whether a deputy could follow the documented steps.
  • A high-impact routine such as account provisioning depends on personal notes without controlled approval, version history or a defined escalation route.
  • The procedure lists commands but omits prerequisites, expected results and stop conditions, leaving an operator unable to identify an unsafe deviation.

How you can implement it

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

  • Identify recurring or high-impact tasks that need written instructions, prioritising those involving sensitive information, service availability or limited staff coverage. Assign a procedure owner and establish the level of detail needed by a suitably competent deputy, not only the original author.
  • Write instructions with prerequisites, dependencies, safety checks, expected outcomes and recovery or escalation steps. Keep secrets outside the runbook and reference an approved access mechanism. Explain when the operator must stop and seek approval rather than continue through an unexpected result.
  • Validate the procedure through a supervised walkthrough or controlled exercise by someone other than its author. Record ambiguous steps, missing access and environmental differences. Update the document and retain the test outcome so approval reflects practical usability rather than formatting alone.
  • Link updates to relevant system and process changes, and make the current procedure available where operators need it. For outage or emergency tasks, assess access when the normal document platform is unavailable. Retire obsolete copies while preserving the required history of previous instructions.

What an auditor will ask to see

  • Approved operating procedures for selected high-impact tasks, including ownership, prerequisites, expected outcomes, escalation contacts and controls on privileged or sensitive actions.
  • A deputy walkthrough or exercise record showing that the instructions can be followed in the real environment and identifying how discovered gaps were resolved.
  • Change-linked review history and access arrangements demonstrating that operators can obtain the current runbook, including during loss of normal collaboration or identity services.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with 7.5 — Documented information and A.8.32 — Change management. 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.