ISO/IEC 27001:2022’s Annex A contains 93 information security controls organised under four themes: Organizational (A.5), People (A.6), Physical (A.7) and Technological (A.8). They are a normative reference set, not a blanket checklist: your risk assessment decides which controls apply, and your Statement of Applicability records and justifies every inclusion and exclusion. The full list is below, cross-checked against two independent published control lists and anchored to Ireland’s national standards body. [Source: NSAI ISO/IEC 27001 page, checked 13-08-2026; control titles cross-checked between HighTable and CertPro, both checked 13-08-2026]
Most pages ranking for this term republish the list without saying where it comes from. This guide gives you the list with its sourcing, then the parts the list alone will not tell you: how controls are actually selected, what changed in the 2022 edition, what evidence satisfies each theme for a cloud-native software company, and what an auditor will sample.
The ISO 27001 Annex A controls at a glance
93 controls across four themes. The total of 93 is stated by NSAI, Ireland’s national standards body; the per-theme counts below are arithmetic from the published control numbering ranges, which is flagged here because ISO prints no count in the standard itself. [Source: NSAI ISO/IEC 27001 page, checked 13-08-2026, verbatim: “Annex A of the standard contains 93 information security controls organised under four themes”; numbering ranges from the published control lists, checked 13-08-2026]
| Reference | Theme | Controls | Numbering | What it covers, in one line |
|---|---|---|---|---|
| A.5 | Organizational controls | 37 | A.5.1 to A.5.37 | Policies, roles, asset and supplier management, incidents, legal obligations |
| A.6 | People controls | 8 | A.6.1 to A.6.8 | Screening, training, contracts, the employment lifecycle, remote working |
| A.7 | Physical controls | 14 | A.7.1 to A.7.14 | Premises, entry, equipment, cabling, media, disposal |
| A.8 | Technological controls | 34 | A.8.1 to A.8.34 | Access control, logging, vulnerabilities, cryptography, secure development |
| Clauses 4 to 10 | The ISMS itself | 7 clauses | 4.1 to 10.2 | The management system requirements Annex A hangs off (see below) |
[Source: NSAI ISO/IEC 27001 page (93 total, four themes), checked 13-08-2026; per-theme counts are arithmetic from the published numbering ranges (A.5.1-A.5.37, A.6.1-A.6.8, A.7.1-A.7.14, A.8.1-A.8.34), cross-checked between HighTable and CertPro, both checked 13-08-2026; theme titles printed as in the standard’s English text, which uses ISO spelling “Organizational” while NSAI’s web page renders “Organisational”]
Why listen to us
Atoro is an Irish AI governance and cyber compliance consultancy for software companies, and the first consultancy in Europe certified against ISO 42001; our certificate is AIMS-AT-120224, issued by A-LIGN under ANAB accreditation. Our own site states we have delivered more than 200 certifications across security and compliance. [Source: atoro.io, checked 08-08-2026] We deliver ISO 27001 implementation and independent ISO 27001 internal audits for software companies across the UK and Ireland, so Annex A is a list we map, justify and audit against, not one we have only read.
The full ISO 27001 Annex A controls list
The complete 93-control list for the 2022 edition follows, grouped by the four themes. Titles were cross-checked against two independent published lists (HighTable, a UK consultancy, and CertPro, a US CPA firm); where their wording differed on a handful of titles we used the fuller form and flagged the variants at the end of this section. [Source: HighTable ISO 27001 Annex A controls list, and CertPro ISO 27001 controls list, both checked 13-08-2026; both are tier 2 sources, so treat exact wording as best-available pending check against the purchased standard]
A.5 Organizational controls (37 controls, A.5.1 to A.5.37)
- A.5.1 Policies for information security
- A.5.2 Information security roles and responsibilities
- A.5.3 Segregation of duties
- A.5.4 Management responsibilities
- A.5.5 Contact with authorities
- A.5.6 Contact with special interest groups
- A.5.7 Threat intelligence
- A.5.8 Information security in project management
- A.5.9 Inventory of information and other associated assets
- A.5.10 Acceptable use of information and other associated assets
- A.5.11 Return of assets
- A.5.12 Classification of information
- A.5.13 Labelling of information
- A.5.14 Information transfer
- A.5.15 Access control
- A.5.16 Identity management
- A.5.17 Authentication information
- A.5.18 Access rights
- A.5.19 Information security in supplier relationships
- A.5.20 Addressing information security within supplier agreements
- A.5.21 Managing information security in the ICT supply chain
- A.5.22 Monitoring, review and change management of supplier services
- A.5.23 Information security for use of cloud services
- A.5.24 Information security incident management planning and preparation
- A.5.25 Assessment and decision on information security events
- A.5.26 Response to information security incidents
- A.5.27 Learning from information security incidents
- A.5.28 Collection of evidence
- A.5.29 Information security during disruption
- A.5.30 ICT readiness for business continuity
- A.5.31 Identification of legal, statutory, regulatory and contractual requirements
- A.5.32 Intellectual property rights
- A.5.33 Protection of records
- A.5.34 Privacy and protection of PII
- A.5.35 Independent review of information security
- A.5.36 Compliance with policies, rules and standards for information security
- A.5.37 Documented operating procedures
A.6 People controls (8 controls, A.6.1 to A.6.8)
- A.6.1 Screening
- A.6.2 Terms and conditions of employment
- A.6.3 Information security awareness, education and training
- A.6.4 Disciplinary process
- A.6.5 Responsibilities after termination or change of employment
- A.6.6 Confidentiality or non-disclosure agreements
- A.6.7 Remote working
- A.6.8 Information security event reporting
A.7 Physical controls (14 controls, A.7.1 to A.7.14)
- A.7.1 Physical security perimeters
- A.7.2 Physical entry controls
- A.7.3 Securing offices, rooms and facilities
- A.7.4 Physical security monitoring
- A.7.5 Protecting against physical and environmental threats
- A.7.6 Working in secure areas
- A.7.7 Clear desk and clear screen
- A.7.8 Equipment siting and protection
- A.7.9 Security of assets off-premises
- A.7.10 Storage media
- A.7.11 Supporting utilities
- A.7.12 Cabling security
- A.7.13 Equipment maintenance
- A.7.14 Secure disposal or re-use of equipment
A.8 Technological controls (34 controls, A.8.1 to A.8.34)
- A.8.1 User endpoint devices
- A.8.2 Privileged access rights
- A.8.3 Information access restriction
- A.8.4 Access to source code
- A.8.5 Secure authentication
- A.8.6 Capacity management
- A.8.7 Protection against malware
- A.8.8 Management of technical vulnerabilities
- A.8.9 Configuration management
- A.8.10 Information deletion
- A.8.11 Data masking
- A.8.12 Data leakage prevention
- A.8.13 Information backup
- A.8.14 Redundancy of information processing facilities
- A.8.15 Logging
- A.8.16 Monitoring activities
- A.8.17 Clock synchronisation
- A.8.18 Use of privileged utility programs
- A.8.19 Installation of software on operational systems
- A.8.20 Networks security
- A.8.21 Security of network services
- A.8.22 Segregation of networks
- A.8.23 Web filtering
- A.8.24 Use of cryptography
- A.8.25 Secure development life cycle
- A.8.26 Application security requirements
- A.8.27 Secure system architecture and engineering principles
- A.8.28 Secure coding
- A.8.29 Security testing in development and acceptance
- A.8.30 Outsourced development
- A.8.31 Separation of development, test and production environments
- A.8.32 Change management
- A.8.33 Test information
- A.8.34 Protection of information systems during audit testing
[Source: titles cross-checked between HighTable and CertPro, both checked 13-08-2026, with corroboration for the A.8.28 Secure coding title from three further tier 2 sources. All sources used are tier 2; ISO sells the standard text, so exact official wording should be confirmed against the purchased standard or ISO/IEC 27002:2022 before print.]
Sourcing notes on the list. First, wording variants between the two sources: HighTable prints shortened forms on a few titles (for example “Network controls” at A.8.20 where CertPro prints “Networks security”, and singular “Physical security perimeter” at A.7.1); we used the fuller forms above. Second, completeness: the list above contains all 34 A.8 controls including A.8.28 Secure coding; at least one ranking page’s published list skips that number, so check any downloaded checklist against the count of 93 before you rely on it.
What Annex A actually is (and what it is not)
Annex A is the standard’s normative reference set of information security controls. It is not a list of requirements you must all meet: the requirement is to run a risk assessment, select the controls that treat your risks, and justify inclusions and exclusions in the Statement of Applicability. [Source: NSAI ISO/IEC 27001 page (Annex A “reference” framing and 93-control statement), checked 13-08-2026; EN ISO/IEC 27001:2023 table of contents listing “Annex A (normative) Information security controls reference”, via iTeh/SIST preview, checked 13-08-2026]
The mechanism matters more than the list. Clause 6.1.3, “Information security risk treatment”, is where the standard requires the Statement of Applicability (SoA): the document that records which Annex A controls you need, why you included them, whether they are implemented, and why any were excluded. Three independent practitioner sources place the SoA requirement at clause 6.1.3 d) with those four contents; we could not confirm the letter against ISO’s own free preview, which blocked access on the day we checked. [Source: Cybernion SoA guide, SecureSlate SoA guide, and Security Compliance Guide SoA guide, all checked 13-08-2026, tier 2]
Practitioners are blunt about the checklist misconception. One consultant on r/ISO27001 put it: “Companies often treat Annex A like a mandatory checklist, while auditors sometimes push the same misconception. In reality, 6.1.3 is about risk-driven treatment: run your (proper) risk analysis, select only the controls that address identified risks, justify exclusions in the SoA, and plan their implementation.” [Source: r/ISO27001, u/DxfferentMSP, captured 13-08-2026, language source only] An auditor answering a question about Annex A noncompliance made the same point from the other side: “Technically the Annex A controls are not requirements so you cannot be non-compliant with them. If however your SoA states you have a control implementation even though you have not done so, that would be an issue.” [Source: r/ISO27001, u/Marekjdj, captured 13-08-2026, language source only] Read those together and the audit position is clear: you are not audited against Annex A in the abstract, you are audited against what your SoA claims.
Annex A and ISO/IEC 27002: not the same document
Annex A is the control reference inside ISO/IEC 27001. ISO/IEC 27002:2022 is a separate guidance standard that explains how to implement those controls; you can be certified to 27001, not to 27002. [Source: iso.org ISO/IEC 27002:2022 page FAQ, checked 13-08-2026]
ISO states the relationship on its own 27002 page, verbatim: “While ISO/IEC 27001 specifies the requirements for establishing an ISMS, ISO/IEC 27002 provides the detailed best practices and controls that can be applied within the ISMS.” On certification: “No, ISO/IEC 27002 provides best practice recommendations and cannot be certified to. But organizations can get certified to ISO/IEC 27001 which references ISO/IEC 27002 guidance.” [Source: iso.org ISO/IEC 27002:2022 page FAQ, checked 13-08-2026, verbatim]
This corrects a confusion that appears in the wild, including on ranking pages, that ISO 27002 is “an annex to ISO 27001”. It is not. Annex A is part of 27001; 27002 is the 152-page guidance companion, priced at CHF 227 (Swiss francs) on iso.org, where the 19-page 27001 itself is CHF 155 list price as checked 13-08-2026. [Source: iso.org ISO/IEC 27002:2022 page and ISO/IEC 27001:2022 page, both checked 13-08-2026] If you want the objectives and implementation guidance behind each control title in the list above, 27002 is the document that contains them.
The clauses 4 to 10 structure Annex A hangs off
Annex A does not stand alone. The requirements you are certified against live in clauses 4 to 10 of the standard, the management system itself, and Annex A is the control menu those clauses draw on. No page ranking for this keyword publishes both; the list without the clauses is half the standard. [Source: EN ISO/IEC 27001:2023 table of contents, the CEN-CENELEC adoption approved “without any modification” from ISO/IEC 27001:2022, via iTeh/SIST preview, checked 13-08-2026]
The published structure of ISO/IEC 27001:2022:
- 4 Context of the organization: 4.1 Understanding the organization and its context; 4.2 Understanding the needs and expectations of interested parties; 4.3 Determining the scope of the information security management system; 4.4 Information security management system
- 5 Leadership: 5.1 Leadership and commitment; 5.2 Policy; 5.3 Organizational roles, responsibilities and authorities
- 6 Planning: 6.1 Actions to address risks and opportunities (6.1.1 General; 6.1.2 Information security risk assessment; 6.1.3 Information security risk treatment); 6.2 Information security objectives and planning to achieve them; 6.3 Planning of changes
- 7 Support: 7.1 Resources; 7.2 Competence; 7.3 Awareness; 7.4 Communication; 7.5 Documented information (7.5.1 General; 7.5.2 Creating and updating; 7.5.3 Control of documented information)
- 8 Operation: 8.1 Operational planning and control; 8.2 Information security risk assessment; 8.3 Information security risk treatment
- 9 Performance evaluation: 9.1 Monitoring, measurement, analysis and evaluation; 9.2 Internal audit (9.2.1 General; 9.2.2 Internal audit programme); 9.3 Management review (9.3.1 General; 9.3.2 Management review inputs; 9.3.3 Management review results)
- 10 Improvement: 10.1 Continual improvement; 10.2 Nonconformity and corrective action
[Source: EN ISO/IEC 27001:2023 table of contents via iTeh/SIST preview, checked 13-08-2026; note 6.3 confirmed via the Slovenian national TOC on the same preview, and clause 10’s subclause order is flipped versus the 2013 edition]
A consultant in a practitioner thread on mapping controls put the relationship in one line: “Annex A does not get you certified, clause 4 to 10 will, annex A will help with clause 8.3.” [Source: r/ISO27001, u/MisterD05, captured 13-08-2026, language source only] That is the right mental model. The risk assessment at clause 6.1.2 identifies your risks; clause 6.1.3 turns them into a treatment plan and the SoA; clause 8 runs both in operation. Annex A is where the candidate controls come from, which is why a weak risk assessment produces a weak control set no matter how carefully the 93 are read.
What changed in the 2022 edition
The 2022 edition restructured Annex A from 114 controls across 14 domains in the 2013 edition to 93 controls across four themes, merging overlapping controls and adding new ones aimed at cloud, threat intelligence, data handling and secure development. The exact count of new controls is disputed across sources, so we describe the new ground rather than print a bare number. [Source: 114 controls in 14 domains for the 2013 edition and 93 in 4 for 2022, consistent across IS Partners and CertPro, both checked 13-08-2026, tier 2; the 2013 edition’s own contents show “Annex A (normative) Reference control objectives and controls” via the iTeh ISO/IEC 27001:2013 preview, checked 13-08-2026]
Ten controls are consistently tagged as new across the tier 2 sources we checked: A.5.7 Threat intelligence; A.5.23 Information security for use of cloud services; A.5.30 ICT readiness for business continuity; A.7.4 Physical security monitoring; A.8.9 Configuration management; A.8.10 Information deletion; A.8.11 Data masking; A.8.12 Data leakage prevention; A.8.16 Monitoring activities; A.8.28 Secure coding. Sources then disagree: some count A.5.21 Managing information security in the ICT supply chain and A.8.23 Web filtering among the new controls, others treat them as changed, which is why published totals vary between 11 and 12. [Source: IS Partners new-controls list (11, includes A.8.23, excludes A.5.21) and CertPro new-controls table (11, includes A.5.21, excludes A.8.23 in its table while tagging it new in body text), both checked 13-08-2026]
Read the new set by theme and it tells you where the standard moved: threat and supply-side awareness (A.5.7, and the disputed A.5.21), cloud service governance (A.5.23), ICT continuity (A.5.30), and a data-and-engineering cluster in the technological theme covering configuration, deletion, masking, leakage prevention, monitoring and secure coding. For a software company, that A.8 cluster plus A.5.23 is where the 2022 edition’s attention landed.
Two other current-edition markers worth knowing. Clause 6.3 “Planning of changes” is new in the 2022 edition’s clause structure. [Source: EN ISO/IEC 27001:2023 TOC via iTeh/SIST preview, checked 13-08-2026] And ISO published a free amendment, ISO/IEC 27001:2022/Amd 1:2024, which adds climate-change considerations to the clause 4 context text. [Source: iso.org ISO/IEC 27001:2022 page listing Amd 1:2024 at CHF 0, checked 13-08-2026; amendment content corroborated by SureCloud, checked 13-08-2026, tier 2] The 2013 edition is closed for new certifications: multiple tier 2 sources state the transition period ended 31 October 2025, and any page still quoting “114 controls” is describing a withdrawn structure. [Source: transition date asserted by Cybernion, SureCloud and dSalta pages, all checked 13-08-2026, tier 2]
What evidence satisfies each theme for a cloud-native, fully remote software company
The control titles name the deliverables, and each theme has a characteristic evidence shape. What follows is derived from the titles plus labelled practitioner language, because no tier 1 or tier 2 source publishes a theme-by-theme evidence map for this profile; treat it as practitioner guidance, not cited fact.
A.5 Organizational: policy, ownership and the paper trail that proves governance
The evidence the titles point to: approved policies and topic-specific policies (A.5.1), named role assignments (A.5.2), an asset inventory that includes your cloud services and codebases (A.5.9), classification and labelling rules (A.5.12, A.5.13), supplier agreements with security clauses and monitoring records (A.5.19 to A.5.22), incident plans and post-incident reviews (A.5.24 to A.5.27), and the register of legal and contractual obligations (A.5.31). For a software company, A.5.23 Information security for use of cloud services is the theme’s centre of gravity: one self-described lead auditor (“LA, 100+ audits”) wrote that alongside clear desk and clear screen, the recurring findings he sees are “mapping your risk back to your annex a controls” and that 5.23 “is not very well understood in organizations.” [Source: r/ISO27001, u/Zealousideal_Dog6629, captured 13-08-2026, language source only] For a cloud-native company, A.5.23 is where your AWS, GCP or Azure responsibilities meet your ISMS, so expect it to be read closely.
A.6 People: employment lifecycle records
The evidence the titles point to: screening records proportionate to role (A.6.1), contracts and terms covering security responsibilities (A.6.2), training and awareness completion records (A.6.3), the disciplinary process (A.6.4), leaver checklists showing access revoked and assets returned (A.6.5, also A.5.11), signed confidentiality agreements (A.6.6), remote working rules (A.6.7) and a channel staff actually use to report events (A.6.8). For a fully remote company, A.6.7 carries the weight A.7 would for an office-based one: home-working and coworking expectations written down, communicated and acknowledged.
A.7 Physical: small surface, honest exclusions
The evidence the titles point to concentrates on premises, equipment and media. A cloud-native, fully remote company has a small physical attack surface, and the honest move is to exclude much of this theme with justification rather than perform it. Practitioners running exactly this profile describe the same approach: “I have no offices, no on prem network, everything is saas, cloud and zero trust. Most physical controls are descoped. I still have a physical security policy, and it has some focus on how to stay safe when coworking in shared office spaces.” [Source: r/ISO27001, u/JPJackPott, captured 13-08-2026, language source only] Another put the mechanism plainly: “I simply remove items from the SoA where there are no risks driving inclusion of those SoA items.” [Source: r/ISO27001, u/skip-pivot, same thread, language source only] What usually survives for a remote team: clear desk and clear screen expectations (A.7.7, one of the recurring audit findings noted above), secure disposal of laptops and drives (A.7.14), and storage media handling (A.7.10). The exclusion is defensible; an unjustified gap is not.
A.8 Technological: where a software company’s audit is won or lost
This theme is where your existing engineering practice maps most directly. The evidence the titles point to: endpoint management and disk encryption records (A.8.1), privileged access lists and reviews (A.8.2), role-based access configuration (A.8.3), repository access rules (A.8.4), MFA enforcement (A.8.5), vulnerability scanning and patch records (A.8.8), configuration baselines (A.8.9), backup and restore test evidence (A.8.13), log retention and review (A.8.15, A.8.16), network and cloud security group configuration (A.8.20 to A.8.22), key management (A.8.24), and the secure development controls: lifecycle rules, application security requirements, architecture principles, secure coding, security testing, environment separation and change management (A.8.25 to A.8.32). An in-house implementer on r/ISO27001 described the small-team version honestly: “I’m a team of 2 and we have our Audit on Monday and Tuesday so I’ll know better then! Mostly we are using checklists and calendar reminders for now.” [Source: r/ISO27001, u/Ethernetman1980, captured 13-08-2026, language source only] Checklists pass only if the records behind them stay live: one practitioner reported “a control on access reviews technically satisfied by a spreadsheet nobody updated in months. Passed the checklist, failed the actual intent.” [Source: r/ISO27001, u/8h45k4r, captured 13-08-2026, language source only]
How auditors sample
Auditors do not test all 93 controls end to end; they sample against your SoA. CertPro, a US CPA firm, describes the evaluation as three dimensions: design adequacy (does the control address the identified risk), implementation evidence (is there documented evidence it operates), and operational effectiveness (does it produce the intended outcome consistently over time). [Source: CertPro ISO 27001 controls list, checked 13-08-2026, tier 2] Forum answers from auditors fill in the sampling behaviour: “In my experience, external auditors expect you to have implemented all controls unless there is a suitable justification to exclude it” [Source: r/ISO27001, u/zenith_97, same thread as above, language source only], and the recurring findings are mismatches between the SoA and reality, clear desk and clear screen, risk-to-control mapping, and the cloud services control, as quoted above. The practical consequence: depth on a justified control set beats shallow coverage of all 93.
Common failure points
The failures practitioners report are not exotic: paper controls with no operating evidence, an SoA that overclaims, and control work that starts before the risk assessment. All come from labelled practitioner forum language, so treat them as informed warnings, not statistics.
- Checklist thinking. “Most organizations starting out on ISO 27001 are too much focused on checking off controls, and pay too little attention to the management processes,” wrote one contributor disclosing “I’m an auditor,” adding that “it’s not called an ISMS for nothing.” [Source: r/ISO27001, u/But-I-Am-a-Robot, practitioner thread, captured 13-08-2026, language source only] Annex A serves clauses 4 to 10; it does not replace them.
- Overclaiming in the SoA. The auditor finding quoted above: your SoA states a control is implemented and it is not. That is the noncompliance that actually bites, not the exclusion itself.
- Stale evidence. The access-review spreadsheet nobody updated. Applicability matters less than “proving the depth you claimed is real.”
- Starting from the controls instead of the risk. “The risk assessment (6.1.2) and the Statement of Applicability are the real roots, and any Annex A dependency graph you draw is downstream of them.” [Source: r/ISO27001, u/Snoo_29776, control dependencies thread, captured 13-08-2026, language source only]
- Overbuilding controls you do not need. One consultant noted auditors sometimes push the other way: “I have seen some auditors interpret it as requiring full SIEM deployments for even very small companies, which is way beyond what’s actually needed.” [Source: r/ISO27001, u/Cyber_Gooser, over-interpreted control thread, captured 13-08-2026, language source only] Right-size to your risks; the SoA is where that sizing is defended.
- Rebuilding instead of mapping. A team that expected to redo everything reported: “We went in expecting to rebuild everything and were surprised by how much already existed once we laid it out.” [Source: r/ISO27001, u/Ill-Nebula6909, mapping thread, captured 13-08-2026, language source only]
Requirements people assume exist, but do not
Most Annex A folklore comes from treating the standard as a product checklist. The structure above says otherwise.
- “We must implement all 93 controls.” No. Selection is risk-based and exclusions are legitimate when justified in the SoA; the misconception is common enough that practitioners and auditors both complain about it. [Source: r/ISO27001 over-interpreted control thread, language source only; CertPro and IS Partners both state the risk-based selection position, checked 13-08-2026, tier 2]
- “Penetration testing is required by ISO 27001.” The standard names no such control. One practitioner: “Pen testing. Which is a client requirement usually and interpreted as a 27001 requirement which it is not.” Another consultant: “It’s not a specific requirement of the standard. However, auditors always attack it like it’s a line item / must have. I have had auditors back down on pen testing a few times now.” The vulnerability management control is A.8.8; how you satisfy it follows from your risk assessment. [Source: r/ISO27001, u/Natural_Zucchini_274 and u/Cyber_Gooser, over-interpreted control thread, captured 13-08-2026, language source only]
- “Annex A compliance is the certification.” The certificate is for the ISMS under clauses 4 to 10; Annex A is the control reference those clauses use. [Source: EN ISO/IEC 27001:2023 TOC via iTeh/SIST preview, checked 13-08-2026]
- “ISO 27002 is an annex of ISO 27001.” It is a separate guidance standard that “cannot be certified to”, in ISO’s own FAQ wording. [Source: iso.org ISO/IEC 27002:2022 page FAQ, checked 13-08-2026, verbatim]
- “There are 114 controls in 14 domains.” That was the 2013 edition, now withdrawn; the current structure is 93 controls in four themes. Any checklist still counting to 114 is stale. [Source: IS Partners and CertPro, checked 13-08-2026, tier 2; NSAI for the 93 total, tier 1]
- “ISO 27001 is a security standard.” A practitioner correction worth quoting: “Most people think 27001 is a security standard which it is not, it is an information security management system standard based on risk. Without guidance most people over do most controls or even have controls they do not need.” [Source: r/ISO27001, u/Natural_Zucchini_274, language source only]
- “The full control text is free online.” ISO sells the standard at CHF 155 (Swiss francs, list price as checked 13-08-2026); 27002 at CHF 227. The free Online Browsing Platform preview shows only limited sections, and in Ireland the identical text is adopted as I.S. EN ISO/IEC 27001:2023, which NSAI states has “no material differences between the content, requirements, or controls” and for which “[c]ertification to ISO/IEC 27001:2022 is therefore equivalent to certification to I.S. EN ISO/IEC 27001:2023”. [Source: iso.org standard pages, checked 13-08-2026; NSAI ISO/IEC 27001 page, checked 13-08-2026, verbatim]
For what a full certification costs once your control set is scoped, our ISO 27001 certification cost guide covers the published market figures.
FAQs
1. How many controls are in ISO 27001 Annex A?
93, in the current ISO/IEC 27001:2022 edition, organised under four themes: Organizational, People, Physical and Technological controls. The total is stated by NSAI, Ireland’s national standards body; the per-theme counts (37, 8, 14 and 34) are arithmetic from the published numbering ranges A.5.1 to A.8.34. The previous 2013 edition had 114 controls across 14 domains. [Source: NSAI ISO/IEC 27001 page, checked 13-08-2026; IS Partners and CertPro, checked 13-08-2026, tier 2]
2. Do we have to implement all 93 ISO 27001 Annex A controls?
No. You run a risk assessment, select the controls that treat your identified risks, and record every inclusion and exclusion with justification in the Statement of Applicability. Excluding controls is legitimate; claiming a control is implemented when it is not is what gets found at audit. [Source: CertPro and IS Partners on risk-based selection, checked 13-08-2026, tier 2; r/ISO27001 auditor answers, language source only]
3. What will the auditor actually check on Annex A controls?
Against your Statement of Applicability, auditors sample controls rather than testing all 93: they look at whether each selected control is designed for the risk, whether evidence shows it operating, and whether it works consistently over time. Practitioner forum answers add that auditors expect implementation of everything not explicitly justified as excluded, and that recurring findings are SoA overclaims, clear desk and clear screen, and weak mapping of risks back to controls. [Source: CertPro, checked 13-08-2026, tier 2; r/ISO27001 auditor thread, language source only]
4. Which Annex A controls actually apply to a cloud-native software company with no office?
The technological theme (A.8) and the cloud services control (A.5.23) carry the weight, alongside the people theme’s remote working control (A.6.7). Most of the physical theme (A.7) can be excluded with justification where no premises or on-premises infrastructure exist, though disposal, media handling and clear desk expectations usually survive. Practitioners running fully remote companies describe exactly this descoping, keeping a short physical policy for coworking and home working. [Source: r/ISO27001 “SaaS heavy organisations?” thread, captured 13-08-2026, language source only]
5. How much of Annex A is mapping what we already do versus actual new work?
Mostly mapping, for a company with reasonable existing security practice. One practitioner answer put it: “In my experience, most of the early effort is translation not transformation… The work comes from making implicit practices explicit and documenting ownership, scope and intent in a way an external assessor can follow.” The genuinely new work concentrates where you have no artefact at all, typically the risk assessment chain, the SoA itself, and any 2022-era controls your practice does not yet cover. [Source: r/ISO27001, u/Playful-Dress-2287, mapping thread, captured 13-08-2026, language source only]
6. Is penetration testing a requirement of ISO 27001?
No control in Annex A mandates penetration testing; the relevant control is A.8.8 Management of technical vulnerabilities, and how you meet it follows from your risk assessment. Practitioners note that pen testing is usually a client requirement that gets confused with a standard requirement, and that some auditors push it harder than the text supports. If your risks or your customers call for one, do one; do not treat it as a certification checkbox. [Source: r/ISO27001 over-interpreted control thread, captured 13-08-2026, language source only]
7. What is the difference between ISO 27001 Annex A and ISO 27002?
Annex A is the normative control reference inside ISO/IEC 27001; ISO/IEC 27002:2022 is a separate guidance standard explaining how to implement the controls. ISO’s own FAQ says 27002 “provides best practice recommendations and cannot be certified to”, and that organisations certify to 27001, which references 27002 guidance. Claims that 27002 is “an annex” of 27001 are wrong. [Source: iso.org ISO/IEC 27002:2022 page FAQ, checked 13-08-2026, verbatim]
8. What changed in Annex A in the 2022 edition?
The 2022 edition moved Annex A from 114 controls in 14 domains to 93 controls in four themes, merging overlapping controls and adding new ones around threat intelligence, cloud services, ICT continuity, data handling (deletion, masking, leakage prevention), monitoring and secure coding. Sources disagree on the exact new-control count (11 versus 12), so treat any precise number with caution until checked against the standard. The 2013 edition’s transition period is reported to have ended on 31 October 2025. [Source: IS Partners and CertPro, checked 13-08-2026, tier 2; transition date via Cybernion, SureCloud and dSalta, tier 2, unconfirmed against iaf.nu]
Next step
If the list above tells you one thing, it is that the hard part is not the 93 controls; it is the risk assessment that selects them and the evidence that proves the ones you selected. Atoro delivers ISO 27001 implementation for software companies across the UK and Ireland, starting from your risk profile rather than a template, and we will tell you honestly which parts of Annex A you can exclude. If you are further along, our internal audit requirements guide covers the clause 9.2 check you will need before certification.
Sources
Tier 1:
- NSAI (National Standards Authority of Ireland), ISO/IEC 27001 page (“Annex A of the standard contains 93 information security controls organised under four themes”; Irish adoption I.S. EN ISO/IEC 27001:2023 equivalence statements), checked 13-08-2026.
- ISO, ISO/IEC 27001:2022 standard page (bibliographic facts: Edition 3, published 2022-10, 19 pages, CHF 155 Swiss francs list price as checked 13-08-2026; Amd 1:2024 listed free; ISO Survey 2021/2022 certificate figures), checked 13-08-2026.
- ISO, ISO/IEC 27002:2022 standard page and FAQ (relationship and certification verbatim quotes; 152 pages, CHF 227 Swiss francs), checked 13-08-2026.
- EN ISO/IEC 27001:2023 table of contents via licensed reseller preview (clause 4-10 structure with subclause titles; Annex A listed as “(normative) Information security controls reference”; European foreword “approved by CEN-CENELEC as EN ISO/IEC 27001:2023 without any modification”), checked 13-08-2026; 6.3 and clause 10 order confirmed via the SIST Slovenian national TOC on the same preview.
- ISO/IEC 27001:2013 preview contents via iTeh (2013 annex structure “Annex A (normative) Reference control objectives and controls”), checked 13-08-2026.
Tier 2 (provider named, date checked):
- HighTable (UK consultancy, Stuart Barker), “The ISO 27001 Annex A Controls List” (full 93-control list; cross-check source 1; retrieved text skips A.8.28 between A.8.27 and A.8.29), checked 13-08-2026.
- CertPro (CertPro CPA LLC, US), “ISO 27001 Controls List” (full 93-control list with per-control summaries; cross-check source 2; auditor evaluation dimensions; 11 new controls table including A.5.21), checked 13-08-2026.
- IS Partners (US CPA/audit firm), “How Many Controls Are in ISO 27001” (93 controls, four themes with counts; 11 new controls list excluding A.5.21, including A.8.23; 114/14 for 2013), checked 13-08-2026.
- Cybernion (AU consultancy), SoA guide (SoA at clause 6.1.3 d) with four contents), checked 13-08-2026; corroborated by SecureSlate, and Security Compliance Guide, both checked 13-08-2026.
- SureCloud (Amd 1:2024 climate amendment description; 31 October 2025 transition date), checked 13-08-2026; transition date also asserted by Cybernion and dSalta, checked 13-08-2026.
- atoro.io (“more than 200 certifications delivered across security and compliance”), checked 08-08-2026.
Language sources only (never cited as fact):
- r/ISO27001, “What’s the Most Over Interpreted Control in Annex A” (checklist misconception, pen testing, SIEM over-interpretation, risk-based treatment quotes), captured 13-08-2026.
- r/ISO27001, “Where have you been found noncompliant within the Annex A controls?” (SoA overclaim finding; auditor sampling expectations; clear desk, risk mapping, 5.23 findings), captured 13-08-2026.
- r/ISO27001, “Mapping ISO 27001 controls to what you already do” (translation not transformation; rebuild relief; “Annex A does not get you certified”; checklist-focus warning), captured 13-08-2026.
- r/ISO27001, “SaaS heavy organisations?” (physical descoping; coworking policy; SoA removal mechanism), captured 13-08-2026.
- r/ISO27001, “How are small teams practically mapping ISO 27001 controls without overcomplicating it?” (team of 2, checklists and calendar reminders), captured 13-08-2026. Note: the thread OP links their own GRC tool in-thread and stays vendor-flagged; only the in-house implementer’s answer is quoted.
- r/ISO27001, “ISO 27001 control dependencies” (stale access-review spreadsheet; risk assessment and SoA as roots), captured 13-08-2026.
Atoro supplied facts: Atoro’s positioning as an Irish AI governance and cyber compliance consultancy for software companies; first consultancy in Europe certified against ISO 42001; certificate AIMS-AT-120224 (A-LIGN, ANAB accreditation); ISO 27001 implementation and internal audit services across the UK and Ireland.