ISO/IEC 27001:2022 sets the requirements for implementing, maintaining and continually improving an information security management system (ISMS). The standard helps organisations of any size identify risks, define responsibilities, select controls and evaluate their effectiveness. For organisations that need to demonstrate conformity to clients or partners, independent certification can be an additional goal. This guide explains the main implementation steps, the costs involved and how to prepare for a certification audit.
ISO/IEC 27001:2022 sets out the requirements for establishing, implementing, maintaining and continually improving an information security management system (ISMS). It covers information security risks across people, processes, physical information, suppliers and technology, not only IT systems. Any organisation can adopt the standard without seeking certification. Certification is a separate, optional step: an accredited certification body assesses your ISMS and confirms that it conforms to the standard. It becomes necessary only when a customer, contract or other obligation requires it.
The management system requirements sit in clauses 4 to 10: context and scope, leadership, planning (including risk assessment and risk treatment), support, operation, performance evaluation and improvement. Several of these are easy to overlook:
Annex A lists 93 controls across four themes: organisational, people, physical and technological. It is a reference catalogue, not a checklist you must complete, and it is not exhaustive: your risk assessment may show you need controls that are not in it. Under clause 6.1.3 d, the Statement of Applicability (SoA) records the necessary controls, why each is included, whether it is implemented, and why any Annex A control is excluded. It must reflect your real risk treatment decisions.
You do not have to cover your entire organisation. Many organisations scope the ISMS around a specific service line or product, which keeps it manageable. Define the scope carefully at the start: it is difficult to change once the project is underway.
ISO 27001 is not legally mandated in most sectors. Businesses adopt it, and often certify against it, for four main reasons:
If none of these apply, ISO 27001 may not be the right priority. Cyber Essentials Plus or a targeted security assessment may deliver more value for less effort.
The first five steps build and run the ISMS. The sixth applies only if you pursue certification.
Staff are a common entry point for security incidents, and awareness is a requirement of the standard. Cover phishing, password practice, incident reporting and handling sensitive data, include it in onboarding and refresh it regularly. Keep completion records: auditors ask for them.
Nonconformities are common, particularly at Stage 2. A minor nonconformity does not usually prevent certification: the certification body sets a period to submit a corrective action plan or evidence of the fix. A major nonconformity means the certificate cannot be issued until it is resolved, and may require a follow-up visit. Typical causes are controls documented but not operating, missing evidence, and gaps between the SoA and what the auditor finds. Closing internal audit findings properly is the best prevention.
Auditors look for records, not intentions. This overview shows the key evidence at each stage. For practical tips on organising it, see our guide to IT audit readiness.
These are planning scenarios, not rules. In our projects, scoping and gap assessment usually take two to four weeks and documentation four to eight weeks. The period of operating the ISMS before certification depends on scope, how often key processes run and what the certification body expects; we use three to six months as a planning reference. Internal audit takes one to two weeks, and the certification body sets the interval between Stage 1 and Stage 2.
The most common causes of delay are scope creep and over-engineered documentation. Policies for a 10-person business do not need to be 40 pages long.
Many organisations try to implement all 93 controls regardless of risk, while others exclude whole themes too quickly. A SaaS company without its own data centre may find certain specific physical controls not applicable, but it must still assess offices, equipment, remote work, physical access and the disposal of assets. Every exclusion in the SoA must be justified by your scope and risk assessment.
The ranges below are indicative Cyvra estimates based on our own projects, not market averages. Categories may be bundled differently by other providers. Your final cost depends on scope, maturity, the number of sites and systems, regulatory complexity and quotes from certification bodies. Implementation costs and certification body fees are separate.
Also budget for internal staff time and any technical improvements the gap assessment uncovers, such as new tooling or configuration work. Organisations that do more of the work internally, or start from a strong baseline, spend less on consultancy. The recertification audit in year three usually costs about the same as the original Stage 2.
"The standard is scalable. A 15-person professional services firm and a 150-person SaaS business need different ISMS implementations, and the standard accommodates both. The mistake is treating it as a one-size enterprise exercise."
The standard requires continual improvement, so the work continues. Keep monitoring and measurement running, hold management reviews, log and review incidents, update the risk register when the business or threat landscape changes, and close nonconformities with corrective action. Staff turnover is a common cause of ISMS drift, so keep awareness training in onboarding.
Surveillance audits take place roughly every 12 months and sample part of the ISMS, including follow-up of earlier findings. At year three a recertification audit covers the full system. Organisations that keep the ISMS current find it straightforward; those that update records only in the weeks before tend to find it stressful and expensive.
If you are adopting AI, ISO/IEC 42001 uses the same management system structure, so it can build on your ISMS.
The most valuable first step is a gap assessment. It typically takes two to four weeks, including scoping, and gives you a project plan with estimated effort per workstream before you commit to a timeline or budget. If a client has asked for ISO 27001, check their deadline and whether Cyber Essentials Plus would meet their needs in the interim.
You do not need a consultant. A consultant can help you interpret the requirements, define the scope, organise the project and find gaps, but certification depends on the conformity you demonstrate and on the certification body's independent assessment.
If you are not sure where ISO 27001 fits, a cybersecurity roadmap maps it against your existing controls. For the source material, see the ISO/IEC 27001:2022 page at ISO and ISO's practical guide for SMEs.
Cyvra works with businesses that need ISO 27001 to meet a client requirement, satisfy a regulatory review or build demonstrable security maturity. Most arrive with a specific trigger: a procurement questionnaire, a new contract or a board decision.
An engagement can cover the full project, from scoping to preparing for the certification audit. What you receive:
Most engagements are delivered by a single consultant, so the person who helped build your ISMS should not be the only one auditing it. We agree the internal audit approach with you at the start: usually an independent internal auditor we can recommend, or someone in your organisation we prepare to carry it out, with our role limited to support rather than auditing our own work. After certification, we can support surveillance audits and risk register maintenance.
If a client has asked for ISO 27001 or you have a deadline in mind, get in touch. The first step is a short call to understand your situation before we recommend a scope and approach.
No. Annex A is a reference catalogue. You select the controls your risk assessment shows are necessary, and the Statement of Applicability records why each is included, whether it is implemented and why any Annex A control is excluded. You may also need controls that are not in Annex A.
No, unless a contract, customer or other obligation requires it. You can implement an ISMS according to ISO/IEC 27001 without certifying. Certification is an optional external assessment by an accredited certification body.
It varies with scope, existing maturity and available resources. As an illustrative Cyvra planning scenario, six to nine months is realistic with a reasonable security baseline, and nine to twelve months when starting from minimal controls. The standard does not set a fixed operating period before certification.
Separate the cost lines: implementation, internal staff time, optional consultancy, technical improvements and certification body fees. Cyvra's indicative estimate for certification body fees is £2,500 to £7,000 for Stage 1 and Stage 2, with lower annual surveillance fees. Get quotes from accredited certification bodies for your scope.
Cyber Essentials is a UK government-backed scheme covering five basic technical controls: firewalls, secure configuration, user access control, malware protection and security update management. It is relatively quick to achieve and required for some UK government contracts. ISO 27001 is a full management system standard covering governance, risk management, people, physical security, suppliers and technology, and carries more weight with enterprise and international clients.
No. A consultant is not mandatory, but can help you interpret the requirements, define the scope, organise the project and identify gaps. Whether you are certified depends on the conformity you demonstrate and on the certification body's independent assessment.
Required by clause 6.1.3 d, the Statement of Applicability (SoA) lists the necessary controls, the justification for including them, whether they are implemented, and the justification for excluding any Annex A controls. It must reflect your real risk treatment decisions, not a generic template.
Cyvra's ISO 27001:2022 Readiness Checklist covers all 118 check items across every ISMS clause and Annex A control. Open in any browser, mark status, add evidence notes, and save as PDF. No sign-up needed.
Download the Checklist
Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile
A gap assessment gives you a project plan, timeline, and cost estimate before you commit to anything.
Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.