ISO 27001 Annex A 5.37 Documented operating procedures for information processing
What it says
Operating procedures for information processing facilities shall be documented and made available to personnel who need them.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishEnsure procedures are written down and accessible to those who need them.
Imagine running a business where no one knows exactly how to do their job because the instructions aren't written down. This control is basically saying: 'Let's not leave things to chance!' By documenting how information is processed, you ensure everyone knows what to do and how to do it, reducing mistakes and making sure everything runs smoothly.
Free. Save your status, tasks and notes.
Why it matters
Without documented operating procedures, staff run processing tasks inconsistently, increasing outages, data handling errors and inability to repeat or audit processing steps.
How to implement
The IT manager should take the lead in documenting procedures for all key information processing activities.
They can start by listing frequent, rare, and new activities, ensuring every procedure is written down so it can be consistently followed.
HR should ensure that new staff receive and understand these documented procedures as part of their onboarding process.
This can be done by integrating these procedures into training sessions and making sure they're easily accessible.
Department heads should be responsible for keeping procedure documents up-to-date and relevant.
They can do this by regularly reviewing the procedures, especially after changes in systems or regulations, to ensure they remain accurate.
An operations manager should oversee the secure handling and storage of these documents.
This includes setting up a digital library that is backed up regularly, ensuring easy access for authorised personnel only, aligned with the ASD Essential Eight.
The compliance officer should verify that procedures include specific details like handling errors and correct sequences of tasks.
They can do this by cross-referencing the procedures with actual practices, ensuring compliance with the Australian Privacy Act 1988.
Keep it running
Maintain version-controlled operating procedures for each processing facility; assign owners, review after changes/incidents, and publish them where relevant staff can easily access.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The documented operating procedures for all key information processing activities.
Look at
Whether each procedure is clearly written, relevant, and accessible to required personnel.
Good evidence
A comprehensive set of current documents available to everyone who needs them.
- Check 2 of 5What an auditor asks for
Ask for
Records of when procedures were last reviewed and updated.
Look at
Timestamps and authorisation signatures on these records to see if reviews occur regularly. GOOD means procedures are reviewed regularly, and any updates are well-documented and authorised.
- Check 3 of 5What an auditor asks for
Ask for
To see training records for new staff on these procedures.
Look at
Whether there is evidence that all relevant personnel received proper training. GOOD will have everyone equipped with what they need to follow the procedures correctly from day one.
- Check 4 of 5What an auditor asks for
Ask for
Evidence of how exceptions or errors are handled following documented procedures.
Look at
Examples of error logs or incident reports referencing applicable procedures. GOOD reflects consistent handling of issues as outlined in the procedures.
- Check 5 of 5What an auditor asks for
Ask for
How changes to procedures are communicated to staff.
Look at
Communication logs, emails, or memorandum updates that are sent when procedures are updated. GOOD means there's a clear, documented process for communicating changes promptly to everyone involved.
Mappings
Closest match in ASD Information Security Manual: ISM-0042, Maintain effective system administration practices, which this control covers in full and more.
ASD Information Security Manual: 7 mappings
This control is broader than ISM-0042.
Annex A 5.37 requires operating procedures for information processing facilities to be documented and made available to personnel who need them. ISM-0042 requires system administration processes and supporting procedures to be developed, implemented and maintained, which necessarily relies on having clear, documented procedures accessible to administrators and operators. ISM-0042 is focused on the system administration domain specifically, whereas Annex A 5.37 is broader across all information processing operations, not just administration.
This control is broader than ISM-0206.
ISM-0206 requires documented and maintained cable labelling processes and supporting procedures. This is a specific instance of ISO/IEC 27001:2022 Annex A 5.37, which requires documented operating procedures for information processing facilities to be available to relevant personnel. Annex A 5.37 covers a wider set of operational procedures, while ISM-0206 narrows the requirement to cable labelling procedures specifically.
This control is broader than ISM-0348.
ISM-0348 requires organisations to develop, implement, and maintain media sanitisation processes and supporting procedures. ISO/IEC 27001:2022 Annex A 5.37 requires documented operating procedures for information processing facilities to be available to relevant personnel, which would include documenting and publishing media sanitisation procedures. Annex A 5.37 is broader because it covers operating procedures across many processing activities, whereas ISM-0348 is specifically focused on media sanitisation.
This control partially overlaps ISM-0576.
Annex A 5.37 requires operational procedures for information processing to be documented and made available to relevant personnel. ISM-0576 requires documented incident management policy and incident response plan, which are a class of operating procedures used during incident handling. ISM-0576 is focused specifically on cyber security incidents, whereas Annex A 5.37 applies to operating procedures across all information processing activities.
This control partially overlaps ISM-0888.
Annex A 5.37 requires operating procedures for information processing facilities to be documented and made available to personnel who need them. ISM-0888 strengthens this by requiring cyber security documentation to be reviewed at least annually and dated, helping ensure the documented procedures referenced by Annex A 5.37 remain current and reliable for users. ISM-0888 does not itself require that operating procedures exist or are made available; it focuses on review cadence and currency markings.
This control partially overlaps ISM-0912.
Annex A 5.37 requires documented and accessible operating procedures for information processing facilities. ISM-0912 requires a change and configuration management plan that defines how configuration changes are requested, tracked, documented, approved and communicated-these are operational procedures for managing system changes. ISM-0912 is specifically scoped to change/configuration management and includes detailed workflow elements, whereas Annex A 5.37 covers a wider range of operational procedures beyond change management.
This control partially overlaps ISM-1602.
ISM-1602 requires cyber security documentation, including change notifications, to be communicated to stakeholders. ISO/IEC 27001:2022 Annex A 5.37 requires documented operating procedures to be made available to personnel who need them, which overlaps with ensuring operational security documentation is distributed and accessible. Annex A 5.37 is narrower (availability to those who need procedures) and does not explicitly require proactive communication of updates to all stakeholders as ISM-1602 does.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.
Get help with this control
ISO 27001 training
Mindset Cyber runs PECB-accredited ISO/IEC 27001 training that maps directly to the controls in this library.




