ISO 27001 Statement of Applicability: Requirements Guide

The Statement of Applicability (SoA) is the document ISO/IEC 27001:2022 makes you produce when you plan risk treatment: it records which of Annex A’s 93 controls you have determined necessary, why each one is included, whether it is implemented, and why any control was excluded. The requirement sits in clause 6.1.3, “Information security risk treatment”, and the SoA is the single document an external audit tests your control decisions against. The clause 6.1.3 title is confirmed in the standard’s published table of contents; the item d) location and the four required contents are corroborated by three independent practice sources, because ISO’s free online preview was inaccessible from our research environment. [Source: contents page of EN ISO/IEC 27001:2023 via licensed reseller preview (identical text to ISO/IEC 27001:2022), checked 13-08-2026, tier 1 for clause titles; Cybernion; SecureSlate; Security Compliance Guide, all checked 13-08-2026, tier 2 for item d) and the four contents; 93 controls in four themes: NSAI, checked 13-08-2026, tier 1]

If you have just been told you need an SoA, you are probably mid-implementation and this page is written for you. It assumes nothing beyond that.

The SoA requirement at a glance

One clause requires the document, and four contents make it complete. Everything else on this page is about making those four contents defensible.

WhatThe requirementWhere it comes from
Requirement locationClause 6.1.3, “Information security risk treatment”, item d)Clause title: EN ISO/IEC 27001:2023 table of contents (tier 1); item d): corroborated by Cybernion, SecureSlate and Security Compliance Guide (tier 2, all checked 13-08-2026)
Content 1The necessary controlsTier 2 corroboration as above
Content 2Justification for each inclusionTier 2 corroboration as above
Content 3Whether each control is implementedTier 2 corroboration as above
Content 4Justification for each exclusion of an Annex A controlTier 2 corroboration as above
The control set it appliesAnnex A: 93 controls across four themes (organisational, people, physical, technological)NSAI (tier 1, checked 13-08-2026); Annex A is the normative “Information security controls reference” per the standard’s table of contents (tier 1)
Document controlThe SoA is documented information and must be controlled under clause 7.5.3, “Control of documented information”Clause title: EN ISO/IEC 27001:2023 table of contents (tier 1); change-log practice: Security Compliance Guide (tier 2, checked 13-08-2026)

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 (certificate AIMS-AT-120224, issued by A-LIGN under ANAB accreditation). Our own site records more than 200 certifications delivered across security and compliance, and we deliver ISO 27001 implementation for software companies across the UK and Ireland, so the SoA mechanics below are documents we write and defend with clients, not theory. [Source: atoro.io, checked 08-08-2026]

Where ISO 27001 requires the Statement of Applicability

Clause 6.1.3, “Information security risk treatment”, is where the SoA requirement lives, at item d). The clause title is confirmed in the standard’s published table of contents; the item letter and its four contents are corroborated by three independent practice sources because ISO’s free Online Browsing Platform preview returned access errors during our research.

The placement tells you something most template pages do not: the SoA is not a clause 4 context document or a clause 5 leadership document. It sits inside risk treatment, which sits inside planning (clause 6), directly after the risk assessment clause (6.1.2, “Information security risk assessment”). The standard’s table of contents shows both, in that order. [Source: contents page of EN ISO/IEC 27001:2023 via licensed reseller preview, checked 13-08-2026, tier 1]

That ordering is the spine of a defensible SoA, and it is the subject of the next section.

A note on editions before you go further. The current edition is ISO/IEC 27001:2022, published October 2022, with 93 Annex A controls in four themes. [Source: iso.org standard page, checked 13-08-2026, tier 1; NSAI, checked 13-08-2026, tier 1] In Ireland it is adopted as I.S. EN ISO/IEC 27001:2023, and NSAI states there are “no material differences between the content, requirements, or controls” of the two and that certification to one is equivalent to certification to the other. [Source: NSAI, checked 13-08-2026, tier 1] Templates for the withdrawn 2013 edition (114 controls) and its EN 2017 adoption are still being sold and given away; the transition period for the 2013 edition closed on 31 October 2025, so an SoA built on a 114-control template is built on a dead edition. [Source: ICT Institute free templates page; HighTable SoA product page; both checked 13-08-2026, tier 2, both still carrying pre-2022 versions; transition date per IAF, IAF MD26 MLA-scope transition table, checked 14-08-2026, tier 1]

