A5.37 Documented operating procedures
Documented operating procedures are essential for consistent and secure operation of information systems. They serve as a reference for staff to follow standardized methods for tasks such as system startup, shutdown, backup, troubleshooting, and incident handling.
ISO 27001 A5.37 Documented operating procedures requires that organizations establish, document, and maintain operating procedures for managing IT systems and services. These procedures help reduce errors, improve efficiency, ensure compliance, and support business continuity by clearly outlining responsibilities and steps for key operational activities.
Implementation Guide #
Step 1: Identify Key Operational Activities
- List critical IT operations (e.g., backups, patch management, log reviews, software updates).
- Identify systems, applications, and environments needing standard procedures.
Step 2: Develop Standard Operating Procedures (SOPs)
- Create SOPs for routine tasks using a consistent format.
- Include objectives, scope, responsibilities, steps, tools needed, and safety/rollback procedures.
- Examples:
- Backup and restore processes
- Server maintenance routines
- Incident response actions
Tools to Use:
Microsoft Word or Google Docs for drafting SOPs,
Confluence or Notion for SOP collaboration and publishing,
ITSM tools like ServiceNow or Freshservice to embed SOPs into workflows.
Step 3: Ensure Accessibility and Version Control
- Store procedures in a secure, centralized location accessible to authorized staff.
- Use document management systems with versioning and change control (e.g., SharePoint, Atlassian Confluence).
Step 4: Train Relevant Personnel
- Conduct onboarding and refresher training for IT and support staff on following SOPs.
- Ensure they understand where to find procedures and how to request changes.
Step 5: Maintain and Review Procedures
- Set periodic reviews (e.g., annually or after major system changes).
- Assign owners to each document responsible for accuracy and updates.
Templates #
- Standard Operating Procedure (SOP) Template
- Change Log Template
- Document Review and Approval Log
- Access Log for SOP Documentation
- SOP Acknowledgment Form for Staff
Example #
A mid-sized enterprise documented its procedures for restoring email services after outages. The SOP outlined the tools to use, escalation paths, verification steps, and communication protocols. During an actual incident, the IT team followed the documented process and restored service within 30 minutes, reducing downtime and user disruption.
How to Comply #
To comply with A.5.37:
- Create documented procedures for key operational activities.
- Maintain accessibility, version control, and periodic review.
- Train staff and ensure they follow documented methods.
How to Pass an Audit #
Key Documents to Prepare:
- A library of current SOPs for IT operations
- Review history or change logs
- Staff training records or acknowledgment forms
- SOP compliance monitoring records
What the Auditor Will Check:
- Are operational procedures documented and maintained?
- Are they followed consistently by staff?
- Are there controls for versioning and updates?
- Do SOPs align with actual practices and system configurations?
Top 3 Mistakes People Make #
- Lack of consistency in documenting procedures across departments.
- Outdated SOPs that no longer reflect system changes or upgrades.
- Poor accessibility, making it hard for staff to find and use the correct documents.
ISO 27001 Documented Operating Procedures FAQ #
Q1: Can we use informal guidelines instead of full SOPs?
No. ISO 27001 requires formal, documented, and controlled procedures to ensure repeatability and accountability.
Q2: Who should write and approve SOPs?
Subject matter experts should write them, and department heads or ISMS managers should review and approve them.
Q3: How often should we review operating procedures?
At least annually, or whenever there are significant changes in systems or processes.
ISO 27001 Controls and Attribute Values #
| Control | Attribute Value |
| A.5.37 Documented Operating Procedures | Preventive, Operational, Compliance-Focused |
| Purpose | Ensure secure, standardized, and efficient operation of information systems |
| Applicability | IT operations, infrastructure teams, support services |
| ISO 27001 Domains | Operations Security, Organizational Controls |