Skip to main content
The Annex A module displays all 93 ISO 27002:2022 controls organised by domain. For each control you can record its implementation status, responsible party, and last review date. When your evaluation is complete, you can export a PDF Statement of Applicability (SoA).

Control domains

ISO 27002:2022 organises controls into four thematic domains:

Organisational

Policies, roles, responsibilities, and governance controls. Covers information security policies, asset management rules, and supplier relationships.

People

Human resource controls covering screening, terms of employment, awareness, training, and disciplinary processes.

Physical

Physical and environmental security controls including secure areas, equipment protection, and clear desk policies.

Technological

Technical controls covering access management, cryptography, vulnerability management, logging, and network security.

Evaluating a control

1

Open the Annex A page

Navigate to Annex A in the sidebar. The table shows all 93 controls with their current status.
2

Filter by domain (optional)

Use the domain tabs or filter at the top of the table to narrow the view to a single theme such as Technological or People.
3

Set the implementation status

Click the status cell for the control you want to evaluate and select one of the four options:
StatusMeaning
Not evaluatedDefault — no assessment has been recorded
In progressControl is partially implemented
ImplementedControl is fully in place
Not applicableControl does not apply to your scope
4

Assign a responsible party

Enter the name or role of the person accountable for this control in the Responsible column.
5

Record the last review date

Set the date when this control was last assessed using the date field in the Last review column.
For controls marked Not applicable, document the justification in your risk treatment documentation. Auditors will ask for the rationale behind any SoA exclusion.

Control data reference

Each control in the table carries the following fields:
FieldDescription
IDISO 27002:2022 control identifier (e.g. A.5.1)
DomainThematic group (Organisational, People, Physical, Technological)
NameOfficial control title
DescriptionSummary of the control objective
StatusCurrent implementation status
ResponsibleAccountable person or role
Last reviewDate of last assessment

Exporting the Statement of Applicability

The Statement of Applicability (SoA) is a mandatory ISO 27001 document that lists every Annex A control and records whether it is applicable and implemented. To export the SoA:
  1. Evaluate all relevant controls (at minimum set every control to a status other than Not evaluated).
  2. Click Export SoA in the page header.
  3. ISOwl generates a PDF containing the full control table with statuses, responsible parties, and review dates.
  4. The file downloads to your browser’s default download folder.
Exporting before all controls have been evaluated will include Not evaluated controls in the PDF. Review the control table completely before generating a formal SoA for an audit.

How the Annex A score is calculated

The Annex A maturity percentage displayed on the Executive Dashboard is:
Annex A score = Implemented controls / (Total controls − Not applicable controls)
Marking a control as Not applicable reduces the denominator, which raises the percentage. Marking a control as In progress or Not evaluated does not contribute to the numerator.

Frequently asked questions

The control library is fixed to the 93 controls defined in ISO 27002:2022. If your organisation uses supplementary controls, document them in the notes field of the closest applicable control.
The exported PDF includes the status of each control. Free-text justifications entered in notes fields are also included if present. Ensure you document exclusion rationale before the export.
ISO 27001 requires periodic review of the ISMS. Most organisations review controls at least annually or after significant changes. The Last review date field helps you track which controls are overdue for reassessment.

Build docs developers (and LLMs) love