ISO 27001 Statement of Applicability (SoA)

Selecting information-security controls is one of the most important decisions made during ISO 27001 implementation. A common misconception is that every organisation needs to implement all 93 Annex A controls.

ISO 27001 instead follows a risk-based approach.

The Statement of Applicability records which controls have been selected, which have been excluded, the justification for those decisions and how applicable controls have been implemented.

It therefore creates the connection between the Information Security Risk Assessment, the Risk Treatment Plan and the controls operating within the ISMS.

For both management and certification auditors, the SoA is one of the central documents explaining the organisation’s control strategy.

Key Takeaways

01

Which Annex A controls have been selected

02

Which controls have been excluded

03

The justification for those decisions

04

It links the results of the Information Security Risk Assessment to the Risk Treatment Plan and ultimately to the Annex A controls that have been implemented.

05

It is a practical management tool that helps organisations understand their security posture, communicate control decisions, support governance and maintain consistency as the Information Security Management System evolves.

06

In reality, ISO 27001 follows a risk-based approach, meaning organisations select only those controls that are appropriate for their identified information security risks, legal obligations and business objectives.

What You'll Learn

In this guide, you'll learn:

  • What an ISO 27001 Statement of Applicability is
  • Why the SoA is a mandatory document
  • What information a Statement of Applicability should contain
  • How the SoA links Risk Assessment, Risk Treatment and Annex A controls
  • How to develop and maintain an effective Statement of Applicability
  • Common mistakes organisations make when preparing an SoA
  • How a well-developed SoA supports ISO 27001 certification and continual improvement
Key takeaway: The Statement of Applicability is one of the cornerstone documents of an ISO 27001 Information Security Management System. It demonstrates how an organisation has selected and justified its Annex A controls based on identified information security risks, providing a clear link between Risk Assessment, Risk Treatment and certification readiness.

What Is an ISO 27001 Statement of Applicability?

The Statement of Applicability is one of the most important documents within an ISO/IEC 27001:2022 Information Security Management System.

In simple terms, it explains which information security controls your organisation has chosen to implement, which controls have been excluded and why those decisions have been made.

Rather than being a checklist of every Annex A control, the SoA demonstrates that control selection has been based on a structured Information Security Risk Assessment and Risk Treatment process.

Think of the Statement of Applicability as the document that tells the story behind your security controls.

It shows that each control has been selected because it addresses an identified information security risk or fulfils a legal, regulatory or contractual requirement, not because it was copied from a template or implemented without justification.

The Purpose of the Statement of Applicability

The primary purpose of the SoA is to provide documented evidence that the organisation has taken a risk-based approach to information security.

It records:

  • Which Annex A controls have been selected
  • Which Annex A controls have been excluded
  • The justification for each decision
  • How the selected controls have been implemented

This information provides management, auditors and other interested parties with confidence that the organisation's Information Security Management System has been developed systematically and that security controls are aligned with actual business risks.

The SoA Connects Risk Assessment to Annex A

One of the easiest ways to understand the Statement of Applicability is to see it as the bridge between identifying risks and implementing controls.

The relationship looks like this:

Information Security Risk Assessment → Risk Treatment → Select Annex A Controls → Statement of Applicability → Implement and Maintain Controls

Without the SoA, it would be difficult to demonstrate why specific controls have been implemented or why others have not.

This is why the Statement of Applicability is often regarded as the central document linking the organisation's Risk Assessment to its Annex A control selection.

More Than an Audit Document

Many organisations mistakenly view the Statement of Applicability as something created solely for certification audits.

In reality, it is an important management tool.

An effective SoA helps organisations to:

  • Understand their current information security controls
  • Communicate security decisions consistently
  • Support governance and management oversight
  • Demonstrate accountability
  • Track the implementation of security controls
  • Maintain consistency as the Information Security Management System evolves

As new risks emerge or business operations change, the SoA should be reviewed and updated to ensure it continues to reflect the organisation's current risk profile and security objectives.

Is the Statement of Applicability Mandatory?

Yes.

The Statement of Applicability is one of the key pieces of documented information required by ISO/IEC 27001:2022.

Certification auditors rely heavily on the SoA to verify that the organisation has selected Annex A controls based on identified information security risks rather than implementing controls arbitrarily.

