Home / cybersecurity / ISO/IEC 27001 Lead Implementer / Cheat Sheet
ISO/IEC 27001 Lead Implementer

ISO 27001 LI Cheat Sheet

ISO 27001 Lead Implementer Tests Risk-Driven ISMS Design — Not Deploying Every Annex A Control

This PECB exam puts you on the implementing organisation's side: scope, risk assessment, Statement of Applicability, operation, measurement and certification readiness. Every control must trace back to a risk treatment decision.

Check Your Readiness →
Among the harder certs
Avg: Not published by PECB
Pass: 750 / 1000
Most candidates understand ISO/IEC 27001 Lead Implementer concepts — and still fail. This exam tests how you apply knowledge under pressure.

PECB ISO/IEC 27001 Lead Implementer Domain Map

Eighty three-option multiple-choice questions, open book, including scenario sets of five questions. Planning carries the most weight, and the right option usually follows clause logic: context and scope, risk criteria, assessment, treatment, then controls justified in the Statement of Applicability.

  1. 01
    ISMS principles and concepts (18.75%) — CIA, threat vs vulnerability vs risk, control types and categories, harmonized structure
  2. 02
    ISMS requirements and controls (15%) — Annex A's 93 controls in four themes, ISO/IEC 27002 attributes, SABSA and other architecture frameworks
  3. 03
    Planning the implementation (22.5%) — context, scope, gap analysis, risk criteria and assessment, treatment options, SoA, objectives
  4. 04
    Implementing the ISMS (17.5%) — documented information, competence and awareness, cloud responsibility, incident handling, RPO and RTO
  5. 05
    Monitoring and measurement (12.5%) — clause 9.1 determinations, effectiveness metrics, internal audit programme, management review
  6. 06
    Continual improvement (7.5%) — correction vs corrective action, root cause tools, effectiveness review, change triggers
  7. 07
    Preparing for certification (6.25%) — Stage 1 and Stage 2, certification decision, surveillance and recertification

Wrong instinct vs correct approach

To certify faster, the sponsor wants core customer-facing systems left out of the ISMS scope
✕ Wrong instinct

Narrow the scope to the easiest departments first

✓ Correct approach

Clause 4.3 scope must reflect external and internal issues, interested party requirements, interfaces and dependencies. Excluding what customers rely on undermines the certificate's value and is likely to be challenged at Stage 1.

The board proposes buying cyber insurance as the response to ransomware risk
✕ Wrong instinct

Record the risk as fully transferred to the insurer

✓ Correct approach

Insurance is risk sharing: it reduces some financial consequences, but accountability, downtime and reputational impact remain. Combine it with risk modification such as backups and tested recovery, and have the risk owner accept what remains.

Controls went live last week and management wants the Stage 2 audit booked immediately
✕ Wrong instinct

Schedule Stage 2 now that controls are deployed

✓ Correct approach

Stage 2 tests whether the ISMS works, which needs operating records, a completed internal audit and a management review with recorded decisions. Book it once that evidence exists, after a Stage 1 readiness review.

A SaaS rollout team assumes the provider now handles all access management
✕ Wrong instinct

Leave user access reviews to the SaaS provider

✓ Correct approach

Under the shared responsibility model the customer always keeps accountability for its users, permissions and data. IaaS leaves the most to the customer and SaaS the least, but access reviews stay in house.

Know these cold

  • ▸ Plan in clause order — .1 context, 4.2 interested parties, 4.3 scope, then 6.1 risk
  • ▸ SoA elements — ecessary controls, justification, implementation status, and justification for any exclusion
  • ▸ Annex A 2022 — 3 controls; organizational 37, people 8, physical 14, technological 34
  • ▸ Treatment options — odify, retain, avoid, share; sharing never transfers accountability
  • ▸ Gap analysis drives the project plan; risk assessment drives control selection
  • ▸ RPO is acceptable data loss and sets backup frequency; RTO is acceptable downtime
  • ▸ Backups are corrective controls, log reviews are detective, access restrictions are preventive
  • ▸ No ISMS manual is required; clause 7.5.1 b leaves extra documentation to the organisation
  • ▸ Five whys follows one causal chain, fishbone maps many factors, Pareto prioritises known causes
  • ▸ Clause 10.1 improves suitability, adequacy and effectiveness, not efficiency or cost

Can you answer these without checking your notes?

In this scenario: "To certify faster, the sponsor wants core customer-facing systems left out of the ISMS scope" — what should you do first?
Clause 4.3 scope must reflect external and internal issues, interested party requirements, interfaces and dependencies. Excluding what customers rely on undermines the certificate's value and is likely to be challenged at Stage 1.
In this scenario: "The board proposes buying cyber insurance as the response to ransomware risk" — what should you do first?
Insurance is risk sharing: it reduces some financial consequences, but accountability, downtime and reputational impact remain. Combine it with risk modification such as backups and tested recovery, and have the risk owner accept what remains.
In this scenario: "Controls went live last week and management wants the Stage 2 audit booked immediately" — what should you do first?
Stage 2 tests whether the ISMS works, which needs operating records, a completed internal audit and a management review with recorded decisions. Book it once that evidence exists, after a Stage 1 readiness review.

Common Exam Mistakes — What candidates get wrong

Implementing Annex A controls before the risk assessment

Clause 6.1.3 determines necessary controls from risk treatment; Annex A is then used to check nothing necessary was omitted. Rolling out controls first for quick progress produces unjustified controls and an SoA that cannot be defended.

Setting risk acceptance criteria after seeing the assessment results

Clause 6.1.2 a requires risk acceptance criteria and criteria for performing assessments to be set first, so results are consistent, valid and comparable. No method is mandated; ISO/IEC 27005 is optional guidance.

Letting the ISMS project manager approve residual risk

Clause 6.1.3 f requires risk owners, people with accountability and authority to manage the risk, to approve the risk treatment plan and accept residual risks. Neither the project manager nor an asset custodian satisfies it.

Measuring awareness by the number of sessions held

Clause 9.1 requires deciding what to measure, the methods, when, who measures, when results are analysed and who evaluates them. Effectiveness metrics show outcomes such as phishing report rates, not activity counts.

Closing a nonconformity once the immediate fix is applied

Clause 10.2 requires correction, evaluating the cause, checking for similar nonconformities elsewhere, corrective action to prevent recurrence and a review of its effectiveness. Retraining staff without root cause analysis rarely fixes a flawed process.

Resources to help you pass ISO/IEC 27001 Lead Implementer on your first attempt

Lead Implementer rewards risk-driven design. Check whether every control you choose traces to a treatment decision.