Risk assessment comes first: the SoA is an output, not a starting document

The SoA is the output of your risk assessment and risk treatment decisions, not a document you start from. If you write the SoA before the risk assessment, you have produced a list of controls with invented justifications, and that is exactly what auditors probe.

This is the strongest point on the current search results page, made by the Australian consultancy Cybernion, and it deserves repeating: the SoA records decisions already taken in risk treatment, so its entries trace back to something. [Source: Cybernion, checked 13-08-2026, tier 2] A practitioner on r/ISO27001 put the same dependency plainly: “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]

In practice the chain looks like this:

  1. Assess risk (clause 6.1.2). Identify your information security risks, analyse them, evaluate them against your risk criteria. Clause title from the published table of contents, tier 1.
  2. Treat risk (clause 6.1.3). Decide which risks you treat with controls, and which controls treat them: Annex A controls, controls from elsewhere, or controls you design yourself.
  3. Record it in the SoA (clause 6.1.3 d). Every control determined necessary goes in with its justification and implementation status; every Annex A control you leave out gets a written reason.
  4. Repeat in operation. Clauses 8.2 and 8.3 (“Information security risk assessment” and “Information security risk treatment”) repeat the cycle operationally, which is why the SoA is never finished. Clause titles from the published table of contents, tier 1. [Source for clause titles in this chain: contents page of EN ISO/IEC 27001:2023 via licensed reseller preview, checked 13-08-2026, tier 1]

The practical mechanics can be simple. One practitioner described building it straight from a spreadsheet: “For me I would start just excel, annex A controls and map towards the organization is doing. Make a simple status (for example 10,25,50,75 and fully implemented). List the actions in a different sheet and link them. It gives you your SoA.” [Source: r/ISO27001, u/MisterD05, captured 13-08-2026, language source only] The tool does not matter. The traceability does.

The four required contents, and what a defensible entry looks like

Three independent practice sources agree on the four contents clause 6.1.3 d) requires: the necessary controls, justification for inclusions, implementation status, and justification for exclusions of Annex A controls. Here is what a defensible entry looks like for each. [Source: Cybernion; SecureSlate; Security Compliance Guide; all checked 13-08-2026, tier 2 corroboration]

1. The necessary controls

List every control your risk treatment determined necessary. That is the Annex A controls you need, plus any controls you adopted from outside Annex A, plus any you designed yourself. The cleanest working format lists all 93 Annex A controls, one per row, so inclusion and exclusion are both explicit rather than implied by absence. The four-theme structure (37 organisational, 8 people, 14 physical, 34 technological controls, totalling 93) gives you the rows. [Source: NSAI states 93 controls in four themes, checked 13-08-2026, tier 1; per-theme 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 visible in the HighTable control list, checked 13-08-2026, tier 2; the arithmetic is ours: 37 + 8 + 14 + 34 = 93]

2. Justification for each inclusion

“Included because Annex A says so” is not a justification. A defensible inclusion points to the reason the control is necessary: a risk from your assessment it treats, a legal or contractual requirement it meets, or a business requirement. The test is whether an auditor can follow the line from your risk register to the control and back. A practitioner describing what makes an SoA hold up wrote: “If a control is applicable/selected the reasoning for that must be documented in the SoA.” [Source: r/ISO27001, u/BBQQueue, nonconformity thread, captured 13-08-2026, language source only]

3. Implementation status