Because of its importance, it is widely regarded as one of the cornerstone documents of an effective Information Security Management System.

Every Statement of Applicability Is Different

No two organisations will have identical Statements of Applicability.

A financial institution, software company, healthcare provider and manufacturer all face different information security risks, legal obligations and business objectives.

As a result, each organisation will select a different combination of Annex A controls.

For example:

  • A cloud software provider may place greater emphasis on identity management, secure development and supplier controls
  • A manufacturer may prioritise physical security, operational technology and business continuity
  • A professional services firm may focus on confidentiality, access control and document management

This flexibility is one of ISO 27001's greatest strengths.

Instead of prescribing a one-size-fits-all set of security controls, the standard allows organisations to develop an Information Security Management System that reflects their own operating environment and risk profile.

Why Is the Statement of Applicability Important?

The Statement of Applicability is much more than a mandatory ISO 27001 document.

It is one of the most valuable management tools within an Information Security Management System because it demonstrates how an organisation has translated the results of its Information Security Risk Assessment into practical security controls.

Rather than simply listing which Annex A controls have been implemented, the SoA provides the rationale behind those decisions, showing that the organisation has adopted a structured, risk-based approach to information security.

Demonstrates a Risk-Based Approach

One of the fundamental principles of ISO/IEC 27001:2022 is that information security controls should be selected based on risk.

The Statement of Applicability provides documented evidence that this principle has been applied.

It shows that the organisation has:

  • Conducted an Information Security Risk Assessment
  • Evaluated identified risks
  • Determined appropriate Risk Treatment actions
  • Selected Annex A controls that address those risks
  • Justified any controls that have been excluded

This helps demonstrate that security decisions have been made systematically rather than by applying a generic checklist or template.

Supports ISO 27001 Certification

During an ISO 27001 certification audit, the Statement of Applicability is one of the first documents an auditor is likely to review.

Auditors use the SoA to verify that:

  • Control selection is based on identified information security risks
  • Applicable Annex A controls have been implemented
  • Excluded controls have been appropriately justified
  • The organisation's Information Security Management System aligns with its scope and risk profile

Because the SoA links the Risk Assessment to the implemented controls, it provides auditors with a clear roadmap for evaluating the effectiveness of the Information Security Management System.

Provides a Single Source of Truth

As organisations grow, information security controls often become distributed across multiple policies, procedures, systems and departments.

The Statement of Applicability brings these decisions together into a single, structured document.

It provides a consolidated view of:

  • Which controls apply
  • Why they apply
  • Where they have been implemented
  • Who is responsible for them

This makes the SoA a valuable reference for management, Internal Auditors, implementation teams and certification auditors.

Strengthens Governance and Accountability

Good governance requires clear decisions and documented accountability.

The Statement of Applicability supports this by recording not only which controls have been selected, but also the business justification behind those decisions.

This enables senior management to understand:

  • The organisation's information security priorities
  • How risks are being managed
  • Why resources have been allocated to specific controls
  • How the Information Security Management System supports business objectives
Supports Consistent Control Management

Information security controls should not remain static.

New technologies, emerging cyber threats, organisational changes and updated legal or contractual requirements may all affect which controls are appropriate.

The Statement of Applicability provides a structured framework for reviewing and updating control decisions over time.

Improves Communication Across the Organisation

The Statement of Applicability helps stakeholders understand:

  • Which controls have been implemented
  • Why those controls are necessary
  • How they support organisational objectives
  • Where responsibilities lie

This improves communication and creates a shared understanding of the organisation's information security strategy.

Supports Continual Improvement

Keeping the SoA current helps organisations:

  • Identify gaps in control implementation
  • Respond to new information security risks
  • Incorporate lessons learned from incidents and audits
  • Support Management Reviews
  • Demonstrate continual improvement during certification audits
Delivers Business Value Beyond Certification

A well-maintained SoA helps organisations:

  • Make informed security decisions
  • Reduce duplicated or unnecessary controls
  • Improve operational consistency
  • Support customer and supplier assurance
  • Strengthen governance
  • Maintain alignment between business objectives and information security

ISO 27001 Statement of Applicability Requirements

The Statement of Applicability is a mandatory component of an ISO/IEC 27001:2022 Information Security Management System.

Although the standard specifies what the SoA must achieve, it does not prescribe a fixed template or format.

Organisations are free to structure the document in a way that best suits their business, provided it contains the required information and accurately reflects their Information Security Management System.

The Statement of Applicability Is Mandatory

During certification audits, the SoA provides evidence that the organisation has selected information security controls through a structured Information Security Risk Assessment and Risk Treatment process rather than implementing controls arbitrarily.

Without an accurate and up-to-date Statement of Applicability, organisations may find it difficult to demonstrate how their implemented controls address identified information security risks.

The SoA Must Be Based on Risk

The process should follow a logical sequence:

Information Security Risk Assessment → Risk Treatment → Select Annex A Controls → Statement of Applicability → Implement and Monitor Controls

Each control included within the SoA should have a clear business justification that can be traced back to identified information security risks, legal obligations or contractual requirements.

What Must the Statement of Applicability Include?

Every Statement of Applicability should identify:

  • Which Annex A controls have been selected
  • Which Annex A controls have been excluded
  • The justification for including or excluding each control
  • Whether each applicable control has been implemented

Many organisations also include:

  • Control owners
  • Implementation status
  • Supporting policies
  • Review dates

These additions can make the document more useful as an operational management tool.

Every Annex A Control Must Be Considered

For each control, the organisation should determine whether it is:

  • Applicable
  • Not applicable
  • Already implemented
  • Planned for implementation

Where a control is excluded, the organisation should provide a clear justification explaining why it is not relevant within the scope of the Information Security Management System.

The SoA Should Reflect the Current ISMS

Updates may be required following:

  • Changes to the Information Security Risk Assessment
  • New or emerging information security risks
  • Implementation of new technologies
  • Organisational restructuring
  • Changes to legal or contractual obligations
  • Internal Audit findings
  • Management Review decisions
  • Corrective Actions

The SoA Supports Multiple ISO 27001 Requirements

ISO 27001 Activity
How the SoA Supports It
Information Security Risk Assessment
Demonstrates that controls are selected to address identified risks
Risk Treatment
Records the controls chosen to reduce or manage identified risks
Annex A Controls
Documents which controls apply and why
Internal Audits
Enables auditors to verify that selected controls have been implemented
Management Reviews
Supports leadership in reviewing the effectiveness of the ISMS
Certification Audits
Provides documented evidence that control selection follows a structured, risk-based process

What Should a Statement of Applicability Include?

At a minimum, the Statement of Applicability should identify:

  • Which Annex A controls have been selected
  • Which Annex A controls have been excluded
  • The justification for including each applicable control
  • The justification for excluding any controls
  • Whether each applicable control has been implemented

Typical Statement of Applicability Structure

Column
Purpose
Annex A Control Number
Identifies the specific control
Control Name
Describes the control being assessed
Applicable?
Indicates whether the control applies
Justification
Explains why the control has been included or excluded
Implementation Status
Shows whether the control has been implemented, is planned or is not applicable
Supporting Documentation
References relevant policies, procedures, standards or records
Control Owner
Identifies the person or function responsible for maintaining the control

Many organisations also include:

  • Review dates
  • Implementation comments
  • Links to supporting evidence

Justifying Included Controls

Every control included within the Statement of Applicability should have a clear justification.

Typical reasons include:

  • It addresses an identified information security risk
  • It supports legal or regulatory requirements
  • It satisfies customer or contractual obligations
  • It protects critical business information
  • It supports business continuity or operational resilience

A weak justification might be:

"Required by ISO."

A stronger justification would explain the business reason, for example:

"Implemented to reduce the risk of unauthorised access to customer information identified during the Information Security Risk Assessment."

Justifying Excluded Controls

A control should only be excluded where there is a valid business reason.

Examples may include:

  • The control is outside the scope of the ISMS
  • The organisation does not perform the activity addressed by the control
  • The identified risk does not exist within the organisation
  • Alternative controls adequately address the risk

Every exclusion should be documented with sufficient justification to demonstrate that the decision resulted from the Risk Assessment and Risk Treatment process.

Link the SoA to Supporting Documentation

