ISO 27001 Controls List and Implementation Plan (Annex A)
A copy-ready ISO 27001 implementation plan and the full list of 93 Annex A controls (2022), plus a Statement of Applicability template and an AI prompt.
For Security and Legal & Compliance

What are the ISO 27001 Annex A controls, and how do you implement them?
ISO/IEC 27001:2022 Annex A lists 93 information security controls in four themes: Organizational (37), People (8), Physical (14) and Technological (34). You do not implement all 93 by default. You run a risk assessment, decide which controls apply, record that decision in a Statement of Applicability, and then put the chosen controls in place. Certification also requires the management system clauses (4 to 10): scope, policy, risk process, internal audit and management review.
This page gives you the full controls list, a phased implementation plan you can copy, a Statement of Applicability template, a worked example, and an AI prompt that drafts the first pass.
TL;DR
- Annex A has 93 controls in four themes in the 2022 edition, down from 114 controls in 14 domains in the 2013 edition, with 11 controls that are new.
- The controls are only half the standard. Clauses 4 to 10 (scope, leadership, risk, objectives, audit, review, improvement) are mandatory, and auditors check them first.
- Your risk assessment decides which controls apply. Excluding a control is allowed if you can justify it in the Statement of Applicability.
- A realistic plan runs in phases: scope and gap analysis, risk assessment, control implementation, internal audit and management review, then the two-stage certification audit.
- AI is good at drafting policies, mapping controls to your existing evidence and writing the first version of your register. It should not decide applicability or tell you evidence exists.
- Keep one living register with an owner, evidence link and review date per control. That register is what you will actually use for three years.
What does an ISO 27001 implementation plan look like?
Most projects follow the same arc. Timelines depend on scope, how much you already have documented (many large companies already hold SOC 2 reports or run NIST-aligned programs) and how quickly owners respond. Many mid-size and large organizations plan for several months to a year from kickoff to certification, but treat that as a planning range, not a promise.
Copy this table into your project tool and fill in names and dates.
| Phase | Key activities | Outputs | Owner | Target dates |
|---|---|---|---|---|
| 1. Mandate and scope | Get executive sponsorship. Define ISMS scope (business units, locations, systems, data). List interested parties and their requirements (customers, regulators, contracts). | Scope statement, sponsor sign-off, project charter | CISO / Security lead | |
| 2. Gap analysis | Compare current practices to clauses 4 to 10 and to each Annex A control. Rate each as in place, partial or missing. | Gap report, prioritized backlog | Security + Compliance | |
| 3. Policy and governance | Write the information security policy, define roles, set security objectives, set the risk methodology. | ISMS policy, roles and responsibilities, risk assessment procedure, objectives | Security + Legal | |
| 4. Risk assessment and treatment | Build the asset inventory. Identify threats and vulnerabilities. Score risks. Choose treatments (reduce, accept, transfer, avoid). | Risk register, risk treatment plan, risk owner approvals | Risk owners | |
| 5. Statement of Applicability | For all 93 controls: applicable or not, why, status, and where the evidence is. | Statement of Applicability (SoA) | Security + Compliance | |
| 6. Implement controls | Work the backlog: access reviews, supplier assessments, logging, backup tests, training, incident process. Collect evidence as you go. | Procedures, configurations, records | Control owners (IT, HR, Facilities, Engineering, Legal) | |
| 7. Awareness and training | Train all in-scope staff. Brief leadership on their duties. | Training records, acknowledgments | HR + Security | |
| 8. Operate and measure | Run the controls for long enough to produce records (access reviews, incident logs, backup tests). Track metrics. | Monitoring results, KPIs | Security | |
| 9. Internal audit | Audit the ISMS against the standard, using someone independent of the work being audited. Raise nonconformities. | Audit program, audit report, corrective actions | Internal audit / independent reviewer | |
| 10. Management review | Leadership reviews results, risks, audit findings and resourcing. Record decisions. | Management review minutes | Executive sponsor | |
| 11. Certification audit | Stage 1 (documentation and readiness review), then Stage 2 (implementation and effectiveness), by an accredited certification body. Fix any nonconformities. | Certificate | Security + auditor | |
| 12. Maintain | Surveillance audits in the following years, a full recertification at the end of the three-year cycle, continual improvement. | Ongoing records | Security |
Which documents does the standard require?
You need documented information for, at minimum: the ISMS scope, the information security policy, the risk assessment and risk treatment processes, the Statement of Applicability, the risk treatment plan, security objectives, evidence of competence, and the results of risk assessment, risk treatment, monitoring, internal audits, management reviews and corrective actions. Annex A controls then add their own procedures and records. Auditors would rather see a small set of documents people use than a large set nobody reads.
What is the full ISO 27001 Annex A controls list (2022)?
The list below uses the control numbers and names from ISO/IEC 27001:2022 Annex A. Controls marked "new" were added in 2022. For the full wording and implementation guidance, buy the standard and ISO/IEC 27002:2022 from ISO or your national standards body. The names alone are enough to plan with.
Organizational controls (5.1 to 5.37)
| ID | Control |
|---|---|
| 5.1 | Policies for information security |
| 5.2 | Information security roles and responsibilities |
| 5.3 | Segregation of duties |
| 5.4 | Management responsibilities |
| 5.5 | Contact with authorities |
| 5.6 | Contact with special interest groups |
| 5.7 | Threat intelligence (new) |
| 5.8 | Information security in project management |
| 5.9 | Inventory of information and other associated assets |
| 5.10 | Acceptable use of information and other associated assets |
| 5.11 | Return of assets |
| 5.12 | Classification of information |
| 5.13 | Labelling of information |
| 5.14 | Information transfer |
| 5.15 | Access control |
| 5.16 | Identity management |
| 5.17 | Authentication information |
| 5.18 | Access rights |
| 5.19 | Information security in supplier relationships |
| 5.20 | Addressing information security within supplier agreements |
| 5.21 | Managing information security in the ICT supply chain |
| 5.22 | Monitoring, review and change management of supplier services |
| 5.23 | Information security for use of cloud services (new) |
| 5.24 | Information security incident management planning and preparation |
| 5.25 | Assessment and decision on information security events |
| 5.26 | Response to information security incidents |
| 5.27 | Learning from information security incidents |
| 5.28 | Collection of evidence |
| 5.29 | Information security during disruption |
| 5.30 | ICT readiness for business continuity (new) |
| 5.31 | Legal, statutory, regulatory and contractual requirements |
| 5.32 | Intellectual property rights |
| 5.33 | Protection of records |
| 5.34 | Privacy and protection of PII |
| 5.35 | Independent review of information security |
| 5.36 | Compliance with policies, rules and standards for information security |
| 5.37 | Documented operating procedures |
People controls (6.1 to 6.8)
| ID | Control |
|---|---|
| 6.1 | Screening |
| 6.2 | Terms and conditions of employment |
| 6.3 | Information security awareness, education and training |
| 6.4 | Disciplinary process |
| 6.5 | Responsibilities after termination or change of employment |
| 6.6 | Confidentiality or non-disclosure agreements |
| 6.7 | Remote working |
| 6.8 | Information security event reporting |
Physical controls (7.1 to 7.14)
| ID | Control |
|---|---|
| 7.1 | Physical security perimeters |
| 7.2 | Physical entry |
| 7.3 | Securing offices, rooms and facilities |
| 7.4 | Physical security monitoring (new) |
| 7.5 | Protecting against physical and environmental threats |
| 7.6 | Working in secure areas |
| 7.7 | Clear desk and clear screen |
| 7.8 | Equipment siting and protection |
| 7.9 | Security of assets off-premises |
| 7.10 | Storage media |
| 7.11 | Supporting utilities |
| 7.12 | Cabling security |
| 7.13 | Equipment maintenance |
| 7.14 | Secure disposal or re-use of equipment |
Technological controls (8.1 to 8.34)
| ID | Control |
|---|---|
| 8.1 | User endpoint devices |
| 8.2 | Privileged access rights |
| 8.3 | Information access restriction |
| 8.4 | Access to source code |
| 8.5 | Secure authentication |
| 8.6 | Capacity management |
| 8.7 | Protection against malware |
| 8.8 | Management of technical vulnerabilities |
| 8.9 | Configuration management (new) |
| 8.10 | Information deletion (new) |
| 8.11 | Data masking (new) |
| 8.12 | Data leakage prevention (new) |
| 8.13 | Information backup |
| 8.14 | Redundancy of information processing facilities |
| 8.15 | Logging |
| 8.16 | Monitoring activities (new) |
| 8.17 | Clock synchronization |
| 8.18 | Use of privileged utility programs |
| 8.19 | Installation of software on operational systems |
| 8.20 | Networks security |
| 8.21 | Security of network services |
| 8.22 | Segregation of networks |
| 8.23 | Web filtering (new) |
| 8.24 | Use of cryptography |
| 8.25 | Secure development life cycle |
| 8.26 | Application security requirements |
| 8.27 | Secure system architecture and engineering principles |
| 8.28 | Secure coding (new) |
| 8.29 | Security testing in development and acceptance |
| 8.30 | Outsourced development |
| 8.31 | Separation of development, test and production environments |
| 8.32 | Change management |
| 8.33 | Test information |
| 8.34 | Protection of information systems during audit testing |
The 2013 edition had 114 controls in 14 domains. The 2022 edition merged many of them, renamed others and added the 11 marked "new". If your existing documents reference the old numbering (A.5 to A.18), you will need a mapping table.
What is the Statement of Applicability template?
The Statement of Applicability (SoA) is the document auditors spend the most time with. It lists every Annex A control and states whether it applies, why, and where the proof is. Copy these columns into a spreadsheet or database.
| Column | What to put in it |
|---|---|
| Control ID | 5.1, 5.2, ... 8.34 |
| Control name | From the list above |
| Applicable? | Yes / No |
| Justification | The risk or requirement that drives it (risk ID, contract clause, law). For exclusions, why it does not apply. |
| Implementation status | Not started / Partial / Implemented / Not applicable |
| How it is implemented | One or two sentences in plain language |
| Owner | A named person or role |
| Evidence location | Link to policy, ticket, screenshot, report or system |
| Related risks | Risk register IDs |
| Last reviewed | Date |
| Next review | Date |
Worked example: one filled row
| Column | Entry |
|---|---|
| Control ID | 8.13 |
| Control name | Information backup |
| Applicable? | Yes |
| Justification | Risk R-014 (loss of customer records through ransomware or failure); contractual recovery commitments to customers |
| Implementation status | Implemented |
| How it is implemented | Production databases back up daily to a separate account with restricted access. Restore test performed each quarter. |
| Owner | Head of Infrastructure |
| Evidence location | Backup policy v2.1; last restore test ticket; backup job report |
| Related risks | R-014, R-022 |
| Last reviewed | (date) |
| Next review | (date) |
An example of a justified exclusion: 8.30 Outsourced development can be marked "No" if you do not outsource any software development in scope. State that fact and the date you confirmed it. Auditors will test it.
How can AI help draft your ISO 27001 plan?
AI is useful for the heavy first-draft work: turning a scope description into a risk list, drafting policies, and pre-filling the SoA. Paste the prompt below into the AI tool your company approves. Replace the bracketed parts.
You are helping a security and compliance team prepare for ISO/IEC 27001:2022 certification.
Context:
- Company type and size: [e.g., 4,000-person financial services firm]
- ISMS scope: [business units, locations, systems, data types in scope]
- Existing frameworks or audits we already have: [e.g., SOC 2 Type II, NIST CSF, none]
- Key tools: [identity provider, cloud provider, ticketing, endpoint management, SIEM]
- Customer or legal drivers: [contracts, regulations]
Task:
1. Create a Statement of Applicability table for all 93 Annex A controls (2022 numbering: 5.1-5.37, 6.1-6.8, 7.1-7.14, 8.1-8.34) with these columns: Control ID, Control name, Likely applicable (Yes/No/Needs risk review), Why, Typical evidence an auditor would ask for, Suggested owner role.
2. Mark any control you are unsure about as "Needs risk review". Do not assume we have implemented anything.
3. Then list the 10 controls most likely to need new work given the context above, and why.
Rules: Do not invent our policies or tools. Where you make an assumption, label it "Assumption".
What should you check in the answer?
- Numbering and names. Compare against the tables above. Models sometimes mix the 2013 and 2022 numbering.
- Applicability calls. Treat every "No" as a question for your risk owners, not a decision. Only your risk assessment can exclude a control.
- Invented evidence. If the output says you "have" a policy or tool, delete it unless you can point to it. Auditors ask for the document.
- Fit with your scope. Generic output tends to over-include. Cut anything outside the scope statement.
Where should you not trust AI?
Do not let AI score your risks without the people who own those risks. Do not treat its text as a substitute for the standard itself. Do not paste confidential material (customer data, unredacted vulnerability reports, credentials) into a tool your company has not approved. And do not submit AI-written policies you have not read: auditors will interview staff, and people need to recognize and follow what the policy says.
How do you get the most out of the plan in practice?
A few habits separate smooth projects from painful ones.
- Start with scope and keep it narrow at first. Certifying one product or business unit and expanding later is common and acceptable. A scope that is too broad is the most frequent reason timelines slip.
- Reuse what you have. If you already run SOC 2, NIST-based or customer-mandated controls, map them to Annex A rather than rewriting. Many access, logging, backup and incident controls already exist.
- Assign every control to a named owner outside Security. HR owns screening and training. Facilities owns physical controls. Legal owns 5.31 to 5.34. Engineering owns secure development. Security coordinates but cannot own it all.
- Collect evidence as you go. A quarterly access review needs a dated record. If you cannot show it happened, an auditor will treat it as not done.
- Run an honest internal audit. Finding gaps yourself costs less than having the certification body find them.
- Plan the supplier work early. Controls 5.19 to 5.23 involve contracts and questionnaires, which move slowly.
Can you build your own ISO 27001 controls tracker?
Most teams track the SoA in a spreadsheet, and it works until the owners, evidence links and review dates start to drift. A small internal app can do better: one row per control with an owner, status, evidence link and next review date, a login so owners update their own rows, reminder emails before reviews are due, and a view that shows gaps by theme for management review. You can describe that to Remy in plain English and get a deployed app with a database and sign-in, which you own, rather than adding another compliance subscription. Check with your security team where it may be hosted and what data it may hold.
Frequently Asked Questions
How many controls are in ISO 27001?
The 2022 edition of Annex A has 93 controls grouped into Organizational (37), People (8), Physical (14) and Technological (34). The 2013 edition had 114 controls in 14 domains. Certifications to the 2013 edition were subject to a transition period to the 2022 version, so new projects should use the 2022 controls.
Do you have to implement every Annex A control?
No. You must consider every control and record your decision in the Statement of Applicability. You can exclude controls that your risk assessment and legal and contractual requirements show are not needed, as long as you justify each exclusion. You must also check that Annex A does not omit any control your risks require, and add your own if needed.
How long does ISO 27001 implementation take?
It depends on scope, starting maturity and how fast control owners can act. Organizations with existing security programs often plan for several months, while those starting from little documentation often need closer to a year. Certification requires a Stage 1 and Stage 2 audit by an accredited certification body, and you need operating records from your controls before Stage 2.
What is the difference between ISO 27001 and ISO 27002?
ISO 27001 is the certifiable standard: it sets the requirements for the management system and lists the Annex A controls. ISO 27002 is a guidance document that explains each control in detail, with purpose, attributes and implementation advice. You are audited against 27001. You use 27002 to decide how to implement the controls.
Can AI write my ISO 27001 documentation?
It can draft policies, procedures and a first-pass Statement of Applicability, which saves real time. You still need to edit the drafts to match what your company actually does, confirm every claim about existing tools and evidence, and have risk owners approve the risk decisions. An auditor will test whether the documents describe real practice.
Useful for
How we source, write, and correct our articles. Editorial standards
Related articles

Tabletop Exercise Scenarios for Incident Response (Template)

What Was the Hugging Face Incident? Christiano on Reward Hacking

Why Does Paul Christiano Want AI Labs to Pause Progress?