State, honestly, whether each included control is implemented. Overstating this is the fastest way to turn a Stage 2 audit against you: the auditor will sample included controls and ask for evidence that what the SoA claims is real. The same practitioner’s advice: “For controls that are applicable/selected state in the SoA the current level of implementation or at least that they are implemented… Ensure that any policies, processes and procedures related to enabled controls are being followed. Be able to demonstrate [it] if asked.” [Source: r/ISO27001, u/BBQQueue, as above, language source only] A status like “implemented”, “partially implemented” or “planned, due [date]” with an owner is defensible; a column of uniform “yes” is not, unless it is true.

4. Justification for each exclusion

Every Annex A control you exclude needs its own written reason. “If a control is excluded a good justification must be documented in the SoA.” [Source: r/ISO27001, u/BBQQueue, as above, language source only] The justification that survives audit is applicability-based: the control addresses an asset, activity or environment that does not exist inside your scope. The justification that fails is convenience-based: the control is expensive, awkward or simply not done yet. Cybernion’s guide, the strongest current page on this keyword, documents exclusion-justification problems as a real source of audit findings. [Source: Cybernion, checked 13-08-2026, tier 2]

A worked entry (illustrative example, not a template)

ControlNecessary?JustificationImplemented?
A.5.23 Information security for use of cloud servicesYesProduct and customer data hosted on a public cloud provider; risk register items R-04 and R-07 (illustrative references) require controls over cloud acquisition, use and exitYes: cloud service management process documented and operating
A.7.4 Physical security monitoringNoOrganisation is fully remote with no owned or leased premises; no organisational facility exists to monitor. Physical security of the hosted environment rests with the cloud provider and is addressed under A.5.21 and A.5.23 inclusionsn/a

The exclusion row shows the pattern: it does not say “we have no office so physical security does not matter”. It says the specific thing this control addresses does not exist in scope, and it shows where the residual physical risk actually went. Control names A.5.21 (managing information security in the ICT supply chain), A.5.23 (information security for use of cloud services) and A.7.4 (physical security monitoring) are 2022-edition controls named consistently across multiple published sources. [Source: control names per IS Partners, CertPro and other tier 2 pages, checked 13-08-2026]

Which controls a software company can exclude, and how to justify it

For a fully remote, cloud-hosted software company, the A.7 physical controls are the legitimate exclusion candidates, and even they are rarely excludable as a whole theme. Justify exclusions by what does not exist in your scope, never by what is inconvenient.

The honest version of the exclusion conversation looks like this. You have no premises, so controls about securing physical premises have nothing to act on. But your company still runs on laptops in homes and rented desks, and your data still sits in a data centre somewhere. The physical risk did not disappear; it moved to your staff’s home working environment and to your cloud provider. So the defensible pattern is: exclude the specific premises-based controls with applicability justifications, and keep (or add) the controls that address where the risk actually went, which for a cloud-hosted company means supplier and cloud controls such as A.5.21 and A.5.23.

An in-house implementer on r/ISO27001 described exactly this puzzle: “I am trying to work out if a company’s ISO scope states that the physical security of non-business locations is out of scope but it has all remote working, and uses their accountant as a Head Office address that handles their post etc how does that get audited by the ISO auditor? I understand that the Statement of Applicability would reflect that certain physical controls would not be applicable but what about the address on the certificate? How does that work if the auditor does not/cannot check it or do they have to?” [Source: r/ISO27001, u/widgey27, captured 13-08-2026, language source only] It is a real question with no tidy forum answer, which is a good reason to settle your exclusion logic with your certification body before Stage 1, not during it.

Two boundaries hold in every case:

  • Never exclude a control because it is inconvenient. “We do not want to do this” is not a justification; it is an admission. If a control treats a real risk and you have not implemented it, the honest entry is “necessary, planned”, with a date.
  • Risk acceptance alone is shaky ground for exclusion. A practitioner asked the question precisely: “Where a risk exposure has been assessed as within the organisation’s defined risk acceptance or tolerance criteria, can this assessment be used to justify excluding associated control(s) from the Statement of Applicability under ISO/IEC 27001?” The thread did not settle it. [Source: r/ISO27001, u/Dockers-Man, captured 13-08-2026, language source only] The safe reading: risk acceptance is a treatment decision you make after considering controls, not a reason the control was never applicable. Expect an auditor to probe any exclusion whose only basis is tolerance.

At the other extreme, some exclusions are simply not credible for a software company. A.8.28 Secure coding is a 2022-edition control aimed squarely at organisations that build software; excluding it while selling software would invite questions you cannot answer. [Source: A.8.28 Secure coding corroborated as a real 2022-edition control by three independent tier 2 sources, checked 13-08-2026]

ISO 27001 vs ISO 27002: the annex error to avoid

ISO/IEC 27002 is a separate guidance standard, not an annex of ISO 27001, and you cannot be certified to it. The normative control set your SoA applies is Annex A of ISO 27001 itself.

This matters because a ranking product page selling an SoA template gets it wrong, verbatim: “The ISO 27001 statement of applicability is the list of information security controls contained within ISO 27002. ISO 27002 is an annex to ISO 27001 and a requirement of ISO 27001.” [Source: HighTable SoA product page, checked 13-08-2026, tier 2, quoted to correct it] Both sentences are wrong. ISO’s own 27002 page states the relationship in its FAQ: “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.” And 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 standard page FAQ, checked 13-08-2026, tier 1]

The practical reading: Annex A of ISO 27001 is the normative reference control set your SoA selects from and justifies against (“Annex A (normative) Information security controls reference”, per the standard’s table of contents, tier 1). ISO/IEC 27002:2022 is the 152-page guidance volume that explains how to implement each control; use it as an implementation reference, buy it if it helps (list price CHF 227, Swiss francs), but nobody certifies you against it. [Source: iso.org, ISO/IEC 27002:2022 standard page, checked 13-08-2026, tier 1]

The confusion is common. A buyer-side implementer asked: “Why there is ISO27002? Is this the same standard (same controls) and do I have to implement it as well?” A Lead Auditor’s answer captures the working position: “The ISO 27001 annex only has the high level description and ISO 27002 contains all the implementation guidelines. These are useful for implementers but are not formally part of the certification process.” [Source: r/ISO27001, u/paolokoelio question and Lead Auditor answer, captured 13-08-2026, language source only]

The SoA through Stage 1, Stage 2 and surveillance: a living document

The SoA is drafted before Stage 1, tested at Stage 2, and expected to change between audits. Because it is documented information, clause 7.5.3’s control-of-documented-information discipline applies to it: versions, approvals and change history.

At Stage 1, the auditor reviews your documented information, and the SoA is one of the documents they read first because it tells them how you see your own control set. A first-time implementer described the moment: “We’ve drafted a few key documents like our security policies, risk assessment approach, and Statement of Applicability. But since this is our first time going through it, we’re not sure what we might be missing. If you’ve done this before as a startup, what did your auditor focus on during Stage 1? Were there common issues or gaps they called out?” [Source: r/ISO27001, u/LevelFormal1459, captured 13-08-2026, language source only] At Stage 2, the SoA becomes the sampling plan: included controls are where the auditor asks for operating evidence, and exclusions are where they test your reasoning.

After certification, surveillance audits expect the SoA to reflect the ISMS as it actually is, not as it was at Stage 1. The triggers that should send you back to the document are the ones the clause structure itself names: repeated risk assessment and treatment in operation (clauses 8.2 and 8.3), planned changes (clause 6.3, “Planning of changes”, new in the 2022 edition), management review outputs (clause 9.3), and nonconformities with corrective action (clause 10.2). [Source: clause titles from the contents page of EN ISO/IEC 27001:2023 via licensed reseller preview, checked 13-08-2026, tier 1] Each revision is a controlled document change: clause 7.5.3 is titled “Control of documented information” (tier 1), and one current guide’s practical tip, keeping a change log on the SoA tied to clause 7.5.3, is the right habit. [Source: Security Compliance Guide, checked 13-08-2026, tier 2]

