ISO 27001:2022 Annex A 5.37 – Documented Operating Procedures Explained

Security breaks down when critical tasks rely on memory, habit, or assumption.

Annex A 5.37 exists to ensure organisations document operating procedures for information security–relevant activities, so tasks are performed consistently, securely, and reliably, regardless of who carries them out or how often they occur.

This control is about operational discipline, not bureaucracy.

ISO 27001

Quick Guide: Annex A 5.37 at a Glance

Annex A 5.37 of ISO 27001:2022 focuses on documented operating procedures for information security.

At a practical level, this means:

  • Documenting how security-relevant activities are performed
  • Ensuring procedures are available to those who need them
  • Supporting consistent execution of tasks
  • Reducing reliance on individual knowledge or memory
  • Maintaining security during routine and non-routine operations

The control does not require every activity to be documented. It expects procedures where consistency, security, or risk justify it.

In-Depth Guide to Annex A 5.37

What Is Annex A 5.37 and Why Does It Matter?

Information security is delivered through day-to-day operations.

Many incidents occur because:

  • Tasks are performed differently by different people
  • Infrequent activities are forgotten or improvised
  • Knowledge exists only with individuals
  • Responsibility changes without proper handover

Annex A 5.37 ensures that critical and sensitive activities are:

  • Repeatable
  • Understandable
  • Transferable
  • Less dependent on individual experience

This control applies to operational activities, not just technical ones.

When Documented Operating Procedures Are Appropriate

Documented procedures are particularly valuable when:

  • An activity is performed by multiple people in the same way
  • An activity is performed infrequently
  • There is a risk of steps being forgotten
  • New or unfamiliar activities are introduced
  • Responsibility is transferred between individuals or teams
  • Errors could have security, operational, or compliance impact

The intent is to reduce variability where variability introduces risk.

How to Implement Annex A 5.37 Effectively

A  pragmatic approach to Annex A 5.37 typically includes the following elements.

1. Identify Activities That Require Procedures

Organisations should identify activities that:

  • Affect information security
  • Require consistent execution
  • Carry higher risk if performed incorrectly

Not all tasks need procedures, focus on those that matter.

2. Define Responsibilities Clearly

Procedures should clearly state:

  • Who performs the activity
  • Who is accountable
  • Who provides support or escalation

Clarity reduces hesitation and error during execution.

3. Describe Activities Clearly and Practically

Effective procedures typically cover:

  • What needs to be done
  • When it needs to be done
  • How it should be done
  • What security considerations apply

Procedures should be usable under real operational conditions, not written solely for audit.

4. Address Security During System and Process Changes

Where procedures relate to systems, they often include guidance for:

  • Secure installation and configuration
  • Change handling
  • Maintaining security during maintenance

Operational changes are common sources of security weakness.

5. Consider Error Handling and Exceptional Scenarios

Procedures should address:

  • What to do when things go wrong
  • How to handle errors or unexpected outcomes
  • When and how to escalate issues

Exception handling prevents panic-driven decisions.

6. Integrate Continuity and Recovery Considerations

Where relevant, procedures may reference:

  • Backup, recovery, or restoration steps
  • Dependencies on other systems or services
  • Contacts and escalation during disruption

This supports resilience during abnormal conditions.

7. Maintain and Review Procedures

Procedures should be:

  • Reviewed periodically
  • Updated when systems or processes change
  • Approved by appropriate management

Outdated procedures are often worse than none at all.

Practical Considerations

Annex A 5.37 does not require:

  • Lengthy or complex documents
  • Highly technical language for every audience
  • Centralised procedures for all activities

It does expect procedures to be:

  • Appropriate to the task
  • Accessible to those who need them
  • Maintained as part of normal operations

Good procedures support people, they do not replace judgement.

Common Challenges and How to Overcome Them

  • Documenting everything without prioritisation
  • Focus on activities where consistency and security matter
  • Procedures written but not used
  • Ensure procedures are practical and accessible
  • Outdated procedures causing confusion
  • Review and update when change occurs
  • Reliance on individual knowledge
  • Use procedures to support handover and resilience

Operational risk increases when knowledge is informal.

Final Recommendations

Annex A 5.37 is about making secure operations repeatable.

When documented operating procedures are applied effectively:

  • Security becomes consistent
  • Errors are reduced
  • Knowledge is retained during staff change
  • Operations remain reliable under pressure

People deliver security.
Annex A 5.37 ensures they are supported by clarity, not memory.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls