
The ISO 27001 audit: stage 1, stage 2 and what the auditor wants from your IT
An ISO 27001 audit rarely goes wrong on the policy wording. It goes wrong on the sample: the auditor points at a leaver, a laptop or a backup and asks you to show what happened and when. This article walks through the audit days from the side that has to produce the evidence: IT.
A certification audit has two parts: stage 1 checks whether your ISMS holds up on paper, stage 2 whether it works in practice.
The auditor works by sampling, so evidence has to be retrievable case by case: a date, a name, an export from the system.
The audit is carried out by an accredited certification body. We deliver the technical controls and the evidence, but we do not audit or certify anyone.
The ISO 27001 audits you will meet
When people say “the ISO 27001 audit” they usually mean the certification audit, but there are four, and each has a different purpose.
- The internal audit. The standard requires you to check, at planned intervals, whether your ISMS works. It is done by someone independent of the work being assessed. Without at least one completed internal audit and a management review, a certification body will not start stage 2.
- The certification audit. Carried out by a certification body in two parts: stage 1 and stage 2. Choose a body accredited for ISO 27001, in the UK by UKAS; a certificate without accreditation tells a customer little.
- Surveillance audits. A certificate is valid for three years, with a shorter audit in years two and three covering part of the controls and the previous findings.
- Recertification. A full audit again after three years.
On top of that, a customer may audit you as a supplier. That is a contractual audit rather than an ISO one, and it often asks the same questions.
Stage 1: the document review
In stage 1 the auditor checks whether your ISMS is complete on paper and whether you are ready for stage 2. It is often partly remote. Among other things, the auditor reads:
- The scope: which sites, processes and systems are covered, and what is deliberately left out.
- The risk assessment and treatment plan: which method you use, which risks you found and what you do about them.
- The statement of applicability: which controls from the annex of the standard you apply and why the rest do not apply.
- Policy, roles and objectives, plus the internal audit report and the management review.
Stage 1 ends with a report listing areas of concern. You resolve those before stage 2, usually a few weeks later. For IT, stage 1 is the moment to check that what the documents say is actually configured. A policy promising multi-factor authentication for everyone, while three service accounts do not have it, becomes a finding in stage 2.
Stage 2: does it work in practice
In stage 2 the auditor comes to see whether the ISMS does what the documents say. They interview people, from the board to the service desk, and ask for evidence through samples. They do not look at everything; they choose.
A typical question for IT sounds like this: “Show me the last three leavers and when their accounts were disabled.” Or: “Which laptops are missing the latest security update, and since when?” The answer is an export or a screen from the system itself, with a date, not an explanation of how it usually goes.
The audit closes with a meeting setting out the findings. If there is no major nonconformity, the auditor recommends certification; the decision itself is taken by the certification body.
The statement of applicability
The statement of applicability is the document the auditor returns to most often. The annex of ISO 27001:2022 lists 93 controls in four themes: organisational, people, physical and technological. For each control you record:
- whether it applies, and why, with a reference to the risk or requirement that makes it necessary;
- if it does not apply: why not, in a sentence an outsider understands;
- how far implementation has got;
- where the evidence is: which system, which report, which procedure.
That last column shortens the audit day more than anything you do the evening before. If you know for every technical control which system the evidence comes from, nobody has to search during the audit. What an IT supplier usually delivers here and what stays with you is set out in our ISO 27001 checklist from the IT side.
What the auditor wants to see from IT
Questions differ by auditor, but the evidence IT must be able to show always comes from the same sources:
- A current list of devices and systems, with an owner per line, and an explanation of what has been added or removed since last time.
- Access: how joiners and leavers are handled, with dates; a periodic review of who has which rights, with the outcome; multi-factor coverage and who holds the admin accounts.
- Patching: a report showing which systems are up to date and which are not, and what happens to the exceptions.
- Backup: not just that it runs, but the record of a restore test.
- Logging: what is recorded, for how long, and who looks at it.
- Changes and incidents: from the ticketing system, with who approved and what happened.
- Suppliers: which parties have access to your data or systems, and what has been agreed with them.
The pattern: a control without a trail does not exist for the auditor. A restore test that was done but not recorded counts as a test that was not done.
Preparing for the audit day
Most of the stress on an audit day comes from searching. Four things prevent it:
- An evidence index. A list showing, per control, where the evidence is and who can show it. The column from the statement of applicability is the start of it.
- A dress rehearsal. Have someone spend an hour drawing samples the way an auditor would. Anything you cannot show within a few minutes is work for the weeks after.
- The right people in the room. Whoever runs the system shows it. If a supplier manages it, agree in advance that they are available or supply the evidence.
- Show, don’t tell. Answer the question asked, show it in the system, and say so if something is missing. An auditor prefers an honest gap to a story that falls apart at the next sample.
Findings, and what you do with them
An auditor records three kinds of finding. A major nonconformity means a requirement of the standard is not met, or barely; while it is open, no certificate is issued. A minor nonconformity is a requirement that is partly met; you submit a corrective action plan, and the auditor checks at the next audit that it was carried out. An observation or opportunity for improvement is advice.
IT findings we see often: an access review that was scheduled and not done, a restore test with no record, a device list that lags behind, and a statement of applicability that still points to an old control or a colleague who has left.
For every nonconformity, fix the cause and not only the instance. Disabling a forgotten account is the instance; a leavers process that does not reach IT automatically is the cause, and that is what the auditor asks about again at the next surveillance audit.
Where our work stops
What we do. We implement the technical controls in your statement of applicability, make sure they leave a trail, and supply the evidence from the systems we manage: reports on access, patching, backups and changes. On the audit day we will show how that part works if you want us to. We are ISO/IEC 27001 certified ourselves, so we know which questions come from that side of the table.
What we do not do. We are not a certification body and not an auditor. We do not carry out certification audits, do not judge whether you will pass, and certify no one. Scope, risk assessment and statement of applicability belong to your organisation; we do not set or approve them. And the internal audit of controls we operate ourselves should be done by someone other than us.
Questions we get about this
The five that come up most often.
What is the difference between a stage 1 and a stage 2 audit?
In stage 1 the auditor reviews the documents: scope, risk assessment, statement of applicability, policy, internal audit and management review. In stage 2 they test whether the ISMS works in practice, through interviews and samples. There are usually a few weeks between the two to resolve the stage 1 concerns.
How long is an ISO 27001 certificate valid?
Three years. In years two and three there is a surveillance audit covering part of the controls and the previous findings. After three years comes recertification, which is a full audit again.
What happens with a major nonconformity?
A major nonconformity means a requirement of the standard is not met, or barely. While it is open, no certificate is issued. You fix it and show the evidence, after which the certification body decides whether that is sufficient.
What does an ISO 27001 auditor want to see from IT?
Evidence from the systems themselves: a current device list, how joiners and leavers are handled with dates, a periodic access review, patch status, the record of a backup restore test, logging and changes from the ticketing system. The auditor samples, so each case has to be retrievable.
Can you carry out our ISO 27001 audit or certify us?
No. We are not a certification body and not an auditor, and we certify no one. The certification audit is done by an accredited body. We implement the technical controls and supply the evidence from the systems we manage.
Further reading
What the audit connects to.
Shall we check your evidence before the auditor does?
Send us your statement of applicability. For the technical controls we will tell you where the evidence comes from and where it is missing today; the verdict we leave to your auditor.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.