The internal audit is where you test SoA consistency before the certification body does: does the SoA match the risk register, and does reality match the SoA? Our ISO 27001 internal audit requirements guide covers that audit in depth.

Common failure points

The failures below are the ones practitioners and current guides actually describe. They cluster around ordering, honesty and stale editions.

  • Writing the SoA before the risk assessment. The justifications have nothing to trace to, and the document becomes a list of controls with invented reasons. This is the ordering error covered above, and it is the most structural failure on this keyword.
  • Boilerplate justifications. The same sentence pasted against 60 controls tells the auditor none of them was thought about. A Lead Auditor’s framing for small teams is the better instinct: “A lot of early-stage teams find that a lightweight Statement of Applicability helps them justify which controls they’re adapting or excluding, which keeps auditors happy without going overboard.” [Source: r/ISO27001, u/Head_Personality_431, captured 13-08-2026, language source only]
  • Overstated implementation status. Claiming “implemented” for controls that are policies on paper with no operating evidence turns the SoA into the auditor’s list of nonconformities. Status honesty, with planned dates, is the defensible position.
  • Excluding physical controls with no supplier story. Fully remote companies that cross out the A.7 theme without showing where the physical risk went (home working, cloud provider) leave the obvious question unanswered.
  • Building on a withdrawn edition. Templates for the 2013 edition and EN 2017 adoption are still being distributed, including one free library offering a “Statement of applicability ISO27001-2017” template alongside 2022 material, and one paid template still sold in a dual 2013/2022 version after the transition closed. [Source: ICT Institute; HighTable product page; both checked 13-08-2026, tier 2] Check any template against the 93-control, four-theme structure before you touch it. [Source: NSAI, checked 13-08-2026, tier 1]
  • Treating the template as the deliverable. Current ranking pages bundle the SoA with free or paid Excel templates, one self-described as “fully meets the requirements”. [Source: HighTable guide page, checked 13-08-2026, tier 2, self-asserted] A template gives you columns. It cannot give you justifications, because those are your risk decisions.

What the Statement of Applicability is not

Three confusions account for most of the bad SoAs we see described. The document is not a purchased template, not your risk register, and not your risk treatment plan.

  • Not a template you buy and fill in. A blank structure is a fine starting grid; SecureSlate’s free workbook, for example, pre-loads all 93 controls and walks the workbook tab by tab. [Source: SecureSlate, checked 13-08-2026, tier 2] But the four required contents are decisions only you can take, and a pre-filled justification column is someone else’s risk assessment wearing your letterhead.
  • Not the risk register. The risk register records identified risks, their analysis and evaluation. The SoA records control decisions. The register feeds the SoA; neither replaces the other. SecureSlate publishes a SoA-versus-risk-register-versus-risk-treatment-plan comparison, and Cybernion’s guide covers the SoA-versus-risk-treatment-plan distinction directly. [Source: SecureSlate; Cybernion; both checked 13-08-2026, tier 2]
  • Not the risk treatment plan. The treatment plan records what you will do and when; the SoA records which controls are necessary, why, and their status. Auditors read them together and test that they agree.
  • Not ISO 27002. Covered above: a separate guidance standard, not an annex, not certifiable. [Source: iso.org, ISO/IEC 27002:2022 standard page FAQ, checked 13-08-2026, tier 1]

If what brought you here is actually the commercial question (what the whole certification costs, SoA work included), our ISO 27001 certification cost guide covers the published market figures.

FAQs

1. What is a Statement of Applicability in ISO 27001?

It is the document your ISMS produces when you plan risk treatment: which of Annex A’s 93 controls you have determined necessary, why each is included, whether each is implemented, and why any control was excluded. It is the document an external audit tests your control decisions against. The four contents are corroborated by three independent practice sources (Cybernion, SecureSlate, Security Compliance Guide, all checked 13-08-2026); the 93-control set is confirmed by NSAI, Ireland’s national standards body.

