CRYPTOITDATA

ISO 27001 implementation and certification

ISO 27001 implementation for SMBs: from gap analysis to certification

ISO/IEC 27001:2022 implementation for SMBs, from the gap analysis to the certification audit.

Large clients and tenders increasingly ask for an ISO 27001 certificate or a security questionnaire backed by evidence. Without a documented management system, every questionnaire costs days and gives answers you cannot defend in front of an auditor.

Updated

What's holding you back

If at least three of these sound familiar, it's time to talk.

  • You lost a tender or a client because you have no ISO 27001 certificate.

  • Clients send you security questionnaires and you fill them in from scratch every time.

  • Your security policies were copied from the internet and nobody applies them.

  • You have no risk register and no Statement of Applicability (SoA).

  • You do not know how long it takes or what it costs beyond the certification body fee.

How we work

We start from the scope: which processes, sites and systems the certificate covers. A well-chosen scope shortens the project by months and stays credible for the clients who ask for the certificate.

We run the gap analysis against clauses 4–10 of the standard and the 93 Annex A controls. It produces the risk register, the Statement of Applicability and the treatment plan, with an owner and a deadline for every measure.

We implement the controls, write policies your people can follow and collect the evidence that they work. Before the certification audit we run a simulated internal audit and the management review the standard requires. The certificate is issued by an accredited certification body, not by us.

What implementing ISO 27001 means for a small company

ISO/IEC 27001:2022 describes an information security management system. Annex A lists 93 controls in 4 themes: 37 organisational, 8 people, 14 physical and 34 technological. You don't implement all of them by reflex. You start from your risks, pick the controls that treat them and justify each decision in the Statement of Applicability (SoA).

We work on four pieces: the scope, the risk register (impact, likelihood, treatment cost), policies your people can actually follow, and the evidence that you apply them: logs, training records, access reviews, management review. Without evidence, the auditor only sees paperwork.

The version in force is ISO/IEC 27001:2022. The transition period from the 2013 version ended on 31 October 2025, so a new project starts directly on the 2022 version.

How certification works

The certificate is issued by an accredited certification body, such as SRAC or TÜV, not by the company that helps you implement. In Romania, the national accreditation body is RENAR. The certification audit has two stages: the first checks the documentation and whether you are ready, the second checks that the system works in practice.

The certificate is valid for 3 years. During that time there are annual surveillance audits, and at the end a recertification audit. The system has to keep working, not just in audit week: the risk review, the internal audit and the management review repeat every year.

Typical timeline and prices

Typical figures, not guarantees: around 3 months for a narrow scope and an already tidy infrastructure, around 6 months for an SMB starting from scratch, up to 12 months when you have several sites, in-house applications or critical suppliers.

The ISO 27001 Kickstarter package lays the foundation: risk register, SoA, at least 8 policies, the 14 priority Annex A controls and a simulated internal audit. It costs €7,400 for up to 50 devices (3-4 weeks), €11,400 with audit support (6-8 weeks), €14,000 for 50-100 devices and €26,000 above 100. All prices exclude VAT. The certification body's fee is paid separately, directly to that body.

Projects are led by Dragoș Nimu: ISO 27001 internal auditor (TÜV Austria, 2019), information security manager, 25+ years in IT, as IT Manager and IT Director at TRW Automotive, Takata, Profi and AEM. For our other security services (audit, testing, training, vCISO), see the Cybersecurity page.

What we deliver

ISO 27001 gap analysis

Where you stand against clauses 4–10 and Annex A, with findings ordered by risk and effort.

Risk register and SoA

Risks rated by impact and likelihood, the controls chosen and the justification for every exclusion.

Policies and procedures

At least 8 policies written for your company, not templates, plus the procedures the auditor will ask for.

Implementing the controls

Access control, MFA, tested backup, logging, supplier and incident management.

Simulated internal audit

