Clause 9.2 of ISO 27001 requires an internal audit before you can be certified, and your certification body checks at Stage 1 that it happened. A good internal audit is also the cheapest way to find what Stage 2 would otherwise find. This guide covers who can audit, how to plan the programme, how to run it and how to close findings. For hands-on help, see our ISO 27001 consulting page.
Is an internal audit mandatory for ISO 27001?
Yes. Clause 9.2 requires internal audits at planned intervals to check that your ISMS meets your own requirements and those of ISO 27001, and that it is effectively implemented and maintained. An internal audit and a management review (clause 9.3) must be completed before certification, and auditors check both at Stage 1.
A "paper" internal audit, written up without anyone looking at real records, rarely survives Stage 1. Certification auditors read the report, check the dates and often ask how samples were chosen.
Who can perform an ISO 27001 internal audit?
Anyone competent and objective can, whether an employee or an external auditor. The standard requires auditors to be chosen so the audit is objective and impartial, which in practice means nobody audits their own work. Small companies often use an outside auditor for this reason, or have departments audit each other.
Competence means three things:
- The standard: the auditor understands ISO 27001 clauses 4 to 10 and the Annex A controls in scope.
- Audit technique: planning, interviewing, sampling and writing findings. ISO 19011 gives guidance on auditing management systems.
- Your business: enough understanding of how your teams work to ask useful questions.
Keep evidence of each auditor's competence, such as training records or experience, because certification auditors may ask for it.
Plan the audit programme
Clause 9.2.2 asks you to plan, set up, run and maintain an audit programme. It must cover frequency, methods, responsibilities, planning requirements and reporting, and take account of how important each process is and the results of earlier audits.
A simple programme can be one table. This example is generic:
| Audit | What it covers | Auditor | When |
|---|---|---|---|
| 1 | Clauses 4 to 7: context, leadership, risk, support | External auditor | First quarter |
| 2 | Clause 8 and organisational controls (5.1 to 5.37) | External auditor | Second quarter |
| 3 | People, physical and technological controls (6, 7 and 8) | Internal auditor from finance | Third quarter |
| 4 | Clauses 9 and 10, and follow-up of earlier findings | External auditor | Fourth quarter |
Before your first certification, many companies run one full audit instead, so that every clause and every applicable control has been audited before Stage 1.
How often should you run an internal audit?
ISO 27001 says "at planned intervals" and leaves the frequency to you. Most organisations cover the full ISMS at least once in each annual cycle, either in one audit or in parts across the year. Audit high-risk areas and areas with earlier findings more often, and record your reasoning in the audit programme.
Prepare each audit: scope, criteria and checklist
For each audit, write a short audit plan: the scope, the criteria (ISO 27001, your policies and the Statement of Applicability), the areas and people involved, and the dates. Share it with the auditees in advance so the right people and records are available.
A checklist keeps the audit consistent. Our ISO 27001 audit checklist lists clauses 4 to 10 and all 93 Annex A controls with the evidence that satisfies each. Treat it as a starting point: add questions about your own processes and risks.
Run the audit: interviews, evidence and sampling
- Opening meeting. Confirm scope, timings and how findings will be reported.
- Interviews. Ask people to show you how they do the work, not to recite the policy.
- Records. Look at the evidence a process produces: access reviews, change tickets, backup tests, training records, supplier reviews.
- Sampling. Choose samples from the full population, not from a list the auditee prepared. To test leaver access, for example, take leavers from the HR system and check each one in your identity and SaaS tools.
- Closing meeting. Present the findings and agree next steps.
ISO 27001 does not set a sample size. Pick enough items to be confident in your conclusion, and record how you chose them.
How should you grade and report findings?
Grade each finding as a major nonconformity, a minor nonconformity or an opportunity for improvement, using the same definitions as your certification body. Write each one with the requirement, the evidence you saw and why it falls short. Report the results to relevant management and keep the report as evidence of the audit.
A major nonconformity is a total absence of a required process, or a breakdown with real impact. A minor is an isolated lapse. A well-written finding looks like this:
- Requirement: Annex A 5.18 Access rights and the access control policy, which requires quarterly access reviews.
- Evidence: No access review records for the finance system for the last two quarters.
- Finding: Minor nonconformity. Access reviews are not carried out as the policy requires.
Close findings before Stage 1
Handle every nonconformity through corrective action, as clause 10.2 requires:
- Fix the immediate problem.
- Find the root cause.
- Take action so it does not happen again.
- Check the action worked, and keep a record.
Then hold the management review. Clause 9.3 lists audit results as an input, so the review should discuss what the internal audit found and what was done. The order before certification is: internal audit, corrective action, management review, then Stage 1.
Internal audit vs certification audit
The two audits use similar techniques but serve different purposes. Your internal audit is a tool for you: it should find problems so you can fix them. The certification audit is the certification body's independent check, and it relies on your internal audit having been done properly.
| Internal audit | Certification audit | |
|---|---|---|
| Who performs it | A competent, objective auditor you appoint, from inside or outside the company | An accredited certification body |
| Purpose | Find and fix gaps, and meet clause 9.2 | Decide whether to certify, then confirm certification each year |
| Outcome | Findings that feed your corrective action process and management review | A certification decision, then surveillance audits |
| Frequency | At planned intervals you set in the audit programme | Stage 1 and Stage 2, surveillance audits in years two and three, recertification in year three |
An internal audit that finds nothing is not a good sign. Auditors expect a working ISMS to turn up some issues, and to see them handled.
Common internal audit mistakes
- The person who built the ISMS audits it, so impartiality is not shown.
- The audit only reviews documents and never samples records.
- Findings are vague, with no requirement or evidence quoted.
- Corrective actions are recorded but never checked for effectiveness.
- Some applicable Annex A controls are never audited at all.
- The management review happens before the internal audit, so it cannot consider the results.
How CyberWave GRC helps
We can run your internal audit with auditors who were not involved in building your ISMS, or train your own staff to do it and review their first audit. Our ISO 27001 work is a fixed fee, end to end, including the audit, quoted after a free scoping call. Your accredited certification body performs Stage 1 and Stage 2 and issues the certificate; we prepare you and coordinate.
Next, read what happens after certification in ISO 27001 surveillance audits.