2. Where in ISO 27001 is the Statement of Applicability required?

In clause 6.1.3, “Information security risk treatment”, at item d). The clause title is confirmed in the standard’s published table of contents (EN ISO/IEC 27001:2023, identical text to ISO/IEC 27001:2022). The item d) location is corroborated by three independent practice sources, because ISO’s free preview was inaccessible during our research; we attribute it to those sources rather than to ISO directly.

3. Do we have to implement every Annex A control?

No. You determine which controls are necessary through risk treatment, include them with justification, and justify every Annex A control you exclude. Exclusions are normal for software companies, especially among the physical controls, but each one needs its own applicability-based reason. “It is inconvenient” is not a reason that survives an audit.

4. Which controls can a fully remote software company exclude?

The A.7 physical controls are the legitimate exclusion candidates when you own or lease no premises. The justification must name what does not exist (no organisational facility) and show where the risk went: home working equipment and your cloud provider’s physical security, which your supplier and cloud controls (A.5.21, A.5.23) address. Excluding the physical theme wholesale, with no supplier assurance story, is the version that fails.

5. Can we exclude a control because we have accepted the risk?

Risk acceptance alone is shaky ground. A practitioner asked this exact question on r/ISO27001 and the thread did not settle it, which matches what we see in practice: auditors probe exclusions whose only basis is tolerance. The stronger position is that acceptance is a treatment decision made after considering controls, recorded in the risk treatment plan, while SoA exclusions rest on applicability. If the control addresses a real in-scope risk, expect to include it or to explain, concretely, why not.

6. What does the auditor actually check in the SoA at Stage 1?

Stage 1 reviews your documented information, and the SoA is read early because it shows how you see your own control set. Expect the auditor to test traceability (do SoA entries connect to the risk assessment?), exclusion logic (is each exclusion applicability-based?), and status honesty (does “implemented” match what Stage 2 sampling will find?). Version control under clause 7.5.3 also applies: the auditor should be able to see the SoA is a controlled document, not an untracked spreadsheet.

7. Can I trust a supplier’s ISO 27001 certificate, and should I ask for their SoA?

The certificate tells you the supplier’s ISMS was audited; the SoA tells you which controls they actually run, which is usually what you want to know. Buyers on r/ISO27001 ask exactly this, and the practitioner answers are consistent: for a certified supplier, check the SoA, and for uncertified ones, use a security questionnaire under your own third-party risk policy. Read a supplier’s SoA the way an auditor would: look for exclusions and their justifications, not just inclusions. [Language source: r/ISO27001 supplier review thread, captured 13-08-2026.]

8. Is the SoA the same as the risk register or the risk treatment plan?

No, and auditors test that the three agree. The risk register records risks and their evaluation; the risk treatment plan records the actions you will take; the SoA records which controls are necessary, why, and whether they are implemented. Inconsistency between them (a risk treated in the plan but missing from the SoA, or an SoA control with no risk behind it) is a classic audit finding.

Next step

If you are mid-implementation and the SoA is where the work has stalled, the block is usually upstream: the risk assessment has not produced decisions the SoA can record. Fix the ordering and the document writes itself. Atoro delivers ISO 27001 implementation for software companies across the UK and Ireland, including the risk assessment and SoA work described above, and we will tell you honestly if your existing risk work is closer to done than you think.

Sources

