Asurvo
Use case

Build an ISO 27001 program from scratch

Asurvo guides you through scoping, risk assessment, Statement of Applicability, and ongoing operation — with templates that match Annex A one-to-one.

Workflow

How it works in Asurvo.

  1. 1

    Scope your ISMS

    Define boundaries with asset and process registers.

  2. 2

    Run risk assessment

    Use our methodology or bring your own.

  3. 3

    Generate your SoA

    One click, backed by your live control data.

  4. 4

    Operate continuously

    Review cycles, internal audits, and management review in one place.

ISO 27001 playbook

Building an ISMS that passes certification and keeps running

ISO 27001 certification is not awarded for a set of controls. It is awarded for a management system that decides which controls you need, runs them, checks whether they work, and improves. That distinction explains most first-time failures: teams implement Annex A diligently, then arrive at the Stage 2 audit without an internal audit, a management review, or a risk assessment that actually drove their control choices. This playbook is organized around the management system first and the controls second.

What each clause requires you to produce

Clause, Requirement in brief, Artefacts auditors expect comparison
4 ContextUnderstand internal and external issues, interested parties and their requirements, and define the ISMS scopeContext and interested parties analysis, scope statement
5 LeadershipTop management commitment, an information security policy, and assigned roles and responsibilitiesApproved information security policy, roles and responsibilities record
6 PlanningRisk assessment and treatment processes, information security objectives, and planning of changesRisk methodology, risk register, risk treatment plan, Statement of Applicability, objectives
7 SupportResources, competence, awareness, communication, and control of documented informationTraining and competence records, communication plan, document control process
8 OperationRun the planned processes, perform risk assessments at planned intervals, and implement treatmentOperational records and evidence for implemented controls, updated risk assessments
9 Performance evaluationMonitoring and measurement, internal audit, and management reviewMetrics, internal audit program and reports, management review minutes
10 ImprovementContinual improvement, nonconformity handling, and corrective actionNonconformity and corrective action log

Annex A then lists 93 reference controls grouped into four themes: organizational, people, physical, and technological. You do not have to implement all of them, but you must consider every one in your Statement of Applicability, state whether it applies, and justify inclusions and exclusions. For background on the management system concept itself, see what an ISMS is.

A phased path to certification

Indicative sequence; actual duration depends on scope, maturity, and auditor availability

Indicative sequence; actual duration depends on scope, maturity, and auditor availability
1. FoundationAgree scope, context, and interested parties; secure leadership sponsorship; write the top-level policyScope statement, information security policy, rolesManagement has approved scope and policy
2. RiskAdopt a methodology, identify assets and risks, score them, choose treatmentsRisk register, treatment plan, draft SoAEvery in-scope risk has an owner and treatment decision
3. ImplementClose control gaps, write supporting policies and procedures, start collecting evidenceImplemented controls, topic policies, evidence recordsControls in the SoA are operating
4. CheckRun a full internal audit and hold a management reviewInternal audit report, management review minutes, corrective actionsFindings are logged and being addressed
5. Stage 1 auditThe certification body reviews documentation and readinessStage 1 report with areas of concernConcerns resolved before Stage 2
6. Stage 2 auditThe certification body evaluates implementation and effectivenessStage 2 report, nonconformities if anyMajor nonconformities closed; certificate issued
7. OperateSurveillance audits in the following years and recertification before the three-year certificate expiresUpdated risk assessments, recurring internal audits and reviewsThe cycle repeats

Getting the risk assessment right

The risk assessment is where the standard expects your ISMS to become specific to you. Clause 6.1.2 requires defined risk acceptance criteria and a process that produces consistent, valid, and comparable results. In practice that means a written methodology with a scoring scale everyone applies the same way, owners who accept residual risk, and a clear line from each risk to the controls that treat it. Our risk assessment methodology template is a starting point you can adapt.

A common mistake is building the Statement of Applicability first, by walking down Annex A and ticking controls, then writing risks to justify the ticks. Auditors can see this because the risks read like control names. Start from the business: the information you hold, the processes that depend on it, and what could realistically go wrong. The SoA should be an output of that thinking.

Roles the ISMS needs

  • Top management approves the policy, sets objectives, provides resources, and chairs or attends management review. Auditors will want to speak with them.
  • ISMS manager owns the program day to day: risk process, SoA, document control, and audit coordination.
  • Risk and control owners across IT, engineering, HR, facilities, and legal, who operate controls and produce evidence.
  • Internal auditor who is independent of the areas they audit, whether a staff member from another function or an external provider working to an internal audit plan.

Where programs stall

  • Scope drawn so broadly that every office, subsidiary, and legacy system must be covered before the first audit.
  • Leaving internal audit and management review to the final weeks, so there is no time to act on their findings.
  • Policy documents copied from elsewhere that describe processes the organization does not follow.
  • No document control, leaving several versions of the same policy in circulation.
  • Treating certification as the finish line, then scrambling before the first surveillance audit because nothing was maintained.

Signals the ISMS is actually working

  • Risk register updated after a significant change, not only on the annual cycle
  • Objectives with measurable targets and reported results
  • Corrective actions closed with evidence that the root cause was addressed
  • Management review minutes that record decisions, not just attendance
  • Staff can explain the policies relevant to their role
  • Evidence for recurring controls exists for every period, not just the weeks before the audit

How Asurvo supports the program

Asurvo's AI learns your organization's context, then generates controls, drafts policies, and builds a risk assessment specific to you rather than generic boilerplate. The risk register scores inherent, residual, and target risk with treatment plans, owners, and deadlines, and evidence arrives through native integrations with expiry tracking. Internal audit workflows, findings, and corrective actions live in the Audit module. For certification, Asurvo partners with GCAICERT, a certification body for ISO 27001. The ISO 27001 complete guide covers the standard in depth.

FAQ

Frequently asked questions

What is the difference between a Stage 1 and a Stage 2 audit?

Stage 1 reviews your ISMS documentation and readiness: scope, policy, risk assessment, Statement of Applicability, and whether internal audit and management review have been planned or performed. Stage 2 evaluates whether the ISMS is implemented and effective, through interviews, sampling of records, and observation. Issues raised at Stage 1 should be resolved before Stage 2 begins.

Do we have to implement all 93 Annex A controls?

No. You must consider all 93 in your Statement of Applicability and justify each decision, but controls are selected based on your risk assessment and your legal, regulatory, and contractual requirements. A fully remote company may exclude some physical controls, for example. Exclusions need a clear justification an auditor will accept, and they cannot be used to avoid addressing real risks.

How long is an ISO 27001 certificate valid?

Certificates are typically issued for three years. During that cycle the certification body performs surveillance audits, usually annually, to confirm the ISMS is still operating and improving. Before the certificate expires, a recertification audit reviews the whole system again. Nonconformities found at any of these audits must be addressed through corrective action.

Do we need an internal audit before the certification audit?

Yes. Clause 9.2 requires internal audits at planned intervals, and certification bodies generally expect to see at least one completed internal audit covering the ISMS, along with a management review, before they will recommend certification. Plan them early enough that you can act on the findings, since unaddressed internal audit results undermine the Stage 2 audit.

Can we build an ISO 27001 program without a consultant?

Many organizations do, especially with good templates and a platform that structures the work. The standard is readable, and the core effort is internal: understanding your risks, operating controls, and keeping records. Outside help is most valuable for independent internal audit, a readiness review before Stage 1, or specialist areas your team lacks. The certification body cannot also act as your consultant.

Ready to replace the spreadsheet chaos?

See Asurvo in action with a 20-minute walkthrough tailored to your stack and frameworks.