Writing “implemented” across the board against theme 5 in the SoA and moving on is the mistake that attracts the most questions in Stage 2. Of the 93 controls in ISO/IEC 27001:2022 Annex A, 37 are in the “organizational controls” theme, from 5.1 to 5.37. This is the largest theme; it gathers unrelated topics from policy to cloud use and from incident management to intellectual property. This guide splits these controls into functional groups for the ISMS owners who fill in the SoA and operate the controls, and gives, for each group, the evidence the auditor typically asks for and misinterpretations you may come across.
The structure of the organizational controls theme
The 2022 revision divided Annex A into four themes: organizational (5), people (6), physical (7) and technological (8). The organizational theme gathers controls that can’t be tied to a specific person, physical area or technology and that require management decisions and process design. Annex A gives only the control statement; each control’s purpose and implementation guidance are in ISO/IEC 27002:2022. When interpreting, open both documents side by side. Annex A alone isn’t enough.
Splitting the 37 controls into six groups in practice makes SoA preparation and assigning owners easier. This grouping isn’t the standard’s official classification; it’s a practical view used to identify control owners.
| Group | Controls | Typical owner |
|---|---|---|
| Governance and roles | 5.1–5.8, 5.35–5.37 | ISMS manager, top management |
| Assets, information and access | 5.9–5.18 | IT, asset owners |
| Suppliers and cloud | 5.19–5.23 | Purchasing, IT |
| Incident management | 5.24–5.28 | IT security, ISMS manager |
| Continuity | 5.29–5.30 | IT, business continuity manager |
| Legal compliance and privacy | 5.31–5.34 | Legal, KVKK officer |
Governance and roles
This group contains information security policies (5.1), roles and responsibilities (5.2), segregation of duties (5.3), management responsibilities (5.4), contact with authorities and special interest groups (5.5, 5.6), threat intelligence (5.7) and information security in project management (5.8). Independent review (5.35), compliance with policies and standards (5.36) and documented operating procedures (5.37) also belong here by nature.
- 5.1 Policies: In addition to the top-level information security policy, topic-specific policies (access control, cryptography, backup, etc.) are expected. Evidence: approval and review dates, a record of communication to relevant staff.
- 5.3 Segregation of duties: A list of conflicting duties (e.g. the person requesting a change, approving it and putting it live). If full separation isn’t possible in small teams, monitoring and after-the-fact review records are kept as a compensating control. Everyone using the domain admin account in a three-person IT team is the classic gap for this control in the field.
- 5.7 Threat intelligence: One of the new controls introduced in 2022. An intelligence subscription isn’t required; but identifying sources (such as national CERT announcements and vendor security bulletins), assessing the information and turning it into action, and recording this, is expected. Reading the bulletin isn’t enough; the answer to “Does it affect our firewall, and what did we do?” must be on record.
- 5.8 Project management: The project initiation template includes information security requirements and a risk assessment. Evidence: the security assessment in the file of a completed project.
We explained in detail how to write policies in the information security policy guide.
Asset and information management controls
Controls 5.9 to 5.18 start with the inventory of information and other associated assets (5.9) and extend through acceptable use (5.10), return of assets (5.11), classification and labeling (5.12, 5.13), information transfer (5.14) and the access control family (5.15 access control, 5.16 identity management, 5.17 authentication information, 5.18 access rights).
The backbone of this group is the inventory. For an asset without a clear owner, classification, access rights approval or return control can’t be evidenced. The 2022 version uses the phrase “information and other associated assets”; so the inventory can’t be just a hardware list. Information assets such as customer data, drawings and source code, and the systems that process them, must appear together. A situation you may come across: there’s a list of servers pulled from purchase invoices in the accounting software, but no record of which information sits in which database. We covered inventory fields in the article preparing an information asset inventory.
The distinction in the access control family is: 5.15 covers the rules (policy), 5.16 the identity lifecycle, 5.17 the management of passwords and similar authentication information, and 5.18 granting, reviewing and removing rights. Technical implementation (e.g. multi-factor authentication configuration) falls under control 8.5 secure authentication in theme 8. For the organizational control, the auditor wants to see that the rule is defined and operated through a process. The practical test is simple: on what date were the last leaver’s Active Directory account, VPN profile and SaaS license closed? If none of the three dates is on record, 5.18 is weak.
Supplier and cloud controls
5.19 is information security in supplier relationships, 5.20 security in supplier agreements, 5.21 security in the ICT supply chain, 5.22 monitoring and change management of supplier services, and 5.23 information security for use of cloud services. 5.23 is a new control; it requires a process to be defined from acquiring a cloud service through use and management to exit.
The structure expected in practice:
- Tier suppliers by the information they access and the criticality of the service. A maintenance company that connects remotely to your firewall can’t be in the same tier as a stationery supplier.
- Define minimum contract clauses for each tier (confidentiality, incident notification time, use of subcontractors, right to audit, return/destruction of data at the end of the contract).
- Carry out periodic assessments for critical suppliers: independent assurance reports (such as an ISO 27001 certificate and its scope, a SOC 2 report), a questionnaire or an on-site visit.
- For cloud services, put the shared responsibility model in writing: what the provider manages, what you manage, and the exit plan.
You can find the supplier assessment method in the article supplier information security risk assessment, and the scope of our service in this area on the supplier and third-party risk management page.
Incident and continuity controls
Incident management is defined as a lifecycle with five controls: planning and preparation (5.24), assessment and decision on events (5.25), response (5.26), learning from incidents (5.27) and collection of evidence (5.28). Employees reporting events is control 6.8 in the people theme; design the two together.
In this group, the auditor typically opens the incident log and follows a few incidents from start to finish: how it was reported, by what criteria it was decided to be an “incident” or “not an incident”, who responded, and whether the root cause and lesson learned were recorded. An empty incident log isn’t good news. It’s usually read not as “no incidents” but as “incidents aren’t recognized or recorded”. Quarantine records in the antivirus console, locked-out accounts, a lost laptop; if none of these entered the incident process, the process exists only on paper. For the procedure structure, see the article writing an incident management procedure.
On the continuity side, 5.29 requires information security to be maintained during disruption, and the new control 5.30 requires ICT readiness for business continuity. The distinguishing point of 5.30 is that the recovery targets of ICT services are derived from the business impact analysis and these targets are tested. Evidence: recovery time and data loss targets set for ICT services, the disaster recovery plan, the latest test report and tracking of gaps found in testing. The technical backup control (8.13) is separate. Taking backups doesn’t meet 5.30.
Legal compliance and privacy controls
5.31 covers identifying legal, statutory, regulatory and contractual requirements; 5.32 intellectual property rights; 5.33 protection of records; and 5.34 privacy and protection of personal data. For organizations operating in Türkiye, the main input to 5.34 is KVKK (Law No. 6698) and its secondary regulations.
- 5.31: A register of requirements (legislation, contract clauses, customer specifications), the control in the ISMS that meets each one and the review date.
- 5.32: A software license inventory and license compliance check; usage rights for source code and design documents.
- 5.33: Record types, retention periods and storage media; disposal records for records whose legal retention period has expired.
- 5.34: A personal data inventory, privacy notices, data processor agreements and a breach notification process.
5.35 independent review and 5.36 compliance controls are the ISMS’s self-checking mechanism; they’re evidenced through internal audits, external audit reports and management reviews.
Common misinterpretations
| Check | Common misinterpretation | The right approach |
|---|---|---|
| 5.1 | A one-page general policy is enough | Topic-specific policies are also defined and reviewed |
| 5.3 | Not applicable in a small company, so excluded | Applied through compensating monitoring and review |
| 5.7 | A paid intelligence service is mandatory | A process of sources, assessment and action is enough |
| 5.9 | A hardware inventory is enough | Information assets and their owners are shown too |
| 5.23 | The cloud provider’s certificate covers everything | Customer-side responsibilities are managed separately |
| 5.24–5.27 | No incidents, so no evidence needed | Incident criteria, exercises and assessment records are kept |
| 5.30 | We do backups, so it’s met | Targets based on the business impact analysis, and test evidence |
Another common mistake is filling in Annex A like a checklist without linking it to the risk assessment. ISO 27001 clause 6.1.3 requires controls to be determined from risk treatment options and then compared with Annex A to verify that no necessary control has been omitted. Order matters. Risk first, then controls. We explained the selection record in the ISO 27001 SoA article; for support in mapping organizational controls to risks, see our risk analysis and SoA service. The follow-up article for the people and physical themes: Annex A people and physical controls. The official source for the control texts is the ISO/IEC 27002:2022 standard.
Frequently asked questions
Is it mandatory to implement all organizational controls?
No. Annex A controls are selected based on the risk assessment; those not implemented are written in the SoA with a justification. But in practice it’s very hard to defend to an auditor the exclusion of controls such as policies, roles, access control and incident management.
Does the 5.23 cloud control also cover SaaS applications?
Yes. 5.23 covers SaaS services as well as IaaS and PaaS. Acquisition, configuration, monitoring and exit rules must be defined for SaaS services such as email, file sharing or accounting too.
How is the threat intelligence control met in a small company?
For most small organizations, it’s enough to identify reliable, free sources, follow them regularly, assess the relevant information, turn it into action and record this assessment. What matters is that the information is tied to a decision and an action.
How is the line drawn between an organizational control and a technological control?
An organizational control defines the rule and the process; a technological control covers how this rule is applied in systems. For example, the access rights process is assessed under 5.18, and secure authentication configuration under 8.5.