Skip to content
All posts

GRC

ISO 27001:2022 for Small Companies: What Certification Takes

What ISO 27001:2022 really requires, why scope sets the size of the project, what auditors look for, and the mistakes that cost small teams the most.

FMMuhammad Fawad MushtaqHead of Compliance

· 9 min read

On this page

A small company usually starts thinking about ISO 27001 for one reason: a customer's security questionnaire asks for the certificate. The next question is how long it takes, what it costs and how much of the business it will disrupt. The honest answers depend less on the standard than on the choices you make in the first month.

This post is for founders, operations leads and whoever has been told "get us ISO 27001". It explains what the 2022 edition actually requires, the decisions that set the size of the project, what the auditors look at, and the mistakes I see most often when small teams try to get certified.

What ISO 27001:2022 actually asks for

ISO/IEC 27001 defines an information security management system, or ISMS. The current edition was published in October 2022, and a 2024 amendment added that you must consider whether climate change is a relevant issue for your organisation and your interested parties. For most small companies that is a short, reasoned note in the context section, not a project.

The standard has two parts that matter to you.

Clauses 4 to 10 are mandatory. They describe how the system runs: understanding your context and scope (4), leadership and roles (5), risk assessment and treatment (6), resources, competence and documentation (7), operating the plan (8), monitoring, internal audit and management review (9), and fixing problems (10). You cannot exclude any of them.

Annex A is a reference list of 93 controls, grouped in four themes: organisational (37), people (8), physical (14) and technological (34). You are not required to implement all 93. You must compare the controls your risk treatment needs against Annex A, and record in a Statement of Applicability which controls you include, why, whether they are implemented, and why any are excluded. Auditors read that document closely.

The 2013 edition is gone for certification purposes. Under the IAF transition rules (IAF MD 26), certificates against ISO 27001:2013 had to move to the 2022 edition by 31 October 2025. If a supplier still shows you a 2013 certificate, it has expired or been withdrawn.

The decision that sets the size of the project: scope

Scope is where small companies win or lose most of the effort. It is defined in clause 4.3, and it states which parts of the organisation, locations, services and technology the ISMS covers.

Two common mistakes pull in opposite directions.

Scope too wide. A 30-person company scopes "the whole organisation" because it sounds more impressive. Now the office Wi-Fi, the finance laptop, the sales team's personal phones and a legacy file server are all in, and every one needs controls and evidence.

Scope too narrow. A company scopes only "the development team" to make the audit easy. Then a customer reads the certificate, sees that the hosted platform and the support team who can reach customer data are outside it, and the certificate does not answer their question.

The right scope follows the reason you need the certificate. If customers want assurance about the SaaS platform that holds their data, scope that platform and everyone and everything that can affect it: engineering, operations, support with production access, the cloud accounts, the identity provider, and the suppliers you rely on. Write it so a customer can understand it in one sentence, because that sentence is printed on the certificate.

What a realistic path looks like

Every company is different, and I will not give you a number of weeks that pretends otherwise. What I can give you is the order of work, and what each stage needs to produce.

StageWhat you produceWho is involved
1. Decide and scopeReason for certification, scope statement, named owner, leadership commitmentLeadership, ISMS owner
2. Context and risk methodInterested parties and their requirements, risk assessment method, risk criteriaISMS owner, leadership
3. Risk assessment and treatmentRisk register, treatment plan, Statement of ApplicabilityISMS owner, system owners
4. Implement and operateControls in place, policies people can follow, training, records being createdEveryone in scope
5. CheckInternal audit, management review, corrective actionsIndependent internal auditor, leadership
6. Certification auditStage 1 (documentation and readiness), then Stage 2 (implementation and effectiveness)Certification body

The stage most often underestimated is 4. Controls must not only exist; they must have run long enough to leave records. An access review policy written last week has no access reviews behind it. Auditors look for evidence over a period, so plan for the system to operate for some time before Stage 2.

The stage most often rushed is 5. Clause 9.2 requires an internal audit by someone who is objective and impartial towards what they audit. In a small company, the person who built the ISMS cannot audit their own work. Use a colleague from another area who has been trained, or an external auditor. Clause 9.3 requires a management review with defined inputs, and the minutes are evidence.

How the certification audit works

Certification bodies follow ISO/IEC 17021-1 and the ISMS-specific rules in ISO/IEC 27006-1. In practice:

  • Stage 1 reviews your documentation and readiness: scope, risk assessment, Statement of Applicability, and whether internal audit and management review have happened. Gaps here are cheap to fix.
  • Stage 2 tests whether the system works. Auditors interview people, sample records and check that controls in the Statement of Applicability are operating.
  • Audit time is calculated from tables in ISO/IEC 27006-1, mainly from the number of people working under the scope, adjusted for complexity. This is another reason scope matters: it directly sets the auditor days you pay for.
  • The cycle is three years: surveillance audits in years one and two, then recertification. The ISMS has to keep running between audits, or surveillance will find it.

What auditors actually look for

From the auditee's side, the questions that matter are rarely "do you have a policy for X?". They are closer to these:

  • Show me a risk you decided to accept, and who accepted it. Risk owners must approve treatment plans and accept the remaining risk (clause 6.1.3). A register where every risk is "mitigated" and nobody signed anything is a weak sign.
  • Show me how you know this control works. For access control, that means the last access review and what changed because of it. For backups, a restore test with a date. For vulnerability management, the scan results and the record of fixes closed on time. Our post on prioritising vulnerabilities with EPSS and KEV describes the kind of written rule that gives an auditor clear evidence for Annex A 8.8.
  • Show me something that went wrong and what you did. Incidents, near misses and audit findings with corrective actions (clause 10.2) show that the system learns. A company that reports nothing ever going wrong is less convincing, not more.
  • Show me that people know their part. Auditors ask staff, not only the ISMS owner. Can a support engineer explain how they report a suspicious email or what they may do with customer data?
  • Show me your suppliers. For a small cloud-based company, most of the infrastructure belongs to suppliers. Annex A 5.19 to 5.23 expect you to know who they are, what you rely on them for and how you check them.

The mistakes that cost small companies the most

Buying a policy pack and stopping there. Template policies are a reasonable starting point. But a policy that says "access is reviewed quarterly" turns into a finding the first time an auditor asks for last quarter's review. Write policies that describe what you actually do, and then do it.

Treating Annex A as a checklist. Starting with the 93 controls and ticking them off produces a long Statement of Applicability with no link to your risks. Start with the risk assessment, decide treatments, then use Annex A to check you have not missed anything. That is the order clause 6.1.3 describes.

One person owns everything. A single ISMS owner who writes, operates and audits the system is a single point of failure, and it fails the impartiality requirement for internal audit. Give each control an owner in the team that runs it.

Choosing the cheapest certificate. Some certificates are issued by bodies that are not accredited, or after an audit that is hard to tell apart from a sales call. Customers who know the market check. Use a certification body accredited for ISO 27001 by a national accreditation body that is a member of the International Accreditation Forum, and confirm it on IAF CertSearch.

Confusing certification with security. ISO 27001 shows that you manage risk in a structured way. It does not prove that your application is free of vulnerabilities. Many customers will still ask for a recent penetration test, and annual technical testing is good evidence for several Annex A controls. Our post on what a good penetration test delivers explains what to expect from one.

Questions to answer before you start

Use these in your first leadership meeting about certification. If you cannot answer one, that is the first piece of work.

  • Which customers or contracts need the certificate, and what exactly do they expect it to cover?
  • What is our scope in one sentence, and does it include everyone who can reach the data customers care about?
  • Who owns the ISMS, and how much of their time is set aside for it?
  • Who will carry out the internal audit, and are they independent of the work they audit?
  • Which of our current practices (access reviews, backups, onboarding and leaving, incident handling) already leave records, and which do not?
  • Which suppliers hold or process in-scope data, and what do we know about their security?
  • Which accredited certification bodies operate here, and what audit time do they quote for our scope?

How we approach it

When we support a company through certification, we start with scope and the risk assessment, not documents. We find most of the effort is saved by deciding early what is in, what is out and why, and by building the evidence habits (reviews, records, actions) into work the team already does. We then run the internal audit independently of whoever built the system, so the first hard questions come from us rather than the certification body. You can read more about how we work on governance, risk and compliance.

The certificate matters to customers. The system behind it matters more to you, because it is what decides whether the next incident is handled calmly or in a panic. Built around how your team actually works, it does both.

  • ISO 27001
  • Certification
  • ISMS
  • Compliance
FM

Written by

Muhammad Fawad Mushtaq

Head of Compliance, FutaqSec

Keep reading

Not sure where to start?

A 30-minute scoping call is enough to understand your environment and recommend the right first step. No obligation.

Book a free consultation