Depending on the control, supporting documentation may include:

  • Information Security Policy
  • Access Control Policy
  • Risk Assessment records
  • Risk Treatment Plan
  • Incident Management Procedure
  • Asset Register
  • Backup procedures
  • Supplier management procedures
  • Internal Audit records
  • Training records

Referencing these documents makes it easier for Internal Auditors and certification auditors to verify implementation.

Keep the Statement of Applicability Practical

An effective SoA should be:

  • Easy to understand
  • Simple to maintain
  • Clearly linked to identified risks
  • Consistent with the Risk Treatment Plan
  • Updated whenever significant changes occur

How to Develop an ISO 27001 Statement of Applicability

Developing an effective Statement of Applicability is the culmination of several key activities within an Information Security Management System.

Step 1: Complete the Information Security Risk Assessment

The Risk Assessment identifies:

  • Information assets
  • Threats
  • Vulnerabilities
  • Existing controls
  • Risk likelihood
  • Business impact
  • Overall risk levels

Without a completed Risk Assessment, there is no objective basis for developing a Statement of Applicability.

Step 2: Develop the Risk Treatment Plan

Typical Risk Treatment options include:

  • Reducing the risk through additional controls
  • Avoiding the risk
  • Transferring the risk
  • Accepting the risk where it falls within defined Risk Acceptance Criteria

The Risk Treatment Plan documents these decisions and identifies the controls required to reduce identified risks to an acceptable level.

Step 3: Review the Annex A Controls

ISO/IEC 27001:2022 includes 93 Annex A controls grouped into four themes:

  • Organisational Controls
  • People Controls
  • Physical Controls
  • Technological Controls

Each control should be reviewed individually to determine whether it is applicable.

Step 4: Determine Which Controls Apply

For every applicable control, the organisation should understand:

  • Which identified risk the control addresses
  • How the control reduces risk
  • Whether the control has already been implemented
  • What additional work, if any, is required
Step 5: Document the Justification

Good justifications should be:

  • Specific
  • Risk-based
  • Relevant to the organisation
  • Easy for auditors and management to understand
Step 6: Record the Implementation Status

Many organisations use simple status indicators such as:

  • Implemented
  • Partially Implemented
  • Planned
  • Not Applicable
Step 7: Review and Approve the Statement of Applicability

Before approval, confirm that:

  • Every Annex A control has been considered
  • Justifications are complete and accurate
  • The document aligns with the Risk Assessment
  • The Risk Treatment Plan supports the selected controls
  • Supporting documentation exists where required

The completed SoA should then be reviewed and approved in accordance with the organisation's document control process.

Step 8: Maintain the Statement of Applicability

The Statement of Applicability should remain a living document throughout the lifecycle of the Information Security Management System.

It should be reviewed whenever significant changes occur.

Developing a Statement of Applicability at a Glance
Step
Purpose
1. Complete the Risk Assessment
Identify and evaluate information security risks
2. Develop the Risk Treatment Plan
Decide how identified risks will be managed
3. Review Annex A Controls
Assess every control for applicability
4. Select Applicable Controls
Choose controls that address identified risks
5. Document Justifications
Explain why each control is included or excluded
6. Record Implementation Status
Show whether applicable controls have been implemented
7. Review and Approve
Verify the SoA is accurate, complete and aligned with the ISMS
8. Maintain the SoA
Update the document as risks, controls and business needs change

Common Statement of Applicability Mistakes

Treating the SoA as a Checklist

Simply marking controls as "Yes" or "No" does not demonstrate why those decisions have been made.

The purpose of the SoA is to explain why each control has or has not been selected based on the organisation's Information Security Risk Assessment and Risk Treatment process.

Copying a Generic Template

Templates can provide a useful starting point, but they should never replace the organisation's own Risk Assessment and decision-making process.

Every organisation has different:

  • Business objectives
  • Information assets
  • Technologies
  • Regulatory obligations
  • Customers
  • Risk appetite
  • Threat landscape
Weak or Generic Justifications

Generic statements such as:

  • "Required by ISO"
  • "Best practice"
  • "Company policy"

provide little evidence that the control selection process was based on identified risks.

Each justification should explain the business reason behind the decision.

Excluding Controls Without Justification

Simply stating "Not applicable" is rarely sufficient.

