ISO 27001 Consultant for SMEs

ISO 27001 has a reputation for taking a year and a small department. However, the work behind readiness can be straightforward: a risk assessment, a management system that fits how you run, and the evidence to pass an external audit.

I have built and maintained a certified ISMS for years, including the surveillance audits that follow certification. This experience matters because the difficult part is not writing the policies, it is making sure the business still follows them six months later, when everyone has other things to do.
metasploit
Metasploit
malwarebytes
Malwarebytes
fortinet
Fortinet
crowdstrike
Crowdstrike
bitwarden
Bitwarden
azure-intune
Intune
azure-entra-managed-identities
Entra
wireguard
Wireguard
sonicwall
SonicWall
openvpn
OpenVPN
microsoft-defender
Defender
microsoft-azure
Azure
sentinelone
SentinelOne
qualys
Qualys
okta
Okta
cisco-mono
Cisco
Vanta
Vanta
metasploit
Metasploit
malwarebytes
Malwarebytes
fortinet
Fortinet
crowdstrike
Crowdstrike
bitwarden
Bitwarden
azure-intune
Intune
azure-entra-managed-identities
Entra
wireguard
Wireguard
sonicwall
SonicWall
openvpn
OpenVPN
microsoft-defender
Defender
microsoft-azure
Azure
sentinelone
SentinelOne
qualys
Qualys
okta
Okta
cisco-mono
Cisco
Vanta
Vanta

ISO 27001 is proof you are doing what you say you are.

The myth is that ISO 27001 is a documentation project, simply writing policies, it's not. You can write every policy in a fortnight and still fail, because the auditor is not marking your prose. They are checking whether the thing you wrote down is the thing you actually do. Every action you and your staff take should follow the procedures you set, if you say you run an access review every quarter you need to be able to prove it. If suppliers are assessed before approval, show the assessment. If incidents follow a defined process, show who owns it and what happened the last time it was used.

The most common way to fail: A folder full of policies that say one thing, while the business does another. (In our experience).

The ISO 27001 framework

ISO 27001 is the international standard for information security management.
It requires you to build an Information Security Management System (an ISMS), that identifies risks, applies appropriate controls and to ensure those controls keep working.

For certification, an independent certification body has to audit your ISMS and confirm it meets the standard. For UK businesses, this will usually be through a UKAS-accredited certification body.

What an ISMS needs

A working ISMS needs a clear scope, a proper risk assessment, documented controls and evidence that those controls are being followed.

ISO 27001:2022 includes 93 Annex A controls across four areas. Your Statement of Applicability records which controls apply, how they are implemented and why any are excluded.

You also need ongoing internal audits, management reviews and evidence that the system is being maintained.

How long until you are audit ready?

There is no universal timescale, but with an experienced ISO 27001 consultant, for most businesses, ISO 27001 audit readiness takes weeks rather than months, however, your starting point makes a major difference.

A business that already has sensible security controls, documented processes and people following them consistently may already have much of the groundwork in place. If policies are missing, or responsibilities are unclear and processes exist only in someones head, there will be more to build.

Complexity matters. A single UK office is very different from an organisation operating across several countries, multiple cloud platforms, outsourced suppliers and several different technical environments.

The larger factor is your availability, as ISO 27001 cannot be completed entirely by a consultant, decisions need to be made, evidence needs to be provided and people need to take ownership. If every decision takes a week, the project naturally takes longer.
0
Typical Turnaround

What does ISO 27001 cost?

ISO 27001 has three different costs, and separating them out makes the budget much easier to understand.

First is the certification body. This is the unavoidable external cost for Stage 1, Stage 2, annual surveillance and later re-certification. The fee depends on scope, complexity and the audit time required.

Second is getting ready. This is where good ISO 27001 consultancy should save time rather than manufacture it. The aim is to identify what already works, fix what does not, and avoid spending months producing things the business never needed.

Third is keeping the certificate. A cheap implementation becomes expensive very quickly if the resulting ISMS needs constant consultancy just to stay alive. I would rather leave you with a system your own people can run between audits.
0
ISO 27001 Gap Analysis

What an ISO 27001 consultant actually does.

01. Scope and assess

Decide what the system covers, then look honestly at what could go wrong inside it. Get the scope wrong here and everything downstream is either pointless or enormous.
Scope definition
Risk assessment
Gap analysis
Asset & control mapping

02. Build the system

Assemble the ISMS to fit how you really operate, not a template of how a textbook company operates. Controls chosen for reasons you can defend out loud.
ISMS build
Policy set
Statement of Applicability
Annex A control selection

03. Make it run

Put the controls into normal working life and start producing the evidence an assessor will ask to see. If a control disappears as soon as people get busy, it needs fixing before the auditor finds that out for you.
Internal audit
Management review
Evidence collection
Staff security awareness

04. Pass and keep it

Prepare for Stage 1 and Stage 2, deal with findings properly, then make the ISMS maintainable enough to survive the years after certification without becoming somebody's second full-time job.
Stage 1 & 2 readiness
Certification body liaison
Surveillance support
Recertification plan

What to actually budget for.

WhatTypicalNotes
Certification body auditDay-rated, scaled to scopeStage 1 plus Stage 2, then a surveillance audit each year. The unavoidable external cost.
Getting readyWeeks with senior help, months aloneThe line a good consultant shrinks the most.
Internal timeReal hours, not zeroYour people still need to answer questions, provide evidence, approve decisions and own controls.
ToolingFrom spreadsheets to dedicated platformsA small ISMS can run perfectly well without an expensive compliance platform. Tooling should match complexity, not fashion.
Ongoing cycleAnnual surveillance, three-year certification cycleBudget for maintaining the certificate, not simply achieving it once.

