The Statement of Applicability (SoA) is often described as the heartbeat of your Information Security Management System (ISMS). While the risk assessment identifies the ’why’, the SoA defines the ’what’ and the ’how’. It is the single most important document during your certification audit and the definitive roadmap for your internal security operations.<\/p>\n\n\n\n
At Instant 27001, we believe compliance shouldn’t be a manual burden. We help you move from static, error-prone spreadsheets to a dynamic, automated SoA that evolves with your business.<\/p>\n\n\n\n
A common misconception is that the SoA is merely a checkbox for the auditor. In reality, a well-crafted SoA acts as a strategic filter for your organisation:<\/p>\n\n\n\n
If you are pursuing ISO 27001 certification, the SoA isn’t optional. It’s the core requirement. But its utility extends far beyond the compliance department:<\/p>\n\n\n\n
In the 2022 update, ISO 27001 underwent a massive architectural shift. The standard moved away from the fragmented 14-domain structure of the past, consolidating 114 controls down to 93 modern security measures. These controls are now organized into four logical themes. This restructuring isn’t just about brevity; it\u2019s about aligning information security with the way modern, cloud-first businesses actually operate.<\/p>\n\n\n\n
The definition<\/strong> The shift<\/strong> The business advantage<\/strong> Critical controls to watch:<\/strong><\/p>\n\n\n\n The definition<\/strong> The shift<\/strong> The business advantage<\/strong> Critical controls to watch:<\/strong><\/p>\n\n\n\n The definition<\/strong> The shift<\/strong> The business advantage<\/strong> Critical controls to watch:<\/strong><\/p>\n\n\n\n The definition<\/strong> The shift<\/strong> The business advantage<\/strong> Critical controls to watch:<\/strong><\/p>\n\n\n\n Manually mapping these 93 controls to your specific risks is a recipe for error. Instant 27001 automates this mapping, providing you with a pre-configured framework where these controls are already translated into actionable tasks.<\/p>\n\n\n\n Ready to see the 93 controls in action?<\/p>\n\n\n\n One of the most frequent points of confusion in ISO 27001 is the difference between these two documents. While they are inextricably linked, they serve fundamentally different purposes.<\/p>\n\n\n\n Important note:<\/strong> you cannot have a compliant SoA without a thorough Risk Assessment, and you haven’t ”treated” your risks until they are mapped in the SoA. A ”Solid SoA” is not a static document; it is the result of a rigorous, repeatable process.<\/p>\n\n\n\n You don’t select controls because they sound good; you select them because they solve a problem. Every ”Applicable” control in your SoA should have a direct lineage back to a risk identified in your assessment.<\/p>\n\n\n\n ISO 27001 doesn’t require you to be perfect from day one, but it does require honesty. We categorise controls as:<\/p>\n\n\n\n Before finalising, you must cross-reference your selection against the full Annex A list. This ”sanity check” ensures that in your focus on specific risks, you haven’t missed a foundational security requirement.<\/p>\n\n\n\n The manual era of ISO 27001 is over. Instant 27001 provides a high-velocity environment to manage your SoA:<\/p>\n\n\n\n While you can share a template, each legal entity or specific scope usually needs its own SoA to reflect its unique risk environment and local regulations.<\/p>\n\n\n\n During an audit, this is usually classified as a major non-conformity. The SoA defines the scope of the certificate; missing a control means the ISMS certificate is fundamentally flawed.<\/p>\n\n\n\n Instant 27001 provides specific guidance for the 11 new controls (like data leakage prevention and monitoring activities), helping you determine if they apply to your current stack.<\/p>\n\n\n\n
Organizational controls serve as the ”Operating System” of your ISMS. They define the high-level logic, governance frameworks, and operational protocols that dictate how your entire company approaches security.<\/p>\n\n\n\n
ISO moved away from scattered compliance requirements to a unified governance model. By merging previously separate domains like ”Supplier Security” and ”Security Organization,” the standard now aligns directly with global risk management methodologies like ISO 31000.<\/p>\n\n\n\n
This pillar eliminates ”policy overlap,” reducing administrative bloat. For leadership, it provides a single, coherent framework for decision-making, ensuring that security is a boardroom priority rather than an IT-only concern.<\/p>\n\n\n\n\n
\u00a02. People controls (8 controls)<\/h3>\n\n\n\n
Organizational controls serve as the ”Operating System” of your ISMS. They define the high-level logic, governance frameworks, and operational protocols that dictate how your entire company approaches security.<\/p>\n\n\n\n
ISO moved away from scattered compliance requirements to a unified governance model. By merging previously separate domains like ”Supplier Security” and ”Security Organization,” the standard now aligns directly with global risk management methodologies like ISO 31000.<\/p>\n\n\n\n
This pillar eliminates ”policy overlap,” reducing administrative bloat. For leadership, it provides a single, coherent framework for decision-making, ensuring that security is a boardroom priority rather than an IT-only concern.<\/p>\n\n\n\n\n
3. Physical controls (14 controls)<\/h3>\n\n\n\n
Physical controls protect the tangible assets like, facilities, hardware, and infrastructure, that house your digital data. This includes everything from office entry points to the security of home-office workstations.<\/p>\n\n\n\n
This pillar has been modernized for the Hybrid Work Era. It acknowledges that the ”office” is no longer a single building, but a distributed network of home offices, coworking spaces, and data centers.<\/p>\n\n\n\n
By securing the ”Physical-Digital” intersection, you ensure that high-value intellectual property is protected regardless of where your team is working. It provides a standardized framework for managing the risks of a borderless workforce.<\/p>\n\n\n\n\n
4. Technological controls (34 controls)<\/h3>\n\n\n\n
Technological controls are the digital ”locks and keys” of your infrastructure. This pillar focuses on technical implementations like encryption, network security, and secure software development.<\/p>\n\n\n\n
The 2022 update introduces ”Privacy by Design.” It adds technical mandates for data masking and leakage prevention that didn’t exist in the 2013 version, aligning the standard with modern cyber threats like ransomware and SaaS exploits.<\/p>\n\n\n\n
For tech companies, this pillar is the ultimate ”Trust Builder.” It proves to your clients that your software is built securely (Secure Coding) and that their sensitive data is technically shielded from unauthorized access or accidental transfer.<\/p>\n\n\n\n\n
\n\n\n\nWhy managing controls with Instant 27001 matters\u00a0<\/h2>\n\n\n\n
\n\n\n\nThe strategic divide: SoA vs. Risk Assessment report<\/h2>\n\n\n\n
Feature<\/th> Risk Assessment Report (RAR)<\/th> Risk Assessment Report (RAR)<\/th><\/tr><\/thead> Primary goal<\/strong><\/td> To identify vulnerabilities and threats to your information assets.<\/td> To declare which security controls are in place to mitigate those risks.<\/td><\/tr> Focus<\/strong><\/td> ”The problem”: what could go wrong?<\/td> ”The solution”: what are we doing about it?<\/td><\/tr> Content<\/strong><\/td> A list of assets, threats, vulnerabilities, and their impact\/likelihood levels.<\/td> A definitive list of the 93 Annex A controls with justifications for each.<\/td><\/tr> Audience<\/strong><\/td> Primarily internal (risk owners and management).<\/td> Both internal and external (auditors, partners, and clients).<\/td><\/tr> The relationship<\/strong><\/td> The RAR provides the input for the SoA.<\/td> The SoA provides the output of your security decisions.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\nThe SoA cycle: 4 steps to audit success asked questions<\/h2>\n\n\n\n
<\/strong><\/strong>Step 1: the risk-control calibration<\/strong><\/h3>\n\n\n\n
<\/strong><\/strong><\/strong>Step 2: the strictness of justification<\/strong><\/h3>\n\n\n\n
\n
<\/strong><\/strong><\/strong><\/strong>Step 3: the reality check (implementation status)<\/strong><\/h3>\n\n\n\n
\n
<\/strong><\/strong><\/strong><\/strong><\/strong>Step 4: the cross-reference check<\/strong><\/h3>\n\n\n\n
\n\n\n\nHow Instant 27001 reduces the complexity<\/h2>\n\n\n\n
\n
\n\n\n\nFrequently asked questions<\/h2>\n\n\n\n
Can we have a ”generic” SoA for the whole group?<\/h3>\n\n\n\n
What happens if we miss a control in the SoA?<\/h3>\n\n\n\n
How do we handle ”new” controls in the 2022 update?<\/h3>\n\n\n\n