The organisation should explain why the control does not apply within the defined scope of the Information Security Management System.

Failing to Keep the SoA Up to Date

Changes that may require updates include:

  • New technologies
  • New business processes
  • New suppliers
  • Organisational restructuring
  • Changes to legislation
  • New contractual obligations
  • Emerging cyber threats
  • Internal Audit findings
  • Corrective Actions
Poor Alignment With the Risk Assessment

Problems arise when:

  • Significant risks have no corresponding controls
  • Controls appear in the SoA without any identified risk
  • Risk Treatment decisions do not align with selected controls
  • Supporting documentation contradicts the SoA

A well-developed SoA should create a clear and logical line of sight from identified risks through to implemented controls.

Not Linking to Supporting Evidence

Each applicable control should be supported by documented information such as:

  • Policies
  • Procedures
  • Standards
  • Risk Assessment records
  • Risk Treatment Plans
  • Training records
  • Internal Audit reports
  • Technical configurations
Focusing Only on Certification

When used effectively, the SoA supports:

  • Information security governance
  • Management Reviews
  • Internal Audits
  • Risk Management
  • Continual improvement
  • Decision-making
  • Customer assurance
How to Avoid These Mistakes

Organisations should focus on creating a document that is:

  • Based on a thorough Information Security Risk Assessment
  • Clearly aligned with the Risk Treatment Plan
  • Supported by evidence
  • Updated regularly
  • Easy to understand
  • Practical for day-to-day management
  • Relevant to the organisation's business environment

Benefits of a Well-Developed Statement of Applicability

Demonstrates a Risk-Based Information Security Strategy

The SoA shows that each control has been selected to address identified information security risks, legal obligations or business requirements.

Supports ISO 27001 Certification

A clear, accurate and well-maintained SoA helps certification auditors understand:

  • Which Annex A controls have been selected
  • Why those controls have been implemented
  • Which controls have been excluded
  • How control selection aligns with the organisation's Risk Assessment and Risk Treatment process
Strengthens Governance and Management Oversight

The Statement of Applicability provides senior management with a consolidated view of the organisation's information security controls and the reasoning behind key security decisions.

Improves Consistency Across the ISMS

The Statement of Applicability provides a single reference point that records:

  • Applicable controls
  • Implementation status
  • Business justification
  • Supporting documentation
  • Control ownership
Simplifies Internal and External Audits

Internal Auditors and certification auditors can use the SoA as a roadmap to understand:

  • Which controls should exist
  • Where supporting evidence can be found
  • Which controls are outside the scope of the ISMS
  • How identified risks are being treated
Supports Continual Improvement

Regularly updating the SoA helps organisations:

  • Respond to emerging cyber threats
  • Address changes in legislation and regulations
  • Incorporate lessons learned from incidents
  • Reflect organisational growth and restructuring
  • Track improvements resulting from Internal Audits and Management Reviews
Builds Customer and Stakeholder Confidence

The SoA provides evidence that:

  • Security controls have been selected systematically
  • Risks have been assessed and treated
  • Information security decisions are documented
  • Governance processes are in place
  • The organisation is committed to continual improvement
Delivers Long-Term Business Value

A well-maintained SoA supports:

  • Better Risk Management
  • Improved operational resilience
  • More effective governance
  • Increased management visibility
  • Greater audit readiness
  • Stronger customer confidence
  • More informed business decisions
Summary of Benefits
Benefit
Business Value
Risk-based control selection
Ensures security controls address genuine business risks
Certification support
Demonstrates conformity and simplifies audits
Improved governance
Provides leadership with visibility over information security decisions
Better control management
Creates a central record of applicable controls and implementation status
Audit readiness
Makes Internal and certification audits more efficient
Continual improvement
Supports regular review and updating of controls as risks evolve
Increased stakeholder confidence
Demonstrates a structured and accountable approach to information security
Long-term business resilience
Aligns information security with organisational strategy and operational objectives

How ISO Specialist South Africa Can Help

Implementing ISO/IEC 27001 is about much more than completing documentation or passing a certification audit.

A successful Information Security Management System requires a structured approach that aligns information security with your organisation's risks, business objectives and day-to-day operations.

Practical Support Throughout Your ISO 27001 Journey

