ISO certification statistics 2018 to 2025: interactive chart

Key Takeaways

  • Reported ISO 27001 certificates grew about 30% in 2025, the fastest of the five standards tracked since 2018.
  • ISO 9001, 14001 and 45001 grew about 9% to 11%, and ISO 50001 about 23%.
  • Excluding China, ISO 27001 grew about 42%. That view is Tempo Audits’ own calculation.
  • ISO 42001, the AI management standard, appears in the survey for the first time in 2025.
  • The dip in 2023 comes from China’s data being largely missing, not from a real fall in certification.

Can a Startup Get ISO 27001 Certified?

Yes. ISO 27001 certification is open to organisations of any size, including startups with just one person. There is no minimum headcount: the certificate applies to the organisation, not its founder.

The scope should reflect how the startup actually operates: its services, systems, people and locations. A clear scope helps define what the ISMS covers and gives the audit a practical boundary.

At Tempo Audits, we work with early-stage tech businesses, including one-person companies and teams of two to five. A small team can build an effective ISMS; it needs clear responsibilities and controls that work in practice, not a dedicated compliance department.

Why is ISO 27001 Certification Important for Small Businesses and Startups?

For a startup, ISO 27001 can turn information security into something the business can explain and demonstrate. A well-run ISMS gives the team a clear way to manage risk, respond to customer questions and keep security work moving as the company grows.

ISO certifications worldwide, 2018 to 2025

Reported ISO certificates by standard. Switch standards on and off to see how fast each one is growing.

View

Why this switch? China is a large share of reported certificates, and its data was largely missing in 2023. Some drops in this chart are reporting gaps, not real falls in certification. Switch to Excluding China to see the picture without it.

Reported certificates (not organisations).

