1. What certification involves
ISO/IEC 27001 is an international standard describing how to build and operate an information security management system, usually referred to by the acronym ISMS (Information Security Management System). It is not a list of products to install. It is a way of organising responsibilities, risks and rules around information, and of demonstrating that this way of working holds up over time. Obtaining certification means that an accredited independent body has verified the system and judged it compliant.
Complying with the standard and obtaining certification are not the same thing. You can work in line with the standard without ever seeking the certificate, and for a small organisation that can be a reasonable choice. Certification becomes useful when a customer asks for it in a tender, when a larger group assesses its suppliers or when you want independent verification. Decide first why you need it, because this drives timelines, scope and budget.
2. Before you start: objective, owner and resources
Put the objective in writing. A pathway started to answer a customer has different timelines and priorities from one started to reduce internal risk. Also define, as a first approximation, what should be included in the certification: the scope, which you will see in the next step, determines almost all of the work. A vague objective produces a project that never ends. Write it in a sentence that management can approve and that everyone can repeat.
You need an internal owner with a clear mandate and real time to devote to the work. The role often falls to whoever manages IT or security, but management must approve the rules and take part in decisions about risks. The consultant or IT provider can support the work and prepare drafts, but decisions remain with the organisation. If nobody has time to read and sign the documents, the project stalls at the first draft.
Estimate resources honestly: internal hours for meetings and reviews, any tools for inventory and evidence, and the cost of the certification body, which varies with scope and size. Request quotes from several accredited bodies and compare what the audit stages include, not just the final price. Also consider the time of those who will have to collect evidence every month, because it is the cost most often underestimated.
3. Phase 1: defining the scope and context
The scope indicates which sites, processes, systems, data and people are inside the management system. It is the first element the body evaluates, and changing it midway is very costly. Start from a simple question: which information matters to the business and where does it live? List the processes that handle it, such as sales, administration, customer support or production, and the systems that support them.
Then describe the context: the type of business, the most important customers and suppliers, legal and contractual obligations such as the GDPR for personal data. This helps you understand which interested parties matter and which expectations you must meet. A long document is not needed, but a clear page, approved by management, explaining why the system exists. A common mistake is to exclude the most critical system for convenience, such as the management software or backups: a scope that leaves out what the business depends on will be challenged at audit.
4. Phase 2: risks and the statement of applicability
With the scope defined, you assess risks. For each important piece of information, you identify the plausible threats, the vulnerabilities that could exploit them and the impact if it happened. The standard does not impose a single method: what matters is that it is repeatable, documented and capable of producing a risk list ordered by priority. For a medium-sized organisation a table with likelihood, impact and risk owner is often sufficient. A dedicated guide covers the method in detail.
For each risk, decide how to treat it: reduce it with a control, accept it formally, avoid it by changing activity, or transfer it, for example through a contract or insurance cover. From this analysis comes the statement of applicability, the document that lists the controls in Annex A, states which ones you apply and which you do not, and justifies the exclusions. It is one of the documents the body reads most closely, and every exclusion must have a concrete reason.
5. Phase 3: implementing controls and collecting evidence
The controls you have chosen must be implemented in practice: written policies, access management, staff training, supplier control, backup and restore, incident management, physical security of premises. Expensive tools are not needed for every control. Many controls are clear processes, defined roles and records kept regularly. Even a simple control becomes credible when someone performs it consistently and leaves a trace of what they did.
The part that is often missing is the evidence. The body does not judge intentions but evidence: minutes, a log of revoked access, a restore test report, a training certificate, a signed supplier checklist. Define from the outset where each piece of evidence lives, who produces it and how often. Work in groups of controls, starting with the highest risks and those that already have a practice in place, and check in contracts that suppliers can provide the evidence you require.
6. Phase 4: internal audit and management review
Before the external assessment you must check the system yourself. The internal audit is a review carried out by people who do not directly manage the process being examined, and it serves to find nonconformities before the body does. The audit programme defines what to check, when and by whom. Every deviation must be recorded, analysed for its cause and closed with a corrective action whose effectiveness you verify.
The management review is the meeting in which top management looks at the results: status of risks, incidents, audit outcomes, security objectives, changes in context. It is a real meeting, with minutes, decisions and owners. A review held only for form's sake is one of the most common causes of findings. If this is the first time, do not expect a perfect system: the point is to demonstrate that the system checks and improves itself.
7. Phase 5: the certification body's audit
The certification audit takes place in two stages. In the first, the body verifies the documentation: scope, policy, risk analysis, statement of applicability and the other documents required. This helps establish whether the system is ready to be assessed on site. Any gaps must be closed before the second stage, and this is the right moment to ask for clarifications. Prepare for this discussion as you would for an internal check, with the owner present and the evidence already in order.
In the second stage, the body verifies that the system really works: it interviews people, samples the evidence, observes the application of controls, and reviews the handling of incidents and corrective actions. Findings can have different severity, with different closure methods and timelines. Ask the body how it classifies them before the audit. If everything is in order, the certificate is issued and remains valid thanks to periodic surveillance audits.
8. Common mistakes and topics to explore
The mistakes that lengthen timelines most are almost always the same. It often happens with documents copied from generic templates and never adopted by management, or with a scope that does not match the real organisation. Other typical mistakes are controls declared but with no evidence collected over time, and reviews held without minutes. They almost always surface a few weeks before the audit, when fixing them costs more time and energy than expected.
To explore further, the following questions have dedicated guides: how to define the scope of the system, how to conduct the risk analysis, how to read the Annex A controls, how the internal audit is conducted, what the phases of the certification audit are, how the standard intersects with NIS2, which documents are mandatory, which certification to choose, and what the privacy and artificial intelligence extensions add.
- Generic documents, written in haste and never read by management
- A scope that excludes systems or suppliers supporting the business
- Controls declared as applied but without evidence collected over time
- An internal audit carried out by the person who manages the audited process
- A management review without minutes or decisions
9. How to start
The first useful step this week is a short meeting with management to decide three things: the purpose of the certification, the project owner and a first draft of the scope. Write the decisions on a single page and have it signed. Everything else is built from these choices. If the meeting does not produce a written decision by the end of the week, the project has not really started yet.
Immediately afterwards, read the guide on scope and prepare the list of processes and systems that handle important information. With a clear scope, the risk analysis becomes simpler and the statement of applicability takes shape without forcing. Ask several accredited bodies for an offer describing the stages included, and use the answers to choose the partner you will work with.
Frequently Asked Questions
How long does it take to obtain ISO 27001 certification?
The duration depends on the size of the organisation, the complexity of the scope and how much documentation already exists. A company with orderly processes and a dedicated owner takes far less time than one starting from scratch. Do not trust promised timelines without a preliminary analysis. Ask your consultant and the body for a plan with the phases, deadlines and the activities requiring internal staff.
Do I need an external consultant to get certified?
It is not mandatory. You can build the system with internal resources, provided the owner has the skills and the time. A consultant brings experience, helps avoid typical mistakes and speeds up preparation. The risk is delegating everything: the standard assumes that the system belongs to the organisation and that management knows its choices. Also check that whoever supports you has no conflict of interest with the body that will certify you.
How much does ISO 27001 certification cost?
The cost varies with the scope, the number of sites and people, the processes involved, and the preparation work. There are costs for the certification audit, for surveillance audits and for renewal, plus internal hours and any external support. Request comparable quotes that describe exactly what each phase includes, and be wary of offers that do not specify it.
Can a small company get certified?
Yes. The standard applies to organisations of any size, but the system must be proportionate. In a small organisation processes are simpler and responsibilities often coincide, which makes the work lighter. The critical point is to define a sensible scope and avoid copying a system designed for large groups. A narrow scope that is well managed is more robust than a broad one that exists only on paper.
Does ISO 27001 certification suffice for NIS2 or GDPR compliance?
No. Certification covers an important part of security management, but it does not replace the checks required by the individual regulations. The GDPR has its own rules on processing personal data, such as the record of processing and breach management. NIS2 requires incident notifications within precise timelines, which must be organised separately. Check with an adviser which obligations apply to you.
How long does the certificate last and what happens afterwards?
The certificate has a limited validity period and remains active thanks to the body's periodic surveillance audits. At expiry, a complete and more in-depth renewal is required. The system must keep working: management reviews, internal audits, incident handling and risk updates do not stop with the certificate. A system neglected after certification becomes visible at the next audit.
Can I get certified for only part of the company?
Yes, the scope can be limited to a division, a site or a service, provided its boundaries are clearly defined. The problem arises when the certified part depends on excluded systems or people, or when customers expect more than the certificate covers. State in the scope what is included, what is excluded and why, and communicate it clearly to customers.