Our ISO 27001 consultancy services include:

  • ISO 27001 Gap Analysis
  • ISMS implementation and project guidance
  • Information Security Risk Assessments
  • Risk Treatment planning
  • Statement of Applicability development
  • Documentation development and review
  • Internal Audit support
  • Certification readiness assessments
  • Ongoing ISMS maintenance and continual improvement support

Developing an Audit-Ready Statement of Applicability

We help organisations develop SoAs that:

  • Align with the Information Security Risk Assessment
  • Reflect the Risk Treatment Plan
  • Consider all 93 Annex A controls
  • Include clear, risk-based justifications
  • Identify implementation status
  • Reference supporting policies, procedures and records
  • Remain easy to maintain as the organisation evolves

Tailored to Your Organisation

Whether you operate in:

  • Information technology
  • Financial services
  • Professional services
  • Manufacturing
  • Healthcare
  • Logistics
  • Government supply chains
  • Another sector where information security is critical

the Information Security Management System and Statement of Applicability should reflect your specific risks, operational environment and certification objectives.

More Than Certification

An effective Information Security Management System should help your organisation:

  • Protect valuable information assets
  • Improve governance and accountability
  • Reduce information security risks
  • Support customer and contractual requirements
  • Strengthen operational resilience
  • Establish a culture of continual improvement

End-to-End Support

Depending on your requirements, ISO Specialist South Africa can support:

  • Initial Gap Assessments
  • Project planning
  • ISMS implementation
  • Documentation development
  • Staff awareness and ISO 27001 training
  • Internal Audits
  • Certification readiness
  • Ongoing management system maintenance

Training offerings should be confirmed against ISO Specialist South Africa's current service catalogue before publication.

A Practical Partner Throughout the Certification Journey

Certification bodies are responsible for independently auditing and certifying your Information Security Management System.

ISO Specialist South Africa's role is different.

We help you design, implement and prepare your ISMS for certification so that you are ready for an independent audit by the certification body of your choice.

Frequently Asked Questions About the ISO 27001 Statement of Applicability

What is an ISO 27001 Statement of Applicability?

A Statement of Applicability is a mandatory document within an ISO/IEC 27001 Information Security Management System.

It records:

  • Which Annex A controls apply
  • Which controls have been excluded
  • The justification for each decision
  • Whether applicable controls have been implemented
Is the Statement of Applicability mandatory?
Yes.

The Statement of Applicability is required by ISO/IEC 27001:2022 and is one of the key documents reviewed during certification audits.

Do we have to implement all 93 Annex A controls?
No.

Every Annex A control should be considered, but not every control will necessarily apply to every organisation.

Controls that are not applicable may be excluded, provided there is a clear and documented business justification.

What is the difference between the Statement of Applicability and the Risk Treatment Plan?

The Risk Treatment Plan explains how identified information security risks will be managed.

The Statement of Applicability records which Annex A controls have been selected to support those treatment decisions and why they were chosen.

When should the Statement of Applicability be created?

The Statement of Applicability should be developed after the organisation has:

  • Completed its Information Security Risk Assessment
  • Evaluated identified risks
  • Determined its Risk Treatment Plan
  • Reviewed the Annex A controls
Who is responsible for maintaining the Statement of Applicability?

Responsibility varies between organisations.

It may be maintained by:

  • The Information Security Manager
  • The ISMS Manager
  • The Compliance Manager
  • The Risk Manager
  • An appointed ISO 27001 implementation team

Regardless of who maintains it, senior management should ensure that it remains accurate, current and aligned with the Information Security Management System.

How often should the Statement of Applicability be reviewed?

There is no fixed review period specified by ISO 27001.

It should be reviewed whenever significant changes occur, including:

  • Updates to the Information Security Risk Assessment
  • New or emerging cyber threats
  • Organisational restructuring
  • New technologies
  • Changes to legal or contractual requirements
  • Internal Audit findings
  • Management Review outcomes
  • Corrective Actions

Many organisations also review the SoA as part of their annual ISMS review cycle.

Can the Statement of Applicability be maintained in a spreadsheet?
Yes.

Many organisations maintain their SoA in a spreadsheet because it is simple to update and easy to present during audits.

