"How much does ISO 27001 cost?" is usually the first question, and the honest answer is "it depends on what you put inside the scope". A 30-person SaaS company certifying one product and its cloud environment faces a very different bill from a 2,000-person IT services firm certifying every office and delivery centre. What does not change is where the money goes. Once you understand the components, you can control most of them.
What is ISO 27001, briefly?
ISO/IEC 27001 is the international standard for an information security management system (ISMS): a structured way to identify information security risks and treat them. The current edition is the 2022 version, amended in 2024 to add a climate-change consideration to the organisational context. Its Annex A lists 93 reference controls in four themes: organisational, people, physical and technological. They are a reference set, not a mandatory checklist; you choose and justify controls in a Statement of Applicability (ISO/IEC 27001 overview).
ISO does not certify companies. Independent certification bodies do, usually accredited by a national accreditation body. A certificate typically runs on a three-year cycle, with a first surveillance audit within twelve months and recertification at the end of the cycle.
If you hold an older ISO 27001:2013 certificate, note that the transition period to the 2022 version ended on 31 October 2025 (LRQA).
The five cost components
1. Gap analysis
An assessment of where you stand against the standard: which clauses and controls are already in place, which are partial and which are missing. It produces the work plan. For a small, well-run company this can be short; for a company with no written policies, it is longer.
Keep it lean: do it once, properly, with a person who has taken companies through certification. A good gap analysis prevents paying for work you do not need.
2. Implementation
Usually the largest cost, and mostly your own team's time. It includes:
- defining the ISMS scope, context and interested parties;
- a risk assessment and risk treatment plan;
- the Statement of Applicability;
- policies and procedures: access control, acceptable use, supplier security, incident response, backup, change management, secure development;
- fixing real control gaps: MFA, logging, encryption, asset inventory, offboarding, vendor reviews;
- awareness training for staff.
Keep it lean: write policies that describe what you actually do, in plain language. A 10-page access control policy nobody follows fails audits; a two-page one that matches practice passes.
3. Tools
You may need some technology to operate controls: endpoint protection, MFA, a password manager, log collection, backup, vulnerability scanning, and something to track risks, assets and evidence. Many companies already pay for most of these inside Microsoft 365, Google Workspace or their cloud provider without using them fully.
Keep it lean: map controls to tools you already have before buying anything. A compliance automation platform helps larger or fast-growing teams, but a disciplined spreadsheet and shared drive are enough for many small companies.
4. Internal audit and management review
Before certification, the standard requires an internal audit of the ISMS and a management review. The internal auditor must be objective, so it is often an external person or a trained colleague from outside the scope.
Keep it lean: treat the internal audit as a rehearsal. Every finding closed here is one the certification auditor will not raise.
5. Certification body fees
The certification body charges for auditor days. The initial certification has two stages:
- Stage 1: a readiness review of documentation and scope.
- Stage 2: the conformity audit, checking that controls are working, with evidence and interviews.
After that come annual surveillance audits and a recertification audit in year three. Auditor days depend largely on headcount in scope, number of sites and complexity. Always budget for the full three-year cycle, not just year one.
Keep it lean: get quotes from more than one accredited body, confirm accreditation, and ask how they calculate audit days.
Cost drivers at a glance
| Driver | Effect on cost | How to control it |
|---|---|---|
| Headcount in scope | More people means more auditor days and more training | Scope only the teams that handle the in-scope service |
| Number of locations | Each site may need visiting | Exclude sites that do not handle in-scope information, with justification |
| Current maturity | Missing basics means more implementation | Fix MFA, backups and access first; they are needed anyway |
| Technical complexity | Many systems mean more risk assessment and evidence | Start with one product or platform |
| Deadline pressure | Rushed projects buy more consultant time | Start well before the client or tender date |
| Ongoing operation | Controls need running every month | Assign owners and a simple evidence calendar |
The hidden cost: running the ISMS
Certification is not a one-time purchase. Access reviews, risk reviews, supplier checks, internal audits and management reviews must keep happening, with evidence, or the first surveillance audit will find nonconformities. Budget a few hours a week of an owner's time. Companies that treat ISO 27001 as a project with an end date usually struggle in year two.
Five ways small teams waste money on ISO 27001
- Scoping the whole company by default when the client only asked about one product or service.
- Buying template policy packs and spending weeks editing documents that describe a different company.
- Buying tools before deciding the controls, then paying for features nobody uses.
- Leaving technical fixes until after stage 1, so the stage 2 audit turns up gaps that need a second visit.
- No named owner once the consultant leaves, which is how surveillance audits start failing.
Each of these is avoidable with a clear scope statement and a single accountable person inside the business, usually supported by a senior security adviser for a few days a month.
How long does it take?
For a small, focused scope with committed management, a few months from gap analysis to stage 2 is realistic. Larger scopes or teams starting from nothing take longer. The ISMS must also run for long enough to produce evidence: auditors want to see controls operating, not just documents.
Is ISO 27001 worth it for a small Indian company?
It is worth it when a customer, tender or market requires it, or when you sell to European and enterprise buyers who send long security questionnaires. A certificate answers many of those questions at once. If no client has asked, a lighter step, such as fixing the basics and documenting controls, may be the better first investment. If US clients are your main market, compare it with SOC 2 first.
How Cehpoint can help
Cehpoint's ISO 27001 and SOC 2 readiness service covers gap analysis, risk assessment, policies written to match how you actually work, technical control fixes and internal audit, with a published starting price on the service page. We prepare you for the certification body's audit; certification itself is issued by an independent accredited body. For the technical controls, our VAPT service provides the vulnerability management evidence auditors ask for.