Three kinds of ISO 27001 audit
"ISO 27001 audit" can mean three different things, and it helps to keep them apart.
- Internal audits (first-party). Clause 9.2 requires you to audit your own ISMS at planned intervals. The auditor can be on staff or external, but must be objective and impartial, which in practice means they can't audit their own work.
- Customer audits (second-party). A customer or prospect audits you as a supplier, usually through a security questionnaire, sometimes on site. These sit outside certification, though a current certificate often shortens them.
- Certification audits (third-party). An accredited certification body audits you against ISO/IEC 27001:2022 and issues, maintains or renews your certificate. The rest of this article is about these.
The three connect. Your internal audit is one of the first things the certification auditor reviews, every year.
Who sets the rules: accreditation, JAS-ANZ and the IAF
Certification bodies are themselves audited. To issue accredited ISO 27001 certificates, a body must meet ISO/IEC 17021-1, the general standard for management system certification, and ISO/IEC 27006-1, which adds requirements specific to information security. Those two standards set the shape of the cycle described here: how often you are audited, how long audits are and what must happen before a certificate is issued or renewed.
In Australia and New Zealand the accreditation body is JAS-ANZ, the Joint Accreditation System of Australia and New Zealand. JAS-ANZ is a signatory to the International Accreditation Forum (IAF) multilateral arrangement, so certificates issued under its accreditation are recognised by other IAF members, and vice versa. A certificate from a body accredited by another IAF member, such as UKAS in the UK, carries the same weight.
Before you engage a certification body, check it is accredited for ISO 27001 on the JAS-ANZ register or the IAF's CertSearch database. The same check works in reverse: you can look up a supplier's certificate to confirm it is current and covers the scope they claim. A certificate from an unaccredited body won't satisfy most tenders or enterprise customers.
The three-year cycle at a glance
- Before Build and internal audit Implementation, then a full internal audit and management review
- Year 0 Stage 1 audit Certification body reviews your documented system and readiness
- Year 0 Stage 2 audit Certification body tests that the system operates; certificate issued
- Year 1 Surveillance audit A sample of the system re-checked, after your annual internal audit
- Year 2 Surveillance audit Another sample re-checked, after your annual internal audit
- Year 3 Recertification A full audit renews the certificate for another three years
| When | Audit | What it does |
|---|---|---|
| Year 0 | Initial certification: Stage 1 and Stage 2 | Checks the ISMS is designed and operating; certificate issued |
| Within 12 months of the certification decision | First surveillance audit | Re-checks a sample of the ISMS, including internal audit, management review and corrective actions |
| Following calendar year | Second surveillance audit | Another sample, chosen to cover different parts of the scope |
| Before the three-year expiry | Recertification audit | Reviews the whole ISMS and its performance over the cycle; certificate renewed |
Initial certification: Stage 1 and Stage 2
The cycle starts with a two-stage certification audit. Stage 1 reviews your documented ISMS and whether you're ready: scope, risk assessment, Statement of Applicability, policies, internal audit and management review. Stage 2 tests whether the system actually operates, through interviews and evidence sampling. The auditor then recommends certification, an independent reviewer at the certification body makes the decision, and the certificate is issued. The date of that decision is what the rest of the cycle is measured from.
We cover both stages in detail, including how to prepare, in ISO 27001 Stage 1 and Stage 2 audits. For how long it takes to reach Stage 2 in the first place, see how long ISO 27001 takes.
Surveillance audits: years one and two
Under ISO/IEC 17021-1, surveillance audits happen at least once each calendar year, except in the year of recertification. The first must be held no later than 12 months after the certification decision. Certification bodies usually schedule later surveillance audits around the anniversary of that first one, so you can plan for them well ahead. Some bodies allow a little flexibility on exact dates, but treat the 12-month limit for the first audit as fixed.
A surveillance audit is shorter than Stage 2 and doesn't re-examine everything. Certification bodies typically plan the samples across the cycle so that, by recertification, most or all of your scope and applicable controls have been looked at. Each surveillance audit normally covers:
- Internal audit. Has it been done since the last visit, against a plan, by someone objective, and were the findings acted on?
- Management review. Did top management review the ISMS with the inputs clause 9.3 calls for, and did decisions come out of it?
- Corrective actions. Are the nonconformities from the previous audit closed, and did the fixes work? Clause 10.2 expects you to deal with root causes, not just the symptom.
- Changes. New systems, suppliers, offices, products, acquisitions or restructures. The auditor checks that changes to the ISMS itself were planned under clause 6.3, that operational changes were controlled under clause 8.1, with risk reassessed under 8.2 where a change was significant, and that your risk assessment and Statement of Applicability were updated to match.
- Use of the certificate and certification mark. Whether you describe your certification accurately, for example not implying it covers parts of the business outside scope, and follow your certification body's rules for its mark.
- Complaints and objectives. How you handled relevant complaints and how you're tracking against your information security objectives.
- A subset of Annex A controls. A sample of controls, often weighted towards higher-risk areas and anything that changed, tested through evidence and interviews.
The sample shifts each year, so a control that wasn't looked at in year one may be the focus in year two. That's why it pays to keep every applicable control running, not just the ones last audited.
Recertification: year three
A recertification audit must be completed, and the certification body's decision made, before the certificate's expiry date. In practice that means booking it several months ahead, leaving time to close any major nonconformities before the deadline.
Recertification looks at the ISMS as a whole rather than a sample. The auditor reviews whether you still meet all the requirements of ISO 27001, how effective the system has been over the full three years in light of internal and external changes, and whether you remain committed to maintaining and improving it. Previous surveillance reports are part of the input, so recurring findings will be noticed. Where there have been significant changes, such as a major restructure or a much larger scope, the certification body may add a Stage 1 style review. A successful recertification starts a new three-year cycle.
How audit time is set
Certification bodies don't decide audit length by feel. ISO/IEC 27006-1 sets out how to calculate audit time, starting mainly from the number of people doing work under the ISMS, including contractors, then adjusting for complexity: the number of sites, the nature of the business and its information risks, the technology involved, outsourcing, and how mature the ISMS already is. The initial audit is the longest. Each surveillance audit is shorter, and recertification sits in between.
Because audit time follows scope, the most effective way to keep audits proportionate is to scope sensibly from the start. We cover what drives the overall effort in ISO 27001 cost in Australia.
Findings: nonconformities and opportunities for improvement
Every audit in the cycle uses the same grading.
| Finding | What it means | What you do |
|---|---|---|
| Major nonconformity | A requirement isn't met at all, or a control or process has broken down in a way that puts the ISMS's outcomes in doubt | Correct it and take corrective action within the time the certification body sets; the fix is verified, sometimes through a follow-up visit |
| Minor nonconformity | An isolated lapse that doesn't undermine the system | Submit a corrective action plan; the auditor checks it worked at the next audit |
| Opportunity for improvement | An observation or suggestion | Consider it; no formal response required |
Two patterns cause most trouble after certification. The first is a missed internal audit or management review, which auditors usually grade as major because the ISMS has stopped checking itself. The second is a minor nonconformity that comes back. If the same lapse appears at the next audit, it suggests the corrective action didn't address the cause, and auditors may raise it as a major.
Suspension and withdrawal
If you don't close a major nonconformity in time, refuse or can't hold a surveillance or recertification audit when required, or the ISMS seriously fails to meet the standard, the certification body can suspend your certificate. While suspended, the certificate is temporarily invalid and you must not claim to be certified. Suspensions are for a limited period, and if the cause isn't resolved, the certification body withdraws the certificate or reduces its scope to the parts that still conform. You can also ask for a voluntary suspension, for example during a major restructure.
Withdrawal is visible to others. Accredited certificates are listed on public registers, so a customer checking yours will see that it is no longer valid.
Changes during the cycle
Changing scope
Tell your certification body before a significant change, not at the next audit. Extending scope to a new product, office or entity usually needs extra audit time, either at the next scheduled audit or in a special audit, before the certificate is reissued. Reducing scope is simpler, but the certificate must be amended so it doesn't claim more than you deliver. Either way, update your scope statement, risk assessment and Statement of Applicability first.
Changing certification body
You can move to a different accredited certification body during the cycle. Transfers follow IAF MD 2. The new body carries out a pre-transfer review of your certificate, your last certification or recertification report, the latest surveillance report and the status of any open nonconformities. It may visit if, for example, there are open majors. If all is in order, it continues your existing cycle and sets the audit programme for the rest of it, rather than starting again. Only a valid accredited certificate can be transferred; a suspended one can't, and one from an unaccredited body is treated as a new certification.
When certification lapses
If the recertification audit isn't completed, or a major nonconformity isn't verified as closed, before the expiry date, the certificate expires. ISO/IEC 17021-1 generally lets the certification body restore it within six months if the outstanding recertification work is completed, though the certificate shows the gap and keeps the original cycle dates. After that window, expect at least a full Stage 2 audit. For customers and tenders, any gap in validity is a problem, so treat the expiry date as a hard deadline.
The 2013 to 2022 transition is over
ISO/IEC 27001:2022 replaced the 2013 edition, and IAF MD 26 gave certified organisations until 31 October 2025 to transition. That deadline has passed. Certificates to ISO/IEC 27001:2013 are no longer valid, and every certification, surveillance and recertification audit is now against the 2022 edition, including Amendment 1:2024, which added climate change considerations to clauses 4.1 and 4.2. If a supplier gives you a 2013 certificate, it has expired; ask for their current one and check it on the register.
Keeping years two and three routine
The organisations that find surveillance audits uneventful are the ones that run the ISMS on a calendar rather than around the audit date. A few habits make the difference:
- Fix the internal audit and management review dates. Schedule both a few months before each surveillance audit, every year, so there is time to act on what they find. Plan the internal audit so the whole scope is covered over the cycle.
- Close findings as you go. Keep one register of nonconformities from internal and external audits, with owners and dates, and check the fixes worked.
- Run recurring controls on a schedule. Access reviews, backup tests, supplier reviews, training, vulnerability management and risk review should leave evidence every time, not just before an audit.
- Record changes when they happen. A short change note and an updated risk entry beat reconstructing a year of changes for the auditor.
- Keep evidence current. The mandatory documents and records should be reviewed at the intervals you've set, with dates to show it.
- Book audits early. Confirm surveillance dates with your certification body as soon as the previous audit closes, and book recertification well before expiry.
If you're still at the start, how to implement ISO 27001 sets up these habits from the beginning. Keeping the ISMS running between audits is where many teams lose momentum once the certificate is on the wall, and it's the part our managed compliance retainer takes on: internal audits, management review preparation, control upkeep and support through each surveillance and recertification audit.
For a practical guide to what auditors sample in years two and three, the common findings and a preparation timeline, see surveillance audits and recertification: what to expect after year one.
Next step
If you run your ISMS yourself, the piece most worth bringing in from outside is the internal audit. ISO 27001 requires internal auditors to be objective and impartial, so the person who built or runs the system shouldn't audit it. Our independent internal audit is carried out by a Lead Auditor and timed ahead of your surveillance or recertification audit. For the full picture, see ISO 27001, or book a free 30-minute consultation to talk through where you are in the cycle.
