Home › Resources › Guides › ISO 27001 implementation

Resources · Implementation guide

ISO 27001 implementation guide: 10 steps from scope to certification

In shortTo implement ISO 27001, define the scope of your information security management system, assess and treat your risks, write a Statement of Applicability against the 93 Annex A controls, put the controls into operation, then run an internal audit and a management review before an accredited body certifies you in two stages.

What are the steps to implement ISO 27001?

The order below follows the standard's own clauses. Each step names the clause an auditor will test.

  1. Get leadership commitment

    Agree why the organisation wants certification, who sponsors it and what resources it has. Top management must approve the security policy and assign roles.

    Clause 5
  2. Define the scope

    Decide which locations, teams, systems and services the management system covers, and write down the interfaces with what is left out.

    Clause 4.3
  3. Set the risk method

    Define how risks are identified, scored and accepted, so that two people assessing the same risk reach a comparable result.

    Clause 6.1.2
  4. Assess the risks

    List the risks to the information in scope, score them with your method and name an owner for each.

    Clauses 6.1.2 and 8.2
  5. Plan the treatment and write the Statement of Applicability

    Choose controls for each risk, compare them with all 93 Annex A controls, and justify every inclusion and exclusion.

    Clause 6.1.3
  6. Implement the controls

    Put the chosen controls into operation and write only the procedures people will actually follow.

    Clause 8.1
  7. Train people and keep records

    Make sure staff know the policy and their part in it, and that records are controlled.

    Clauses 7.2 to 7.5
  8. Measure and run an internal audit

    Decide what to monitor, then audit the whole system with someone independent of the work being audited.

    Clauses 9.1 and 9.2
  9. Hold a management review and fix nonconformities

    Top management reviews results and decides on changes. Every nonconformity gets a corrective action.

    Clauses 9.3 and 10.2
  10. Pass the certification audit

    An accredited certification body audits in two stages: readiness and documentation, then how the system works in practice.

    Stage 1 and Stage 2

Go deeper: risk assessment · Statement of Applicability · internal audit.

Which documents does ISO 27001 require?

The standard asks for "documented information" in these places. Anything beyond this list is your choice.

Documented informationClause
ISMS scope4.3
Information security policy5.2
Risk assessment process6.1.2
Risk treatment process6.1.3
Statement of Applicability6.1.3 d
Information security objectives6.2
Evidence of competence7.2
Operational planning and control records8.1
Risk assessment results8.2
Risk treatment results8.3
Monitoring and measurement results9.1
Internal audit programme and results9.2
Management review results9.3
Nonconformities and corrective actions10.2

The standard does not require a set number of policies or a particular format. Auditors check that these exist, are controlled and are in use.

Are you ready for the certification audit?

Tick what is done. Nothing is saved or sent; the list resets when you leave the page.

How does the ISO 27001 certification audit work?

Stage 1Readiness

The auditor reviews your scope, documented information and readiness, and tells you what to resolve before Stage 2.

Stage 2Effectiveness

The auditor tests whether the system and its controls work in practice, by interview, observation and sampling of records.

After certificationSurveillance

The certificate runs for three years. Surveillance audits check the system in between, followed by recertification.

Use a certification body accredited by a member of the International Accreditation Forum. A consultant who helped build your system cannot also certify it.

What goes wrong most often?

01

Starting with Annex A

Teams implement all 93 controls first and assess risk afterwards, so the controls are not tied to any risk.

Instead: assess risk first; the controls follow from the treatment decisions.

02

A scope that is too wide

Covering the whole company on day one multiplies the evidence needed before the first audit.

Instead: start with the services your customers ask about, and widen later.

03

Documents nobody uses

Bought policy packs describe a company that does not exist. Auditors test what people actually do.

Instead: write short procedures that match how the work is really done.

How does QULDEX support an ISO 27001 project?

Audit Workspace

Plan the internal audit, test controls, record findings and issue the report in eight phases, with ISO 27001 controls already mapped.

See the workspace

ISO 27001 implementation: common questions

What is the first step in implementing ISO 27001?

Get top management commitment and define the scope: which locations, teams, systems and services the management system will cover.

Do we have to implement all 93 Annex A controls?

No. You must consider all 93 and record in the Statement of Applicability which apply and why. Controls that do not address any of your risks can be excluded with a justification.

How long does ISO 27001 implementation take?

It depends on the scope, the size of the organisation and how many controls already operate. A certification body will also expect the system to have run long enough to show an internal audit and a management review.

Can we certify ourselves?

No. Certification is issued by an independent certification body. For the certificate to be widely accepted, that body should be accredited by a member of the International Accreditation Forum.

Run your ISO 27001 internal audit in one workspace

Controls, evidence, findings and corrective actions together, mapped to the standard.

Schedule
Book a Demo