Speed
How to read this chart
  • Each bar is the number of valid certificates reported to the ISO Survey for one standard in that year. These are certificates, not organisations: one organisation can hold more than one.
  • Switch a standard off and the scale adjusts. With ISO 9001 off, the growth of ISO 27001 is much easier to see.
  • Excluding China removes China's reported certificates from every standard. China accounts for a large share of the totals (for ISO 27001, 23% to 37% in most years) and its data was largely missing in 2023. This view is Tempo Audits' own calculation from the ISO Survey country-level data.
  • Some years need care. The note under the chart explains the reporting issues for each flagged year. The survey relies on voluntary reporting, so counts can move because of who took part as well as real change.
  • Figures come from ISO's country-level survey data. In some years between 2018 and 2023, ISO's published headline totals differ slightly from these figures (by up to about 3% for certificates; for example ISO 27001 in 2023 is 47,291 here and 48,671 in ISO's published note). 2024 and 2025 match exactly.
  • UK and Germany are not shown separately, because reporting coverage for both changed in several years.
  • Exact growth from 2024 to 2025 (worldwide, then excluding China): ISO 27001 29.9% and 42.4%; ISO 9001 9.3% and 14.1%; ISO 14001 9.3% and 16.7%; ISO 45001 10.5% and 23.1%; ISO 50001 23.2% and 28.7%.
  • ISO 42001 (AI management systems) appears in the survey for the first time in 2025, with 271 certificates, so it has no growth rate yet. The USA has the most (100), followed by India (25) and Korea (24).
  • Names: ISO 27001 and ISO 42001 are formally titled ISO/IEC 27001 and ISO/IEC 42001. They are shortened here to save space.

Source: ISO Survey, available via IAF CertSearch (https://www.iafcertsearch.org/services/iso-survey). Country-level results for 2018 to 2025, data as at 31 December each year. Excluding China figures are Tempo Audits' own calculation.

Chart by Tempo Audits, a UKAS accredited ISO 27001 certification body. If you share or embed this chart, please keep this attribution.

Build an ISMS That Fits Your Startup

You don’t need a large compliance team to run an ISMS. You do need someone to coordinate it, a clear scope and controls that are part of the way your startup operates.

1. Give someone responsibility for the ISMS

In a small team, the founder, CTO, COO or operations lead may take ownership alongside their other responsibilities. They coordinate the work and keep it moving; information security still needs attention across the business.

2. Define what the ISMS covers

Set out the services, systems, people and locations included in your scope. It should reflect how the startup actually handles information, so the audit assesses the business you run rather than an artificial boundary.

3. Assess risks and choose controls

Identify the information security risks your startup faces, then decide how to address them. Record the relevant Annex A controls and explain your choices in the Statement of Applicability, including which controls apply and which do not.

4. Put the controls into everyday use

Policies are only part of the system. Your team also needs to follow the controls and keep evidence of activities such as access reviews, backups or incident handling. At Stage 2, Tempo Audits checks that the ISMS is operating in practice, not just documented.

How Much Does ISO 27001 Certification Cost for a Startup?

For a 10–50-person tech startup, the Stage 1 and Stage 2 certification audit fees vary with the number of people operating under the ISMS. The table gives the relevant headcount bands and the corresponding audit time and cost.

Headcount operating under the ISMSStage 1 and Stage 2 audit time, including planning and reportingTypical audit cost
1-103.5-5.5 days£3,500-£5,500
11-154.5-6.5 days£4,500-£6,500
16-255-7.5 days£5,000-£7,500
26-456-9 days£6,000-£9,000
46-657-11 days£7,000-£11,000

These are typical market ranges for the initial certification audit, not a fixed quote. Tempo Audits’ fees are often towards the lower end; the final amount depends on your scope, risk profile and operational complexity. Surveillance audits come after certification, in Years 2 and 3, the starting cost for the same is £1,850.

For a more detailed breakdown, check out our guide on ISO 27001 certification costs.

Optional caption.

How Long Does ISO 27001 Certification Take?

For a startup, the full journey usually takes three to six months. The audit itself is much shorter: the time is mostly spent building and running the ISMS, completing an internal audit and management review, and gathering evidence that security controls work in practice. At Tempo Audits, we plan the certification stages around your readiness, so the timeline reflects the work your business actually needs to complete.

MilestoneTypical timingWhat happens
Scope and preparation1-3+ monthsDefine the ISMS scope, assess risks, implement controls and prepare evidence. The time depends on how much is already in place.
Internal audit and management reviewDuring preparationCheck that the ISMS is working across its scope, record any findings and review its performance with management.
Stage 1 auditUsually 1 day for a startup with 1-10 people in scopeWe review the ISMS documentation and readiness for Stage 2.
Stage 1 follow-upAround 3 weeksYour team has time to address any points from Stage 1 and prepare for the next audit.
Stage 2 auditUsually 2 days for a startup with 1-10 people in scopeWe assess whether the controls are implemented and operating effectively.
Certification decisionAbout 1-2 weeks after Stage 2We complete the report and technical review. Any corrective actions must be resolved before we can issue the certificate.

The fastest we have taken a startup from its first scoping call - before it had started its ISMS - to certification was four weeks. That was an exceptional case: the customer worked around the clock, and it should not be treated as a standard or guaranteed timeline.

What can delay or speed up certification?

The biggest factor is how much of your ISMS is already working before the audit begins. When your scope is clear, controls are in use and you have completed your internal audit and management review, we can plan the certification stages with fewer hold-ups. If evidence is missing or findings are still open, your team may need time to put things right and show that the changes work.

Having the right people available also helps keep the audit on schedule. We’ll move promptly through our reviews, but certification depends on seeing enough evidence to make a sound decision.

How to Get ISO 27001 Certified: The Step-by-Step Process

For most SMEs, the full journey takes three to six months. Preparation usually takes longer than the audits themselves. Here are the main steps and how they fit together.

1. Define your scope

Decide which services, systems, people and locations your ISMS will cover. The scope sets the boundaries for your security work and the certification audit.

2. Identify the gaps

Compare your current security practices with ISO 27001 requirements. This shows what needs attention before you build or adapt your ISMS.

3. Build and implement your ISMS

Assess information security risks, choose controls, prepare policies and put those controls into practice.

4. Complete your internal audit and management review

Check that the ISMS works across its full scope, record any findings and review its performance with management. Complete these activities before Stage 1.

5. Complete the Stage 1 audit

We review your ISMS documentation and readiness for the main audit. For a company with 1-10 people in scope, the audit time is typically one day.

6. Complete Stage 2 and certification review

We assess whether your controls are operating effectively. Once the audit report, technical review and any corrective actions are complete, we typically issue the certificate about a week later.

ISO 27001 Stage 1 vs Stage 2: What Actually Happens at Each Audit

Stage 1 checks whether your ISMS is designed and documented well enough to assess. Stage 2 tests whether it works in practice. Both are needed for certification, and each gives us a different view of your information security.

Stage 1: We review your ISMS design and readiness

Tempo Audits looks at your ISMS scope, policies, risk assessment and treatment plan, Statement of Applicability, internal audit and management review records. We also check that these parts fit together and reflect how your startup actually operates.

Startups often need more work on the basics: a scope that leaves out important services or systems, generic policies that don’t match day-to-day practice, or gaps between identified risks and selected controls. Stage 1 is the time to surface these concerns. We record them as areas of concern, with clear next steps before Stage 2; it is not the operational test of your controls.

Stage 2: We test whether your controls work

At Stage 2, we examine evidence that your ISMS is operating as intended. That can include records of access reviews, staff training, risk treatment, security incidents, supplier checks and other controls that apply to your organisation. We interview the people responsible for relevant processes and sample evidence against your scope and Statement of Applicability.

For most technology companies, we run Stage 2 remotely. We review evidence in your GRC platform or shared workspace, use video calls and screen sharing, and arrange focused discussions with your team. We’ll confirm the audit plan and contacts at the opening meeting, then explain our findings and next steps at the close.

What happens if we raise a nonconformity?

If Tempo Audits identifies a nonconformity, we explain what requirement is not being met and what evidence supports the finding. Your team then provides a corrective action plan and evidence that addresses it. We review the response; where further evidence or clarification is needed, we’ll explain what’s missing.

We can issue the certificate once the required corrective actions are approved and the technical review is complete. When those steps are finished, we typically issue it within about seven days.

How to Choose a UKAS-Accredited ISO 27001 Certification Body for Your Startup

Choosing a certification body affects how your audit is planned, how well the auditor understands your business and whether your certificate meets customer or procurement requirements. Use these five checks before you commit.

1. Verify the accreditation covers ISO/IEC 27001

Check the certification body in the UKAS directory of accredited organisations and confirm that its current accreditation schedule includes ISO/IEC 27001. A logo on a website is not enough. Once a certificate has been issued, you can check the certified organisation in UKAS CertCheck.

Tempo Audits is UKAS-accredited for ISO/IEC 27001.

2. Look for experience with technology businesses

If your startup builds software, provides SaaS or uses AI in its products and services, choose auditors who understand those environments. They should be able to follow how your systems, development work, cloud services and suppliers fit into your ISMS.

We audit technology businesses as a core part of our work, including SaaS, software and AI companies. That familiarity helps us ask relevant questions about your actual security practices.

3. Ask what remote auditing involves

Remote auditing can reduce travel and disruption, but it should still involve a thorough review of your ISMS. Ask how evidence is shared, whether auditors can review it asynchronously, how interviews are scheduled and when an on-site visit might be needed.

Our audits are remote by default for most technology and service businesses. We review evidence in a shared workspace or GRC platform, then arrange focused discussions with the people responsible for relevant controls.

4. Get a realistic timeline, not a promise of instant certification

Ask when Stage 1 and Stage 2 could take place, how much time is allowed between them and how long report and certification reviews usually take. A certification body can move promptly, but the certificate depends on your ISMS being ready and any required corrective actions being completed.

For SMEs, our formal audit phase usually takes around three to four weeks. Once corrective actions are approved and the technical review is complete, certificates are typically issued within about seven days.

5. Clarify the scope, fees and next steps before signing

Ask what the quote includes, how audit time is calculated and what happens if the auditor identifies gaps. You should know what is covered by Stage 1 and Stage 2, what could require follow-up and how surveillance audits fit into the certification cycle.

At Tempo Audits, we calculate audit pricing using factors including the number of people in scope, your ISMS scope, complexity and risk profile.

Common ISO 27001 Challenges for Startups - And How to Clear Them

Startups often have sound technical controls but less-developed processes for documenting and reviewing them. These gaps can slow an audit if they surface late.

1. Scope that keeps expanding

Keep the scope focused on the services you want certified, including the people, systems and suppliers needed to deliver them.

2. A thin Statement of Applicability

Link each control to your risks, explain exclusions and record implementation status. Avoid treating the SoA as a generic checklist.

3. An internal audit that lacks independence

The person who built the ISMS should not audit their own work. Choose a competent auditor who can review it objectively.

4. Policies without evidence

Policies show what should happen; records show what happens in practice. Keep evidence such as access reviews, training records and incident logs organised for Stage 2.

ISO 27001 for Startups: FAQs

Do startups need to implement all 93 Annex A controls?

No. You select controls based on your information security risks. Your Statement of Applicability must list the controls and explain which apply, which do not, and why. A control should not be excluded simply because it feels difficult or is missing from your current setup.

Does a startup need a dedicated security manager to get certified?

No. A small team can assign ISMS responsibilities to people who already have other roles. What matters is that responsibilities are clear, leadership is involved and the team has enough time and expertise to keep the system working. ISO 27001 is designed for organisations of different sizes.

Can we certify one product rather than the whole company?

ISO 27001 certifies an information security management system, not a product. You can define a scope around a particular service or part of the business, provided it accurately covers the people, systems and processes that support it.

How do GRC platforms help during an ISO 27001 audit?

Around 70–80% of our clients use a GRC platform. It gives Tempo Audits an organised place to review policies, records and control evidence, so audit time can focus on questions and how controls work. However, it's important to note that the platform does not do the work for you: results still depend on how well your ISMS is implemented and internally audited.

Does ISO 27001 certification guarantee that we will not have a data breach?

No certification can promise that. ISO 27001 gives your startup a structured way to identify and manage information security risks, but risks can change and incidents can still happen. Certification provides assurance that your ISMS has been independently assessed against the standard; it is not a guarantee of zero incidents.

Rob Hall

About the author

Rob Hall

CEO, Tempo Audits

Rob Hall is the Founder and CEO of Tempo Audits. A former corporate lawyer and tech entrepreneur, he leads a team providing ISO 27001 and ISO 42001 certification audits and SOC 2 assurance for technology companies.

Book a call

No forms, no faff – just a conversation and a quote. Prefer to skip straight to it? Fill out the application form and we'll get moving.

Alternatively, if you have all the details,
fill out this form here.

ISO 27001