Start hereDefine the ISMS boundary
~161 days leftOpen step
Guide library
Certification Global

ISO 27001

ISO/IEC 27001:2022 · Information security management systems

Build an information security management system and prepare for a third-party certification audit.

Who it applies to

Organizations of any size seeking a certifiable information security management system (ISMS) within a defined boundary.

What you’ll produce

ISMS certificate for the audited scope if the external certification body approves.

Confirm the applicable edition, amendments and surveillance cycle with an accredited certification body. Use the licensed standard for normative requirements.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What should the certificate cover?
Define the product, legal entities, teams, sites and cloud operations that need the information security management system (ISMS). Ask commercial teams what wording their customers need and check that the proposed scope matches the work they buy.
Which risks can the business accept?
Name people with authority to accept remaining risk and define what they may approve. Reserve budget for risk treatment, independent internal audit, certification Stage 1 and Stage 2, and surveillance. Compare quotes on sites and scope.
Who will run the ISMS after certification?
Name an ISMS lead, executive sponsor, risk owners and an independent internal auditor. Give the lead permission to schedule management reviews and require evidence from operating teams.

How to spend the first week

  1. Request the licensed standard, product and site inventory, customer commitments, regulatory obligations and system architecture.
  2. Walk through one service with Operations and Engineering. Draw the scope and the interfaces with outsourced or excluded services. Bring disputed boundaries to management.
  3. Book a working session with risk owners. Agree how risks will be rated, who can accept them and where approvals and evidence will live.

What to review each week

Use the register to report overdue high-risk treatments, audit findings past due, and objectives with deteriorating results. Include the next management or certification review date.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

