ISO/IEC 27001 is a management standard, not a checklist of firewalls. Certification bodies audit whether your information security management system (ISMS) is planned, implemented, monitored, and improved — and whether the evidence shows it is actually running. The first 90 days set that trajectory.
Days 1–30 — Scope, leadership, and the risk register
- Define the ISMS scope: which services, systems, locations, and processes are in — and honestly, which are out.
- Name a management owner and get explicit leadership commitment; auditors will talk to them.
- Stand up the risk assessment methodology and run the first risk assessment with the people who actually operate the systems.
A scope that is too ambitious is the single most common way projects slip. Scope for the certificate your business needs to sell, not for every system that exists.
Days 31–60 — Controls that exist outside of documents
Map your risks to Annex A controls and implement the gap. Prefer controls that produce their own evidence: access reviews that export from your identity provider, vulnerability scans that archive their own reports, deployments that only proceed through a reviewed pipeline. Policies should describe what really happens — never the reverse.
- Asset inventory and ownership: the table stakes for everything else.
- Access control lifecycle: joiner-mover-leaver with tickets as evidence.
- Change and deployment management: review, approve, log.
- Incident response: one written path, one tabletop exercise, one after-action record.
- Supplier security: know who touches your data and what you told them.
Days 61–90 — Make the system run itself
- Automate evidence collection: control-by-control, decide what generates it automatically and who owns the exceptions.
- Run the first internal audit — not a performance for the external auditor, a real look for yourself.
- Hold the management review with real inputs: risks moved, incidents, audit findings, resourcing decisions.
- Book the stage 1 audit only when the internal audit says you are ready — the gap analysis is done when the awkward questions have nowhere to go.
“Certification is issued by the independent certification body. Our job is to make their audit boring — in the best possible way.”
The engineer's advantage
Compliance programs fail when they are written by people who will never operate the systems. When controls are designed by engineers, evidence flows from production instead of from screenshots, and the audit becomes a verification of reality rather than a reconstruction of it.