Others use Governance, Risk and Compliance platforms or dedicated ISMS software.

Regardless of the format, the document should remain controlled, version managed and aligned with the organisation's document control process.

What happens if our Statement of Applicability is inaccurate or outdated?

It may:

  • Reference controls that are no longer implemented
  • Omit recently introduced controls
  • Conflict with the Risk Assessment or Risk Treatment Plan
  • Delay certification audits while discrepancies are investigated
Is the Statement of Applicability reviewed during certification audits?
Yes.

Certification auditors typically review the Statement of Applicability early in the audit process because it provides an overview of the organisation's control environment.

Does the Statement of Applicability need to reference supporting documents?

ISO 27001 does not prescribe a specific format, but many organisations reference supporting documentation within the Statement of Applicability.

Examples include:

  • Information Security Policies
  • Procedures
  • Standards
  • Risk Assessment records
  • Risk Treatment Plans
  • Technical standards
  • Training records
  • Internal Audit reports
How does the Statement of Applicability support POPIA compliance in South Africa?

ISO 27001 certification does not automatically demonstrate compliance with POPIA.

However, where POPIA requirements influence the organisation's Information Security Risk Assessment, the SoA can demonstrate how appropriate Annex A controls have been implemented to support the protection of personal information, strengthen governance and meet contractual or regulatory expectations.

ISO 27001 Knowledge Centre

Core ISO 27001 Guides
  • What Is ISO 27001?
  • ISO 27001 Requirements
  • ISO 27001 Implementation Process
Risk Management Resources
  • ISO 27001 Risk Assessment
  • ISO 27001 Gap Analysis
  • ISO 27001 Statement of Applicability
Annex A and Security Controls
  • ISO 27001 Annex A Controls
Documentation and Compliance
  • ISO 27001 Documentation Requirements
Audit and Certification
  • ISO 27001 Internal Audit
  • ISO 27001 Certification Process
  • ISO 27001 Certification Cost
Training and Awareness
  • ISO 27001 Training
How the ISO 27001 Journey Fits Together

Understand ISO 27001 → Define the ISMS Scope → Conduct a Gap Analysis → Perform a Risk Assessment → Develop the Risk Treatment Plan → Select Annex A Controls → Create the Statement of Applicability → Implement Controls → Conduct Internal Audits → Management Review → Certification Audit → Continual Improvement

Conclusion

The Statement of Applicability is far more than a mandatory ISO/IEC 27001 document.

It is one of the cornerstones of an effective Information Security Management System, providing a clear and documented link between your organisation's Information Security Risk Assessment, Risk Treatment decisions and the Annex A controls implemented to protect your information assets.

A well-developed Statement of Applicability delivers value far beyond certification.

It supports stronger governance, simplifies Internal and certification audits, improves accountability, facilitates continual improvement and helps organisations maintain an Information Security Management System that evolves alongside changing business needs, technologies and cyber threats.

The Statement of Applicability Is a Living Document

The Statement of Applicability should never be viewed as a document that is completed once and then forgotten.

Regularly reviewing and updating it helps ensure that it continues to reflect:

  • Current information security risks
  • Changes to business processes
  • New technologies and systems
  • Legal and regulatory requirements
  • Customer and contractual obligations
  • The implementation status of security controls

A Strong Foundation for Certification and Beyond

A practical, well-maintained SoA helps organisations:

  • Make informed risk-based security decisions
  • Improve information security governance
  • Demonstrate accountability to customers and stakeholders
  • Support compliance with contractual and regulatory requirements
  • Strengthen organisational resilience
  • Build a culture of continual improvement

Ready to Strengthen Your Information Security Management System?

ISO Specialist South Africa can assist with:

  • ISO 27001 Gap Analysis
  • Information Security Risk Assessments
  • Risk Treatment planning
  • Statement of Applicability development
  • ISMS implementation
  • Documentation development
  • Internal Audits
  • Certification readiness assessments
  • Ongoing ISMS support and continual improvement

Whether you are implementing ISO 27001 for the first time, preparing for certification or improving an existing Information Security Management System, we can help you develop a practical, risk-based and audit-ready Statement of Applicability aligned with your organisation's business objectives.

:::

Search

Powered by Joinchat