An auditor who comes for ISO 27001 assesses your ISMS, the system with which you secure your information. But what actually is such an ISMS, and how do you set one up without it turning into a pile of paper? After reading this article you will know what an ISMS is, in which order you build it, how you measure, how the internal audit and the management review work, how long it has to run before the audit and whether you need software, a spreadsheet or a consultant for it.
What is an ISMS under ISO 27001?
An ISMS is the fixed way in which your company secures its own information. It safeguards three things: that only the right people see information (confidentiality), that the information is correct (integrity) and that you can access it when you need it (availability). ISMS stands for information security management system, in Dutch a managementsysteem voor informatiebeveiliging. The core is risk management. You work out what can go wrong and you choose controls against it. ISO 27001 requires you to establish, implement, maintain and continually improve the ISMS.
So an ISMS is a cycle. You plan, you carry out, you check and you adjust. Then you start again. What you put on paper is only the trail of that. At a company of twenty people the ISMS often consists of a few documents: a policy, a list of risks, the Statement of Applicability and a work list of controls. On top of that come fixed moments in the calendar to measure, to audit and to review with top management.
Which requirements apply to the ISMS per clause is in the requirements of ISO 27001. Which documents are mandatory is in the mandatory documents. Below is how you build it in practice.
Order for setting up an ISMS
The standard itself says that the order of the clauses says nothing about the order in which you implement them. In practice an ISMS builds on itself. Each part uses the result of the part before it. That is why this order works:
1. Scope of the ISMS
You start with the boundary: which services, departments, locations and systems fall under your ISMS. That is called the scope. Choose it based on the question you want to answer. Does a customer ask for ISO 27001 for your software service? Then that service must be covered, with the people and suppliers who work on it.
ISO has one fixed base text for all management system standards, with guidance alongside. That guidance says that the credibility of a management system depends on a good choice of that boundary. The description must give a factual picture of what is covered. It may not mislead interested parties. A scope that only names the department that is already in order will be exposed by a customer.
2. Risk assessment of your information
Then you record how you assess risks, and only then do you assess them. The method comes first, so that a second round arrives at comparable results. A simple method works well. Give likelihood and consequence each a score from 1 to 5, and agree from which result you must act.
Start with the information and the systems you have. For each system, ask what can go wrong with confidentiality, integrity and availability. A line in your risk list then looks like this: "Customer data in the cloud environment leaked through a stolen password. Owner: IT management. Likelihood 3, consequence 5." What exactly the standard requires regarding the method and the risk owners is in the requirements of ISO 27001.
3. Statement of Applicability
The controls follow from the risks. You compare them with the 93 controls from Annex A, so that you do not miss any. The result is the Statement of Applicability. For each control it states whether you need it, whether it already works and why you exclude it if that is the case. How to build that Statement is in the mandatory documents.
4. Implementing controls with a risk treatment plan
What does not yet work, you put in your risk treatment plan. That plan is a work list with an owner and a date for each control. Start with the risks with the highest score. A control is only implemented when three things are right. There is an agreement. Someone carries out that agreement. And you can show that it happens. An example is two-step login. The agreement is in your access policy. The setting is switched on in your systems. And an export from your admin portal shows that every account uses it.
Some of your controls rest with suppliers, such as your hosting provider or your IT administrator. Request their certificates and reports early. Then your planning does not get stuck on their schedule.
5. Measuring whether your ISMS works
Once the first controls are running, you start measuring. ISO 27001 requires you to determine what you measure, how you measure, when you measure and when you evaluate the results. You keep the results as evidence. In addition, you set information security objectives. Those objectives fit your policy. You make them measurable where possible, and you monitor them.
Measure few things, and choose things you act on. These measurements suit many small companies:
| What you measure | Why it counts |
|---|---|
| Number of security incidents per quarter, and how quickly you handle them | shows whether your incident process works |
| Time between the release of a security update and its installation | shows whether your vulnerabilities are closed in time |
| Result of a restore test of your backup | shows whether your data can really be recovered |
| Access rights that turned out to be no longer needed during a check | shows whether your access management keeps up |
| Share of employees who have completed the annual training | shows whether your people know what is expected of them |
A figure without action makes little sense. The auditor often asks what you did when a figure went the wrong way.
6. Internal audit of your ISMS
With the internal audit you check for yourself whether your ISMS meets the standard and your own arrangements. You also check whether it works in practice. ISO 27001 requires an audit programme: how often you audit, how, who does it and how you report. Parts that are important or caused problems before get more attention. The results go to management.
The standard also requires you to choose auditors objectively and impartially. At a small company that is difficult, because the person who built the ISMS cannot properly audit their own work. Then you hire an outsider. Your certification body may not be that outsider. ISO/IEC 17021-1 calls an internal audit by the certification body a major threat to impartiality. The recognised solution is that the certification body then does not certify your system for two years.
7. Management review of the ISMS
In the management review management looks at fixed moments at whether the ISMS is still suitable, adequate and effective. The fixed structure of ISO standards lists what has to be discussed at a minimum:
- what has been done with the decisions from the previous time
- what has changed inside and outside the company that affects the ISMS
- what customers, suppliers and other interested parties now require of you
- the trend in nonconformities, measurements and audit results
- opportunities to improve.
In 9.3.2 ISO 27001 requires two more topics. Top management also discusses the feedback from interested parties. And it discusses the result of the risk assessment and the status of the risk treatment plan. Then top management sees which risks are still open and which it has accepted.
The outcome is a decision. You record what you improve and what you change in the ISMS. At a small company that can be one meeting with a short report. That is enough if the decisions are in it.
How long an ISMS must run before the ISO 27001 audit
ISO/IEC 17021-1, the standard for certification bodies, does not set a fixed minimum duration for your ISMS. The auditor does check in stage 1 whether your internal audit and management review are planned and under way. In stage 2 they are assessed. So your ISMS must have completed at least one full round. That runs from risk assessment through controls and measurements to internal audit and management review.
How long that takes depends on how many controls you still have to implement. We do not have a fixed number of months for one round.
For ISO 27001 the additional requirements of ISO/IEC 27006-1 also apply to the certification body. We have not been able to check whether that standard sets a minimum duration. The whole process and the lead time are in the steps for ISO 27001.
After the certificate the cycle keeps running. Your certification body comes back at least once per calendar year for a surveillance audit. The first comes no later than twelve months after the decision on your certificate. At every surveillance audit it looks again at your internal audit and management review. An ISMS that comes to a standstill after the first audit therefore stands out at that surveillance audit.
Software, spreadsheet or consultant for your ISMS
Software is not mandatory. A spreadsheet is enough for many small companies, because ISO 27001 does not prescribe a tool. You choose the form of your documents yourself, such as paper, a text file, a spreadsheet or a tool.
The standard does set requirements for how you control those documents. They are approved before they apply. Whoever needs them can find them. They have version control. And they are protected against loss of confidentiality and integrity. That is the test for every tool. The auditor looks at the content and at the evidence. Which program it is in does not matter.
An ISMS in documents and a spreadsheet
A spreadsheet for your risks and your Statement of Applicability, plus policy in your ordinary word processor, is enough for many small companies. It costs no licence, and everyone can work with it. The weak point is control. You have to arrange yourself who may make changes and which version applies. You also have to keep track yourself of when a measurement or check is due again. Store the files in a place with access rights and version history, such as your existing cloud storage.
An ISMS in software
ISMS software links risks, controls and evidence to each other. It sends reminders for recurring tasks. Some tools automatically collect evidence from your cloud environment, such as settings for login or encryption. That saves work if you have many systems or maintain several standards at once. On the other hand there is a subscription and a learning curve. Tools also often come with ready-made policy texts. Adapt them until they describe how you work, because the auditor checks whether you do what is written. Ask beforehand whether you can take your data with you if you stop using the tool.
Which software suppliers there are and how they differ is in ISMS software.
A consultant for your ISMS
A consultant can take over the research and the writing. Running the ISMS stays with you: the measurements, the internal audit by someone else and the management review. Your certification body may not advise you. ISO/IEC 17021-1 forbids a certification body to give advice on setting up a management system. When a consultant pays off and how to choose one is in doing it yourself or a consultant.
If you already have an ISO 9001 system, you can use your own internal audit, management review and document control for both standards. That is explained in combining standards. If you work in healthcare, you build the same ISMS for NEN 7510, with additional controls for health data.
Do you want help with part of your ISMS, such as the risk assessment or the internal audit? At CertificeerWijzer you describe once how far along you are and what you are looking for help with. Then you put the proposals of implementation partners side by side.
Sources
- NEN, NEN-EN-ISO/IEC 27001:2023 nl, preview copy (introduction, clauses 1 to 3) nen.nl
- ISO, ISO/IEC 27001:2022, Information security management systems, Requirements (edition 3) iso.org
- ISO/TMBG, ISO/IEC Harmonized structure for MSS with guidance for use, 2026-07-01 iso.org
- IAS, summary of ISO/IEC 17021-1:2015 section 9 (stage 1, stage 2, surveillance audits) iasonline.org
- IAS, summary of ISO/IEC 17021-1:2015 section 5 (impartiality) cdn-v2.iasonline.org