ISO 27001 kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Define the ISMS boundary · ISMS lead + leadership [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Request the licensed standard, product and site inventory, customer commitments, regulatory obligations and system architecture.
2. Walk through one service with Operations and Engineering. Draw the scope and the interfaces with outsourced or excluded services. Bring disputed boundaries to management.
3. Book a working session with risk owners. Agree how risks will be rated, who can accept them and where approvals and evidence will live.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which business units and interfaces are inside the proposed ISMS?
  • Can you point from each treated risk to an owner, selected control and evidence of operation?

Worked scenario

A software company scopes its hosted application and keeps its head office outside the proposed certification boundary. It still documents corporate identity as a dependency because a head-office identity change can affect production access.

What to read next

  • ISO 27017 cloud controls

    Assign shared controls for cloud services inside the scope.

  • ISO 22301

    Structure the business continuity work if service disruption is a significant risk.

Plan evidence for ISO 27001 and other programs Test this project’s launch date
The whole journeyabout 161 days across 5 steps
  1. 01Define the ISMS boundaryISMS lead + leadership · ~14 days
  2. 02Assess risks and select controlsRisk owners · ~35 days
  3. 03Operate, audit and review the ISMSInternal auditor + leadership · ~56 days
  4. 04Complete Stage 1 and Stage 2Certification body + ISMS lead · ~35 days
  5. 05Maintain certificationISMS lead · ~21 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 15 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Define the ISMS boundaryISMS lead + leadershipBefore risk assessmentSet a start dateScope statement; Security policy; Obligations registerOpen
Assess risks and select controlsRisk ownersBefore implementationSet a start dateRisk register; Treatment plan; Statement of ApplicabilityOpen
Operate, audit and review the ISMSInternal auditor + leadershipBefore external assessmentSet a start dateInternal audit report; Management review minutes; CAPA logOpen
Complete Stage 1 and Stage 2Certification body + ISMS leadDates agreed with the certification bodySet a start dateReadiness findings; Stage 2 report; Certification decisionOpen
Maintain certificationISMS leadSurveillance and recertification cycleSet a start dateAudit calendar; Updated SoA; Performance measuresOpen
0 of 5 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Define the ISMS boundary

    Who ISMS lead + leadership When Before risk assessment

    Identify interested parties, legal and contractual obligations, interfaces, suppliers and activities covered by the ISMS. Approve scope and policy.

    How to do this step

    Before you start

    Entities, facilities, service flows, relevant interested parties, customer contracts and security obligations.

    1. Draw the information flow from customer intake to deletion. Mark teams, cloud accounts, physical locations and outsourced owners that touch covered information.
    2. Describe which services, sites and dependencies sit within the ISMS. Record how you control interfaces and dependencies outside the boundary.
    3. Assign management and operating responsibilities. Have management approve scope and policy, then communicate the policy to people performing the work.

    What a reviewer should see

    A versioned scope statement matches the service map and says who owns outsourced interfaces. The obligations register names an owner and pointer to each obligation.

    When to escalate

    Reopen scope review if Sales requires a service on the certificate that the draft excludes, or if a critical location or outsourced dependency has no owner.

    What to produce

    Scope statementMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Security policyMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

    Obligations registerSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

  2. 02

    Assess risks and select controls

    Who Risk owners When Before implementation

    Apply approved risk criteria, select treatments and compare selected controls against Annex A. Document applicability, exclusions and implementation status.

    How to do this step

    Before you start

    Approved scope, risk methodology, obligations register, service architecture and incident history.

    1. Write risks as scenarios. For a cloud administrator account takeover, identify the assets, event, business impact, existing safeguards, current rating and owner.
    2. Choose the controls needed to treat the risk. Compare them with Annex A to check for omissions. In the Statement of Applicability record necessary controls, inclusion rationale, implementation status and reasons for excluded Annex A controls.
    3. Set deadlines, evidence and owners in the treatment plan. Get each risk owner’s approval of the plan and acceptance of the remaining risk through the agreed approval route.

    What a reviewer should see

    The account takeover risk links to its treatment, the SoA entry, the identity configuration and the evidence that privileged access works as designed. Remaining risk has named approval.

    When to escalate

    Bring unfunded treatments, unresolved exclusions and residual risks outside authorized thresholds to management before assessment.

    What to produce

    Risk registerSpreadsheet

    Gather first

    • Processing or service design and affected people
    • Threats, consequences and assessment triggers
    • Risk methodology and current safeguards

    How to prepare it

    1. Screen the activity against the applicable assessment trigger. Describe the real scenario and who or what could be harmed. Record likelihood and consequence using your criteria.
    2. Describe existing safeguards. Decide what reduces the risk and what risk remains after those measures. For a required impact assessment, document necessity, alternatives and consultation where applicable.
    3. Send the result to the person who can approve, change or stop the activity. Set a review trigger and keep evidence of the decision.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and risk
    Account recovery could expose invoices to an impersonator.
    Affected people or assets
    Customer account contacts and invoices
    Current controls
    Recovery uses verified channel. Sampled evidence linked.
    Proposed treatment
    Require a second check for requests to change the billing address.
    Remaining risk and decision
    Moderate under company method. Approval required before launch.
    Owner and review trigger
    Product risk owner, repeat when recovery flow changes

    Check before handing it over

    The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.

    Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.

    Treatment planSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

    Statement of ApplicabilitySpreadsheet

    Gather first

    • Licensed standard and applicable amendments
    • Approved ISMS scope, risk assessment and treatment plan
    • Control implementation records
    • Relevant obligations and risk-owner approvals

    How to prepare it

    1. List every control necessary for the selected risk treatments, including controls from outside Annex A. Compare the list with Annex A to identify omissions. Capture each required inclusion and justify each Annex A exclusion using a concrete fact about risk, scope or obligations.
    2. Create one row per control reference. Record the reason it is needed, implementation status and proof. Link the risk and treatment decision where applicable. For a planned control, name its owner, date and interim treatment.
    3. Have the ISMS lead reconcile the rows with the treatment plan, actual controls and obligations. Obtain risk owners’ approval of treatment and acceptance of remaining risks, and preserve version history and review triggers.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Reference and control
    Annex A 8.2, Privileged access rights. Internal control IAM-03.
    Included and why
    Included. Seven named administrators and two automation identities can change production systems supporting hosted invoicing.
    Risk and treatment
    R-014. Misuse or theft of an administrator identity could expose customer invoices. Restrict privileges by role, require approval for elevation and review access quarterly.
    Implementation and evidence
    Implemented in the production billing accounts. Role policy POL-19, quarterly review EV-021 and deployment access test EV-022 show operation.
    Exclusion rationale
    Not applicable to this row. Every excluded Annex A control has its own documented rationale.
    Owner, approval and review
    A. Singh owns IAM-03. Operations Director approved treatment and accepted remaining risk in R-014 on 2026-10-09. Reassess if identity or cloud scope changes.

    Check before handing it over

    A reviewer can trace selected controls to the reasons they are needed and supporting evidence, and can locate a justified decision for every excluded Annex A control.

    The ISMS lead holds the controlled SoA and makes the current version available for audit. Control owners update implementation evidence and notify the lead when treatment or scope changes.

  3. 03

    Operate, audit and review the ISMS

    Who Internal auditor + leadership When Before external assessment

    Collect operating records, audit the ISMS objectively, review results with leadership and close significant corrective actions.

    How to do this step

    Before you start

    Operational records, performance objectives, SoA, previous issues and the scope and criteria for internal audit.

    1. Collect recent examples of the ISMS operating. For each objective record how it is measured, data source, owner and review date.
    2. Assign an auditor who can review the work objectively. Trace a risk to treatment, control operation and follow-up. Record each finding with the relevant requirement and observable evidence.
    3. Use management review to decide resources, changes and improvement actions. Give each decision an accountable owner and a date.

    What a reviewer should see

    The audit file ties a finding to evidence, root cause and corrective action. Management review minutes show a resource decision, owner and checkpoint.

    When to escalate

    Escalate if the internal auditor is reviewing their own work or if management review minutes record discussion without decisions required to resolve the issues.

    What to produce

    Internal audit reportMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    Management review minutesMemo

    Gather first

    • Agenda or decision request
    • Current performance measures and findings
    • Proposed actions and participants

    How to prepare it

    1. Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
    2. Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
    3. Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Item
    Approve a fix for the missing access-removal retry.
    Inputs reviewed
    September test results and IAM incident root-cause notes.
    Decision
    Approve automatic retry plus daily reconciliation.
    Action and due date
    Platform lead to ship and test by 2026-11-28.
    Residual risk and follow-up
    Manual review remains until rollout. Check at December meeting.

    Check before handing it over

    The minutes identify the person who approved each action and the date the decision will be revisited.

    Give owners the actions and add the approved record to the relevant audit or governance file.

    CAPA logSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

  4. 04

    Complete Stage 1 and Stage 2

    Who Certification body + ISMS lead When Dates agreed with the certification body

    Use Stage 1 to address readiness findings and Stage 2 to demonstrate implementation and effectiveness. Resolve nonconformities within the body’s deadlines.

    How to do this step

    Before you start

    Current ISMS documents, internal audit and management review records, operating evidence and the certification body’s assessment plan.

    1. Confirm certificate scope wording and audit schedule with the certification body. Identify who will explain the ISMS and demonstrate controls during interviews.
    2. Use Stage 1 findings to fix readiness gaps before Stage 2. Reconcile the SoA, risk register and actual configurations so evidence is consistent across reviewers.
    3. For each nonconformity, record immediate correction, root cause, corrective action and evidence of effectiveness. Submit responses on the agreed timetable.

    What a reviewer should see

    The assessment file includes the scope and final SoA version, accepted finding responses and the certification body’s decision when issued.

    When to escalate

    Escalate any finding that puts Stage 2 or the decision at risk and any mismatch between requested and proposed certificate scope.

    What to produce

    Readiness findingsSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

    Stage 2 reportIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Certification decisionIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

  5. 05

    Maintain certification

    Who ISMS lead When Surveillance and recertification cycle

    Monitor objectives and risks, update the SoA for changes, repeat internal audits and management review, and schedule surveillance visits.

    How to do this step

    Before you start

    Certificate, surveillance schedule, current SoA, incident history and new processes or locations.

    1. Maintain the internal audit and management review calendar and preserve objective results over time.
    2. Trigger a risk and scope review on major changes. Confirm with the certification body when relevant changes need to be reported or affect scope.
    3. Verify corrective actions stayed effective using new evidence. Track surveillance and recertification dates assigned by the certification body.

    What a reviewer should see

    A new production region has a change decision, updated artifacts and any required communication to the certification body.

    When to escalate

    Raise missed surveillance windows, recurring nonconformities and marketing claims that exceed certificate scope.

    What to produce

    Audit calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

    Updated SoASpreadsheet

    Gather first

    • ISMS risk assessment and risk treatment plan
    • ISO/IEC 27001 Annex A and applicable amendments
    • Implemented controls and management decisions

    How to prepare it

    1. Identify controls necessary for your risk treatment. Cross-check the selection against Annex A and retain any additional controls that address your risks.
    2. For each relevant control document why it is included and whether it is implemented. Record and justify any excluded Annex A controls. Use the licensed text for official references.
    3. Reconcile the worksheet with the risk treatment plan and evidence. Obtain management approval and refresh when risks, scope or controls materially change.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Control reference
    Use the licensed Annex A reference or internal control ID.
    Applicable and why
    Yes. The service uses privileged production roles.
    Risk and treatment
    Risk R-014, review and revoke elevated privileges.
    Implementation status
    Implemented. September review linked in EV-021.
    Exclusion rationale
    Record a specific business or scope reason when excluded.
    Approval and review
    ISMS lead and risk owner, next review at scope change.

    Check before handing it over

    Every Annex A control has an explicit decision, with supporting justification and implementation status where selected.

    Give the approved SoA to the certification body and use it as the baseline for controls and change review.

    Performance measuresSpreadsheet

    Gather first

    • Baseline evidence
    • Approved target or success definition
    • Dates, denominator and responsible service

    How to prepare it

    1. Pick a measure or outcome with a clear definition. Record the population, reporting period and evidence source so others can calculate it.
    2. Record the current state, target and gap. Add the change needed, accountable owner and next date to collect evidence.
    3. Check the numbers against source data and explain material exceptions or changes in scope before sharing.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Outcome
    Administrators receive quarterly access review.
    Current and evidence
    11 of 12 eligible roles reviewed, IAM export as of 30 Sep 2026.
    Target
    All eligible roles reviewed
    Gap and action
    One role missed. Reconcile new roles before next review.
    Owner and review
    IAM lead, next quarter

    Check before handing it over

    The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.

    Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.

Common questions

What goes into an ISO 27001 Statement of Applicability?

Record the controls needed to treat risks, explain why they are included, state whether they are implemented and justify exclusions of Annex A controls. Link these decisions to the risk treatment plan and keep them current as the scope or risks change.

ISO · ISO/IEC 27001:2022 (opens in a new tab)

What happens during the two stages of certification?

Use Stage 1 to check scope, documented information and readiness. Stage 2 looks at how the management system is implemented and operates. Confirm the assessor’s evidence requests and deadlines before the visits.

ISO · Certification and conformity assessment (opens in a new tab)
PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes