The client's supplier questionnaire has one short line: ‘ISO/IEC 27001:2022 certificate, yes or no’. You have three weeks to answer, so the first search is ‘ISO 27001 small business’ and, right after, what the certificate costs. The question is upside down. The certificate is the last step, and part of what the auditor checks are records that only exist once the system has been running for a while.
The good part: the standard is written for any company. ISO/IEC 27001 says its requirements are generic and intended to apply to all organizations, regardless of type, size or nature. The part few people read is the sentence right after: if you claim conformity, you cannot exclude any requirement in clauses 4 to 10. You choose which controls to apply. The management system you build in full.
What ISO 27001 requires from a small business
The current edition is ISO/IEC 27001:2022, the third, from October 2022, with a 2024 amendment on climate change. It has 19 pages and contains two different things: clauses 4 to 10, which describe the management system and are mandatory, and Annex A, a reference list of controls against which you compare your own measures.
| Clause | What it asks, in short | What stays documented |
|---|---|---|
| 4. Context of the organization | Internal and external issues, interested parties and their requirements, the boundaries of the system. | The scope. |
| 5. Leadership | Top management owns the system, approves the policy, assigns roles and responsibilities. | The information security policy. |
| 6. Planning | A risk assessment process with written criteria, risk treatment, comparison with Annex A, measurable objectives. | The risk assessment and treatment processes, the Statement of Applicability, the treatment plan, the objectives. |
| 7. Support | Resources, competence, awareness, communication, control of documents. | Evidence of competence. |
| 8. Operation | You run what you planned and reassess risks at planned intervals or when things change. | Results of risk assessments and risk treatment. |
| 9. Performance evaluation | Monitoring and measurement, internal audit, management review. | Monitoring results, the internal audit programme and results, management review results. |
| 10. Improvement | Nonconformities, corrective action, continual improvement. | The nonconformities and what was done about them. |
Annex A has 93 controls grouped into four themes, the same as in ISO/IEC 27002:2022, the standard that explains them at length. Clause 6.1.3 asks you to determine the controls you need yourself, then check against the list that nothing necessary has been omitted. For each control the decision goes into the Statement of Applicability (SoA): why it is included, whether it is implemented, and why it is excluded where that applies.
| Theme | Controls | Examples |
|---|---|---|
| Organizational | 37 (5.1-5.37) | 5.9 inventory of assets, 5.15 access control, 5.19 suppliers, 5.23 cloud services, 5.24 incident preparation |
| People | 8 (6.1-6.8) | 6.1 screening, 6.3 awareness and training, 6.8 event reporting |
| Physical | 14 (7.1-7.14) | 7.7 clear desk and clear screen, 7.10 storage media, 7.14 secure disposal of equipment |
| Technological | 34 (8.1-8.34) | 8.5 secure authentication, 8.8 technical vulnerabilities, 8.13 backup, 8.24 cryptography |
Why small businesses get stuck on ISO 27001
Rarely for lack of technology. A company of 20-30 people usually has antivirus, backup and a decent firewall. It gets stuck for other reasons, and they repeat:
- It starts from controls, not clauses. It buys tools for Annex A and finds at the end that the risk criteria, the objectives and the management review are missing, the mandatory part.
- It copies a template. An SoA with 93 ticked rows and no link to the risk register shows that a table was filled in, not that a decision was made. How this looks at the certification audit is covered in our article on Stage 2 nonconformities.
- It leaves the records for the last week. Monitoring results, the internal audit and the management review in clause 9 cannot be produced retroactively. They only appear if the system actually runs.
- It puts everything on one person. The IT administrator is also the security lead and the one answering questionnaires. When they go on holiday, the system stops.
All four share one root: ISO 27001 is treated as a project with an end date. The project ends when the certificate is issued. The obligations do not.
ISO 27001 certification is a three-year cycle, not an exam
Certification itself is optional. ISO notes that a certificate from an accredited body adds confidence, because accreditation independently confirms the body’s competence. The requirements for those bodies are in ISO/IEC 27006-1:2024, which complements ISO/IEC 17021-1.
In practice, one body’s rules, those of TÜV AUSTRIA Hellas, look like this: the certification audit has two stages, the certificate is valid for three years, the surveillance audit is annual, and before expiry a recertification follows for another cycle. If deadlines are exceeded, the certificate is suspended for six months and then withdrawn. Other bodies may have their own deadlines, so ask for yours in writing.
| Moment | What the auditor checks | Benchmark from the body’s regulation |
|---|---|---|
| Stage 1 | The documentation the standard requires, including the risk assessment methodology and its results. | May be conducted off your premises. |
| Stage 2 | Whether the system exists, operates and is effective, on site. | No more than 6 months after Stage 1; otherwise Stage 1 is repeated. |
| Certification decision | The certificate is issued for three years; the valid SoA appears on the certificate. | Nonconformities from certification are closed within 2 months of Stage 2. |
| Surveillance 1 and 2 | One audit each year, to keep the certificate valid. | By the anniversary of the certification decision. |
| Recertification | Renewal of validity for a new three-year cycle. | Before the certificate expires. |
For a small business, the question is not whether it passes Stage 2. It is whether the system still works at the first surveillance audit, with the same people and no consultant in the office.
Three choices follow from this, and they matter more than any tool: a narrow, clear scope, a risk assessment method anyone on the team can repeat, and a named owner for each group of controls, with a shared calendar of what has to be done monthly, quarterly and yearly.
Worked example: a 25-person software company
Take a hypothetical company in Timișoara: 25 people, an application hosted in the cloud, a German client asking for the certificate to renew the contract. The steps, in the order we take them:
- 1The scope: development, hosting and support of the application, the office and the cloud services used. Outsourced accounting stays outside it, but the interface with it is part of the analysis, because clause 4.3 requires you to consider interfaces with other organizations.
- 2The risk criteria, before the risks: an impact scale, a likelihood scale and the acceptance threshold. Clause 6.1.2 requires repeated assessments to produce comparable results, so the criteria are not renegotiated for each risk.
- 3The inventory and the risk register: the assets in scope, each with an owner, then the risks to confidentiality, integrity and availability, each with a risk owner.
- 4The Statement of Applicability, row by row for all 93 controls. The company includes 5.23, because the application runs in the cloud, and the physical controls that concern the office. It excludes 8.30, outsourced development, if it does not outsource development, and writes down why.
- 5The treatment plan, approved by the risk owners, who also accept the residual risks, as 6.1.3 requires.
- 6Operation: access reviews, backup restore tests, training with an attendance list, an incident log. Each leaves a dated record.
- 7The internal audit and the management review, before Stage 1. Findings are closed before the certification body arrives.
- 8Stage 1, the corrections requested, then Stage 2.
How long it takes we cannot say without seeing the company, and there is no standard duration. What lengthens the path is well known: a broad scope, several locations, missing documentation and, most often, an internal owner who also has another job. What shortens it: records that already exist, even if they are not called ISO.
The minimum documents
The standard does not require a manual. It requires documented information, meaning documents you maintain and records you retain. The minimum list that follows from clauses 4 to 10:
- The scope of the system (4.3) and the information security policy (5.2).
- The risk assessment process (6.1.2) and the risk treatment process (6.1.3).
- The Statement of Applicability and the risk treatment plan (6.1.3).
- The information security objectives (6.2) and evidence of competence (7.2).
- Results of risk assessment and risk treatment (8.2, 8.3).
- Monitoring and measurement results (9.1), the internal audit programme and results (9.2), management review results (9.3).
- Nonconformities and corrective actions (10.2).
On top of these come whatever the included controls require, for example the operating procedures of 5.37. A document nobody in the company reads is one the auditor will find out of date.
What ISO 27001 costs: the structure, not a figure
We do not give an amount for certification, because there is none that holds for every company. We can give the structure, so you compare offers line by line:
| Component | Who you pay | What drives it |
|---|---|---|
| The text of the standard | ISO or the national standards body | On the ISO website, ISO/IEC 27001:2022 costs CHF 155; the ISO guide for SMEs, CHF 44. |
| Preparation and implementation | The consultant, if you work with one | The scope, what already exists, how many controls must be built from scratch. |
| Team time | Nobody, but it is a real cost | How many people are involved and for how long each month, including after certification. |
| New technical measures | Solution vendors | The gaps the risk analysis reveals: MFA, tested backup, logging. |
| Certification audit (Stage 1 and 2) | The accredited certification body | Audit days, set by the body under the rules for ISMS. |
| Annual surveillance and recertification | The same body | Two more audits in the three-year cycle, then recertification. |
| Major nonconformities | The body, if a re-audit is needed | How prepared you are at Stage 2. |
ISO 27001 and NIS2: large overlap, not a substitute
The NIS2 Directive requires technical, operational and organisational measures proportionate to the risk and says they take into account, where applicable, relevant European and international standards (Art. 21). Article 25 explicitly encourages their use. The minimum list of measures in Art. 21(2) is largely found in ISO 27001:
| NIS2, Art. 21(2) | Where you find it in ISO/IEC 27001:2022 |
|---|---|
| (a) policies on risk analysis and system security | Clauses 5.2, 6.1.2, 6.1.3 |
| (b) incident handling | Controls 5.24, 5.26 |
| (c) business continuity, backup, disaster recovery, crisis | Controls 5.29, 5.30, 8.13 |
| (d) supply chain security | Controls 5.19, 5.20, 5.21 |
| (e) acquisition, development, maintenance, vulnerabilities | Control 8.8 and the development controls in theme 8 |
| (f) assessing the effectiveness of measures | Clauses 9.1, 9.2 |
| (g) cyber hygiene and training | Clause 7.3, control 6.3 |
| (h) cryptography | Control 8.24 |
| (i) human resources, access control, assets | Controls 6.1, 5.15, 5.9 |
| (j) multi-factor authentication, secured communications | Control 8.5 |
Overlap is not equivalence. In Romania, NIS2 is transposed by Government Emergency Ordinance (GEO) 155/2024, approved with amendments by Law 124/2025. The ordinance, too, asks that measures take relevant standards into account (Art. 11(2)). The security audit is mandatory for both essential and important entities (Art. 11(5)), and only auditors attested by DNSC, the national cybersecurity directorate, may carry it out (Art. 58). An ISO 27001 certificate does not replace that audit. The evidence file built for ISO, on the other hand, you use directly. Mind the independence rule as well: the NIS2 auditor may not audit an entity to which it has provided services in the past year (Art. 58(3)). Details under NIS2 and DNSC audit.
What we do and what we do not do
We prepare, implement and carry out internal audits. We do not certify: the certificate is issued by an accredited certification body of your choice. CRYPTOITDATA itself is not ISO 27001 certified either. Dragoș Nimu, the founder, has more than 25 years of IT in large companies in automotive, retail, manufacturing and utilities, is an ISO 27001 internal auditor (TÜV Austria course) and holds the DNSC specialisation for cybersecurity auditors, with DNSC attestation in progress.
The ISO 27001:2022 Implementation Kickstarter package, described on our ISO 27001 implementation page, includes 14 priority Annex A controls, the risk register (impact × likelihood × mitigation cost), the Statement of Applicability, 8+ policies (security, access, incident response, continuity) and a simulated internal audit. Catalogue prices, excluding VAT:
- Standard Micro/Small, up to 50 devices: €7,400, 3-4 weeks.
- Premium Micro/Small, up to 50 devices, with audit support: €11,400, 6-8 weeks.
- Standard Medium, 50-100 devices: €14,000, 6 weeks.
- Large, over 100 devices: €26,000, 8-12 weeks.
The durations are for our deliverables, not for certification. If you first want to know where you stand, the cybersecurity audit includes a light ISO 27001 gap analysis, from €1,800 excluding VAT for up to 10 devices.
Conclusion
For a small business, ISO 27001 is not decided by the price of the certificate but by whether you can keep the system running for three years: a narrow scope, written risk criteria, an SoA tied to risks and records that accumulate from everyday work. If you would like to look together at which scope makes sense for you and what you already have, book a 30-minute call.
Sources
- ISO/IEC 27001:2022, official ISO page, edition 3, October 2022, with Amd 1:2024: price, certification, accreditation.
- ISO/IEC 27001:2022, official preview extract (redline), iTeh Standards: clauses 1 and 4-7.4.
- ISO/IEC 27002:2022, official preview extract (redline), iTeh Standards: table of contents of controls 5.1-8.34.
- ISO/IEC 27006-1:2024, official ISO page.
- TÜV AUSTRIA Hellas, Certification Regulation for Information Security MS, rev. 01, 1 June 2023.
- Directive (EU) 2022/2555 (NIS2), European Parliament and Council, 14 December 2022: Art. 21 and Art. 25.
- GEO 155/2024 on the framework for the cybersecurity of networks and information systems, Romanian Legislative Portal: Art. 11 and Art. 58.