Tier 1:

  1. ISO, ISO/IEC 27001:2022 standard page (current edition, published 2022-10, list price CHF 155 Swiss francs), checked 13-08-2026.
  2. Contents page of EN ISO/IEC 27001:2023 via licensed reseller preview (CEN-CENELEC adoption, text “approved… without any modification” from ISO/IEC 27001:2022; clause 6.1.2 and 6.1.3 titles, clauses 6.3, 7.5.3, 8.2, 8.3, 9.3, 10.2 titles, Annex A “(normative) Information security controls reference”), checked 13-08-2026.
  3. NSAI (National Standards Authority of Ireland), ISO/IEC 27001 page (“Annex A of the standard contains 93 information security controls organised under four themes: Organisational controls, People controls, Physical controls, Technological controls”; Irish adoption as I.S. EN ISO/IEC 27001:2023 with “no material differences”; certification equivalence), checked 13-08-2026.
  4. ISO, ISO/IEC 27002:2022 standard page and FAQ (“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.”; “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.”; 152 pages, list price CHF 227 Swiss francs), checked 13-08-2026.
  5. Atoro, “What is ISO 42001?” (supplied figure: “more than 200 certifications delivered across security and compliance”), checked 08-08-2026.

Tier 2 (provider named, date checked):

  1. Cybernion (AU consultancy; named practitioner Gaurav Vikash), “ISO 27001 Statement of Applicability” (clause 6.1.3 d) and the four required contents; SoA as output of risk treatment; SoA vs risk treatment plan; exclusion-justification audit findings; 2013 transition closed 31 October 2025), checked 13-08-2026.
  2. SecureSlate, “ISO 27001 Statement of Applicability template” (clause 6.1.3(d); all 93 controls pre-loaded; SoA vs risk register vs risk treatment plan comparison), checked 13-08-2026.
  3. Security Compliance Guide, “ISO 27001 Statement of Applicability” (clause 6.1.3 d); SoA column structure; justification-writing method; change-log tip tied to clause 7.5.3), checked 13-08-2026.
  4. HighTable, “Statement of Applicability ISO 27001” guide (states mandatory under Clause 6.1.3 without the d) item; template self-described as “fully meets the requirements”), checked 13-08-2026.
  5. HighTable, SoA template product page (GBP 20.00, UK site; quoted factual error on ISO 27002, reproduced to correct; dual 2013/2022 template still sold post-transition), checked 13-08-2026.
  6. ICT Institute, free templates page (“Statement of applicability ISO27001-2017” template offered post-transition; version pollution example), checked 13-08-2026.
  7. IAF (International Accreditation Forum), IAF MD26 MLA-scope transition table (ISO/IEC 27001:2022 transition deadline 31 October 2025), checked 14-08-2026, tier 1.
  8. IS Partners, CertPro and other tier 2 pages (control names A.5.21, A.5.23, A.7.4, A.8.28; per-theme numbering ranges): checked 13-08-2026.
  1. Reddit r/ISO27001, “ISO 27001 stage 1” by u/LevelFormal1459, ~2025
  2. Reddit r/ISO27001, “Reviewing Supplier based on ISO27001” by u/Euphoric-Physics-768, ~2024 (answers by u/Spirited-Background4, u/SillyStallion, u/dogpupkus)
  3. Reddit r/ISO27001, “ISO27001 – Remote office advice please!” by u/widgey27, ~2023
  4. Reddit r/ISO27001, “Responsible for ISO 27001 implementation” by u/Funkki, ~Mar 2026 (ISO 27002 question by u/paolokoelio, Lead Auditor answer)
  5. Reddit r/ISO27001, “How are small teams practically mapping ISO 27001” (Lead Auditor answer by u/Head_Personality_431), ~Apr 2026
  6. Reddit r/ISO27001, “Where have you been found noncompliant” (u/BBQQueue defensibility breakdown; u/Dockers-Man risk-acceptance question), ~2025-2026
  7. Reddit r/ISO27001, “Mapping ISO 27001 controls to what you already do” (u/MisterD05 spreadsheet mechanics), ~Jan 2026
  8. Reddit r/ISO27001, “ISO 27001 control dependencies” (u/Snoo_29776 downstream quote), ~Jul 2026

Atoro supplied facts: Atoro’s positioning, first-in-Europe ISO 42001 certification claim, certificate AIMS-AT-120224 (A-LIGN, ANAB accreditation), ISO 27001 implementation service for software companies in the UK and Ireland.