We check the system the way an auditor would, before the real audit, and close the nonconformities found.

Certification audit support

We support you through stages 1 and 2 of the audit and help with the corrective action plan.

How we engage

  1. 1

    Scope and gap analysis

    We define what you certify and how far you are from the requirements.

  2. 2

    Risks and SoA

    Risk register, Statement of Applicability and a treatment plan approved by management.

  3. 3

    Implementation

    Technical and organisational controls, policies, training and evidence that they work.

  4. 4

    Internal audit and management review

    Checking the system before certification, as clauses 9.2 and 9.3 require.

  5. 5

    Certification and surveillance

    The two-stage audit with the certification body, then annual surveillance audits.

What you gain

Access to tenders and large clients

The certificate answers the security requirements in tender specifications and contracts in one go.

Questionnaires answered once

The evidence in the system answers client questionnaires without redoing them each time.

Risks treated in the right order

You invest first where impact and likelihood are highest.

A foundation for NIS2

A working ISO 27001 system covers much of what GEO 155/2024 requires.

Relevant certifications:ISO 27001 internal auditor (TÜV Austria)Information security managerDNSC auditor specialisation

Frequently asked questions

How long does ISO 27001 implementation take for an SMB?

Typically 3 to 12 months up to the certification audit, and that range is not a guarantee. A small company with a narrow scope and already documented infrastructure can get there in about 3 months. An SMB starting from scratch usually needs around 6 months. Several sites, in-house applications or many critical suppliers push it towards 12 months. What matters most is how quickly your team responds and how long the system needs to produce real evidence that it works.

Who issues the ISO 27001 certificate?

An accredited certification body, such as SRAC or TÜV, not the company that helps you implement. The certification audit has two stages: the first checks documentation and readiness, the second checks that the system works in practice. The certificate is valid for 3 years, with annual surveillance audits. CRYPTOITDATA prepares you, implements the controls, runs the simulated internal audit and supports you during the audit if you choose the option with support. You pay the certification body's fee directly to that body.

How much does ISO 27001 implementation cost?

The ISO 27001 Kickstarter package costs between €7,400 and €26,000 excluding VAT, depending on the number of devices and audit support. For up to 50 devices, the Standard option is €7,400 and the Premium option, with certification audit support, is €11,400. For 50-100 devices the price is €14,000, and above 100 it is €26,000. On top of that come the certification body's fee and your internal team's time. If you don't yet know where you stand, the cybersecurity audit starts at €1,800 excluding VAT.

Do I have to implement all 93 Annex A controls?

No. You assess all of them, but implement only the controls justified by risks, legal obligations or contractual requirements. The Statement of Applicability shows, for each control, whether it applies, why, and its status. Every exclusion must be argued: a company with no in-house software development can exclude the secure development controls, but it cannot exclude access control or backup. The auditor compares the SoA with the risk register and checks that your decisions hold together.

Does an ISO 27001 certificate replace the NIS2 audit?

No. The NIS2 audit required by GEO 155/2024 is carried out by a DNSC-certified auditor, and an ISO 27001 certificate does not cover DNSC registration, the risk level assessment or the incident reporting deadlines. ENISA publishes a mapping between NIS2 requirements and ISO/IEC 27001:2022, but states that it is not an equivalence. A working ISO 27001 system is still a good foundation: much of the evidence the NIS2 audit asks for already exists. Details on the NIS2 and DNSC audit page.

My certificate is on the 2013 version. Is it still valid?

No. The transition period from ISO/IEC 27001:2013 to the 2022 version ended on 31 October 2025, and certificates issued on the old version that were not transitioned have lost their validity. If your system is still on 2013, you run a gap analysis against the new Annex A (93 controls instead of 114, 11 of them new, such as threat intelligence, information security for cloud services and data masking) and then a certification audit on the 2022 version.

Let's talk about your situation

30 minutes — we explore what you have, what's missing and what concrete next steps look like.