Cyber Essentials to ISO 27001 — a certification ladder, not a cliff
Most security consultants sell you readiness: a gap analysis, a colour-coded spreadsheet, and an invoice. You are still the one who has to pass. I take it the other way — through the assessor, through the pentest, to the certificate you can put in a sales deck or a data room. Every engagement is run on a compliance workspace I deploy into your own cloud tenant in the first week, so evidence starts accruing from day one, compliance stops being a quarterly fire drill, and timelines compress by roughly half against the industry-typical range — with no per-seat platform licence attached to any of it.

Cyber Essentials in Three Weeks
- A compliance workspace standing in your own cloud in week one, wired to your identity provider, cloud accounts, devices and repositories — collecting evidence on its own
- An answer pack for the questionnaire in week one, so your sales team can keep the deal moving while the work happens
- A dated plan you can send to procurement
- A scope and a gap list ranked by what fails first
- An audit date booked with the certification body
Certified, or you don't pay my fee.
The workspace and the evidence in it are yours. If ISO 27001 comes next, the same evidence is what it asks for.
- Cyber Essentials and Cyber Essentials Plus taken through to certification, assessor engagement included
- ISO 27001 ISMS scoped, built and run through Stage 1 and Stage 2 audit
- ISO/IEC 42001 AI management system scoped and built for teams shipping AI features, run through certification the same way
- SOC 2 Type I / Type II controls mapping when the buyer is American
- Policies, risk register, and supplier reviews written to survive an auditor — not template filler
- Scope defined deliberately: certifying the right boundary is what keeps the cost and the evidence burden sane
- A compliance workspace stood up inside your own cloud environment in week one — your data never leaves it
- Wired into the cloud, identity and device management you already run, so evidence collects itself
- Automated collection replacing screenshot-and-spreadsheet audit prep
- Control drift surfaced early, so you find out before the auditor does
- Joiner and leaver checks tied to the actual HR process rather than someone’s memory
- No per-seat licence, and handover so your team owns it — not me, and not a vendor
- Internal pentest first, so the external CREST/CHECK engagement holds no surprises
- Threat modelling (STRIDE) on the load-bearing flows
- Remediation done and re-tested through to closure — not handed over as a PDF
- Sitting between you and the testing firm so scope and findings are argued properly
- Network segmentation, MFA everywhere, and least-privilege IAM that survives a review
- Patch and vulnerability SLAs that are actually met, with the evidence to show it
- Centralised logging, alerting, and retention that satisfies an auditor
- Backup and disaster recovery tested on a schedule, with documented RTO and RPO
- Infrastructure as code, so a passing configuration stays passing
- SAST (Semgrep, CodeQL) wired into CI as a blocking gate
- Dependency scanning, SBOM, and patch policy (Renovate, Dependabot)
- Secret scanning at commit, pre-receive, and rotation playbooks
- Hardened defaults: authn/authz, headers, input validation, CSP
Almost nobody should start at ISO 27001. Each rung below is a certificate in its own right, and each one is the groundwork for the next — the technical evidence you build for Cyber Essentials is the same evidence ISO 27001 asks for later, so nothing is wasted. You can stop at any rung. Most companies climb one every twelve to eighteen months, as their customers start asking for more.
- 01
Cyber Essentials
2–3 weeksThe UK government-backed baseline, covering five technical control areas: boundary firewalls, secure configuration, access control, malware protection and patch management. Self-assessed, then independently reviewed by a certification body.
Unlocks: UK public-sector tenders that name it as a condition of bidding — plus the technical baseline every rung above reuses.
- 02
Cyber Essentials Plus
4–6 weeksRequires Cyber EssentialsThe audited version of the same five controls. An assessor runs authenticated vulnerability scans and tests your devices hands-on rather than reading your answers, so the configuration has to genuinely be right instead of merely described correctly.
Unlocks: NHS-adjacent and defence-adjacent procurement, and enterprise buyers who treat the self-assessed version as insufficient.
- 03
ISO 27001 + ISO 27701
3–6 monthsThe full information security management system — scope, risk assessment, Statement of Applicability, policies, internal audit and management review — taken through Stage 1 and Stage 2. ISO 27701 extends the same management system to privacy, so it is certified in the same audit by the same body rather than run as a second project a year later.
Unlocks: International enterprise procurement, security questionnaires answered with a certificate instead of a spreadsheet, and a defensible route to demonstrating UK GDPR, NIS2 and DORA obligations.
- 04
ISO/IEC 42001
3–5 monthsBest added after ISO 27001The AI management system standard: AI policy, risk and impact assessment, lifecycle governance and its own Statement of Applicability. It shares the management system clauses with ISO 27001, so on a company already certified most of the structure exists and only the AI-specific work is new.
Unlocks: Enterprise AI procurement questionnaires, and a running start on the EU AI Act high-risk obligations that apply from December 2027.
- 05
Surveillance and renewal
OngoingAn ISO certificate runs on a three-year cycle with an annual surveillance audit, and a management system that quietly stops running fails the next one. Retained support keeps the risk register, internal audits and management reviews actually happening rather than being rebuilt in a panic each year.
Unlocks: Certificates that stay valid, and a surveillance audit that stays uneventful.
Durations run from a standing start to certificate and assume a single cloud estate with central identity. Climbing two rungs at once is possible and often sensible — Cyber Essentials in particular is worth doing in the first month of an ISO 27001 project, because it forces the technical basics the standard will ask for anyway and puts a certificate in your hands while the longer project is still running.

Two things drive almost every certification project I get called into, and neither of them is a sudden interest in security. The first is a deal: an enterprise procurement team has sent a security questionnaire, or a public-sector tender has made Cyber Essentials a condition of bidding, and there is a signature waiting on the other side of it. The second is a raise, where an investor's technical diligence has surfaced a gap that needs closing before the round.
In both cases the clock is the problem. Certification is not difficult so much as it is administratively relentless — dozens of controls, each needing a policy that matches reality, evidence that the policy is actually followed, and a paper trail an auditor will accept. Firms lose months not because the security work is hard but because nobody owns the evidence, and the answer to "show me" is a scramble through screenshots.
So the first thing I do on any engagement is stand up a compliance workspace inside your own cloud tenant, wired to your identity provider, cloud accounts, device management and code repositories. From week one it is collecting control evidence continuously and holding the risk register, the Statement of Applicability and the audit trail in one place. The audit stops being a project you prepare for and becomes a report you export — the single biggest lever on how fast the timeline moves. It runs in your environment rather than a vendor’s, there is no per-seat licence, and when the engagement ends it stays with you.
What that workspace does not do — what no compliance tooling does — is fix the underlying infrastructure when a control genuinely is not met. So the honest division of labour runs like this. The workspace handles evidence, continuously and from week one. The certification body handles assessment. I handle the gap between what your systems currently do and what the standard requires them to do — the segmentation, the access model, the logging, the patch discipline, the backup testing, and increasingly the AI-specific controls ISO/IEC 42001 asks for — and then I sit with you through the assessment itself.
The accelerated timeline
The ranges below are what each stage typically takes end to end. Working with me compresses them because evidence starts collecting during scoping rather than after it, and I do the remediation engineering myself instead of handing you a findings report to action alone.
The workspace connects to your cloud, identity and HR systems during scoping, not after certification is decided — so the evidence trail is already months deep by the time the audit is booked.
I do the remediation myself rather than writing a report for someone else to implement, so fixing a gap and evidencing it happen in the same week instead of two sequential ones.
A wider scope reads well on paper and adds months to every stage. The gap analysis draws the smallest scope that genuinely covers what your customers are asking for.
Ranges assume a single cloud estate with central identity. Acquired subsidiaries, on-premise servers, or no SSO push every figure to the right — the gap analysis in the first three weeks is what turns a range into a date.
An audit on the calendar, a failed pentest to fix, or a procurement questionnaire asking for a certification you don't have yet — let's talk before the deadline moves.
- Weeks 1–3
Scope and gap analysis
- Decide what is actually in scope — the single biggest lever on cost, timeline and evidence burden
- Gap analysis against the standard(s), ranked by what will fail an assessment first
- Compliance workspace deployed into your tenant and connected to cloud, identity, HR and code systems
- Baseline evidence starts collecting automatically from day one
- Weeks 4–12
Close the gaps
- Infrastructure work: segmentation, IAM, MFA, logging, patch SLAs, tested backups
- Policies and risk register written to match how the company actually operates
- Internal pentest, with remediation tracked and re-tested to closure
- Joiner and leaver process wired to the evidence trail rather than run on memory
- Assessment
Through the audit
- Cyber Essentials submitted, or ISO 27001 / ISO 42001 Stage 1 and Stage 2 booked and run
- I am in the room for the assessment, not handing you a document beforehand
- Findings answered and closed out directly with the assessor
- Handover so your team owns the workspace and the surveillance cycle afterwards
- Cyber Essentials / Cyber Essentials Plus certificate
- ISO 27001 ISMS through Stage 2 audit
- ISO 27701 privacy extension certified in the same audit, where personal data is in scope
- ISO/IEC 42001 AI management system through certification, where AI is in scope
- A compliance workspace live in your own tenant, collecting evidence continuously, owned by your team
- Internal pentest report + remediation tracked to closure
- Secure SDLC document + CI security gates
Certification runs as a fixed-scope project with a target date, either standalone or alongside a retainer. Cyber Essentials is typically weeks; ISO 27001 and ISO/IEC 42001 are typically three to six months depending on scope and how much already exists.
Through to certificate, or the remediation is on me.
No one honest can guarantee an assessor's verdict. What I guarantee is that I stay until it closes: any finding raised against a control in my scope, I close at no additional fee, until you are certified.
- Cyber Essentials: certified, or you do not pay my fee. The certification body's own fee is separate and excluded.
- If the week-three gap analysis says your date is not achievable, you hear it then and can stop, having paid for three weeks.
- Excludes scope changes, systems added after the gap analysis, and controls you decline to implement.
- Your prerequisites and response times are named in the proposal, not assumed.
Questions I get asked about this.
Do we have to climb the whole ladder?
No — each rung is a finished certificate, and the right place to stop is wherever your buyers stop asking. If UK public-sector work is the goal, Cyber Essentials on its own may be the whole answer. If a single enterprise customer has sent an ISO 27001 questionnaire, you may need to go straight to rung three. The reason to think of it as a ladder rather than a menu is that the work compounds: the access control, patching and logging evidence built for Cyber Essentials is the same evidence ISO 27001 asks for, so climbing later costs far less than starting from scratch.
What is ISO 27701, and why is it bundled with ISO 27001?
ISO 27701 is a privacy extension to ISO 27001 rather than a standalone standard — it cannot be certified on its own. It adds privacy-specific controls on top of the same management system, which means the same auditor certifies both in the same visit. Doing them together costs a fraction of what a separate privacy project would, and it converts "we take GDPR seriously" from an assertion into a certificate you can send a customer. If you process personal data at any volume, it belongs in the same engagement.
How long does ISO 27001 actually take?
Typically three to six months from a standing start to Stage 2 audit, and the variance is almost entirely about two things: how tightly you scope, and how much already exists. A company with a single cloud product, an identity provider and reasonable engineering discipline sits at the short end. A company with acquired subsidiaries, on-premise servers and no central identity sits at the long end. The gap analysis in the first three weeks is what turns that range into a date.
What is ISO/IEC 42001, and do we need it?
It's the international management-system standard for AI, the same shape as ISO 27001 but for how you govern, risk-assess, and monitor AI systems rather than information security broadly. Worth pursuing once AI features are customer-facing or a procurement/investor questionnaire starts asking AI-specific questions. If you already hold ISO 27001, the ISMS foundations overlap heavily, which is usually what keeps the ISO 42001 timeline at the shorter end.
And Cyber Essentials?
Weeks, not months. Cyber Essentials is a self-assessment against five technical control areas, reviewed independently. Cyber Essentials Plus adds a hands-on technical audit, so it needs the underlying configuration to genuinely be right rather than merely described correctly. For most small companies the honest answer is that certification takes days and fixing what it uncovers takes the rest of the time — which is why I would rather look at your estate before quoting you a date.
Do we need to buy Vanta or Drata?
No. Every engagement runs on a compliance workspace I deploy into your own cloud tenant in week one — it holds the risk register, the Statement of Applicability, the policy set and the evidence trail, and it connects to the cloud, identity and device management you already pay for. That means no per-seat licence, no data leaving your environment, and nothing to keep renewing once you are certified. It is not magic: it evidences controls, it does not implement them, and the implementation is the part I do. If you already run Vanta or Drata I will work with what you have rather than move you off it mid-project.
Can you guarantee we pass?
No one honest can, because the assessor makes that call, not me. What I can tell you is that the failures I see come from predictable places — a scope drawn too wide, controls documented but not implemented, or an internal pentest skipped so the external one becomes the first real test. Doing the internal pentest first, remediating properly, and scoping deliberately is what makes the assessment uneventful. If the gap analysis says the target date is unrealistic, you hear that in week three rather than at the audit.
We already failed a pentest. Can you fix it?
Yes, and it is a common starting point. A failed or ugly pentest report is a prioritisation problem more than a security one — the report lists everything it found, in its own order, with no reference to your architecture or your deadline. The work is triaging it against real exploitability, doing the infrastructure fixes properly rather than patching symptoms, and getting it re-tested to closure. I will also sit between you and the testing firm on the retest so scope and findings get argued rather than accepted.
Do we need ISO 27001, or is Cyber Essentials enough?
It depends entirely on who is asking you for it. UK public-sector contracts handling personal data require Cyber Essentials by procurement policy, so that is a hard gate. Enterprise and international buyers tend to ask for ISO 27001 or SOC 2 by name. If nobody has asked yet, Cyber Essentials is the sane starting point — it is fast, it is the recognised UK baseline, and the controls underneath it are the same foundation ISO 27001 builds on later. Certifying ahead of demand mostly buys you an annual renewal cost.
What does it cost?
It varies too much with scope for a number on a page to be useful, and anyone quoting you one before looking at your estate is guessing. There are three separate costs to plan for: the certification body's fees, the independent testing along the way — a pentest, and for ISO an internal audit that has to be run by someone other than me — and the engineering work to close the gaps. That third one is the one that moves, and the gap analysis is what sizes it. Book a call and I will give you a real range once I know what is in scope.
More services
View all →The CTO Seat
You are the one who signs off the spend. This is the seat that shows you the working. Technical direction owned, the team unblocked, fundraising and hiring run as workstreams, and a technical voice that answers to your board rather than to a supplier.
The Twelve-Week Build
From a demo to software your customers actually use. Architecture, full-stack build, data and AI, infrastructure and delivery — owned end to end by one accountable engineer, on a fixed shape with a date attached.
A build you can't evaluate, a demo that has to ship, or a certificate a contract is waiting on.
Book a 30-minute discovery call. If we're not a fit, I'll tell you on the call — and point you toward someone who is.