The ISO 27002 process is predictable once you know the sequence. Below is the standard path, with references to the specific control areasISO 27002 auditors focus on.
Typical end-to-end timeline: 2 – 8 months.
Step 1 — Scoping
Define exactly what's in scope: product lines, systems, offices, subsidiaries, and third-party processors. Over-scoping is the single biggest cause of ISO 27002 cost blowouts; under-scoping risks a scope gap at audit time.
Step 2 — Gap Assessment
Compare your current state against the ISO 27002 control set and produce a gap register. Teams typically run this with either an internal lead or a readiness-focused consultant.
Control areas you'll be assessed on
- Organizational controls (37 controls)
- People controls (8 controls)
- Physical controls (14 controls)
- Technological controls (34 controls)
Step 3 — Remediation
Close the gaps. In practice this is a mix of:
- Technical implementation — MFA, logging, encryption, access reviews, backups, vulnerability management.
- Policy and documentation — information security policy, incident response plan, risk register, data classification, vendor management.
- Process adoption — change tickets with approvals, periodic access reviews, management review meetings, awareness training.
Step 4 — Self-Attestation or Third-Party Review
ISO 27002does not strictly require an accredited auditor. Depending on who's asking (customer, regulator, insurer), you may need a self-attestation, a third-party opinion letter, or a readiness assessment report. Clarify this before signing an auditor.
Common Pitfalls
- Scope creep during the engagement. Freeze scope at kickoff.
- Policy without practice. Auditors verify behavior, not just documents.
- Last-minute evidence hunts. Evidence should be collected continuously, not scrambled for the audit window.
For cost breakdowns and budget tiers, see the cheapest path to ISO 27002. For when it's worth it, see when and why to pursue ISO 27002.