What catches UK businesses out.

This was the one I repeatedly had to mop up while maintaining an ISMS myself. An engineer needed a component or service urgently. A salesperson found a supplier they wanted to use. Somebody placed the order, nobody wanted the extra admin of sending the supplier questionnaire, and the due-diligence process was skipped.
Months later that supplier could be operationally important, while the review that should have happened before approval still did not exist. I would then be tracing the decision backwards before surveillance audit, getting the assessment completed and repairing the evidence trail.

- The document trap. They write beautiful policies and assume that was the job. The awkward audit question is usually some variation of: "Show me the last time you did this."
- The scope dodge. Draw it too narrow and the certificate means nothing to the customer who asked. Too wide and you drown. Scope needs a business decision, not a default template.
- The forgotten rhythm. Internal audits, management reviews, access reviews, supplier reviews and corrective actions happen on a cycle. They cannot all be convincingly hurried the week before audit.
- The certificate nobody values. Certification is only useful if the organisation asking for it recognises the route you took. For UK commercial use, check the certification body's accreditation rather than assuming every logo carrying "ISO 27001" means the same thing.

A perfect binder. An empty company.

AI can produce a polished policy set, risk register and Statement of Applicability remarkably quickly. But does it describe your business, the actual processes your staff follow and the laws you must abide by. Will you end up with a policy nobody has read and when an auditor asks for evidence, you have no idea what they are talking about and nothing to show?

An auditor can pull one thread and test whether the process exists outside the document. Who approved the supplier? Show the review. Who removed the leaver's access? Show the record. When was the risk last discussed? Show the decision.

I want the certificate to mean something.

No year of meetings to decide who attends the next meeting.

Beyond that, the aim is very simple: build an ISMS your staff can actually operate, an auditor can verify, and a customer can trust. If Cyber Essentials genuinely answers the requirement, I may say so. If ISO 27001 is justified, we build it around the business rather than forcing the business to perform a template.

The right certificate is the one that still reflects reality when the auditor comes back.
ISO-ready from 21 days
Built around your deadline
Evidence over promises
Truth Over Comfort
Whole-Business Diagnosis
Senior-Led Execution

ISO 27001 questions, answered

Erryn.io - ISO 27001 Consultant - Connected Systems

What Is an ISO 27001 Consultant?

An ISO 27001 consultant helps define the scope, assess risk, build or repair the ISMS, implement controls, organise evidence and prepare the business for an external certification audit.

I have also maintained a certified ISMS from inside the business, including its surveillance audits. That gives me a useful perspective on what happens after the implementation project ends, when the system has to survive ordinary working life.
ISO 27001 is the international standard for information security management. It requires an ISMS that identifies risks, decides how they will be treated and produces evidence that the resulting controls continue to operate. An independent certification body audits the system for certification.
ISO 27001 contains the requirements you can certify against. ISO 27002 provides detailed guidance on information-security controls. If you want certification, ISO 27001 is the standard the certification audit is assessing.
Audit readiness can take weeks for an SME that already has sensible controls and people available to make decisions. Starting from little documentation or evidence takes longer.

Certification itself also depends on external audit availability and the timing of Stage 1 and Stage 2, so I separate "ready for audit" from "certificate issued" rather than pretending they are the same date.
Three parts: the accredited auditor's day-rated fee (unavoidable), getting ready (the part a good consultant shrinks), and the ongoing surveillance and recertification cycle (the part people forget). There is no honest single number before someone has seen your scope. Anyone giving you one is quoting a package.
Often Cyber Essentials is enough, and we will say so. ISO 27001 earns its cost when large customers, regulated sectors or international deals demand it, or when a competitor who holds it is beating you to contracts. If nobody is asking, the cheaper certificate may serve you better. Other security standards and certifications, such as PCI certification, answer different questions.
It runs on a three-year cycle. An accredited body audits you initially, checks you each year with a surveillance audit, and fully recertifies you in year three. Skip the upkeep and you lose it, which is why a system built to be lived in beats one crammed together to pass once.
It can write every document overnight, and they will look immaculate. It cannot make your organisation actually do what they describe, and that is the only thing the auditor checks.

Those operational controls, and the evidence they produce, are what the audit eventually tests.
If you sell software or connected products into the EU, the Cyber Resilience Act applies wherever you are based. Reporting duties for actively exploited vulnerabilities and serious incidents began on 11 September 2026, with the wider product requirements following in December 2027. In practice that means an incident plan with its own notification route, separate from GDPR, a record of what sits inside your software, and a plan for security updates. If you only use software rather than sell it, the Act sits with your suppliers, though they may start asking you questions.
Yes, but it does not finish the job. A well-built ISMS gives you the policies, risk process and evidence habits that SOC 2 and other frameworks build on, so you are not starting again. SOC 2 still needs a formal control mapping, then evidence that the controls operated over a set period. Build the ISO 27001 system properly once and the next standard becomes a mapping exercise rather than a rewrite.
Give one senior person enough authority to challenge shortcuts, then assign clear owners to the controls they actually operate.

Access, suppliers, incidents, HR and technical controls do not all belong to the same person. The ISMS works better when responsibility follows the real business process and evidence is recorded when the activity happens, rather than reconstructed at year end.

Find out if you even need it.

Most ISO enquiries start with a customer demand or a tender requirement, and a fair number of those turn out not to need the full standard at all.

A short conversation is usually enough to establish what is actually being asked for, how much of the groundwork you already have, and whether ISO 27001 certification is the proportionate answer.