Who runs the audits
Both stages are run by a certification body you engage directly. For a certificate that tenders and enterprise buyers accept, it must be accredited for ISO 27001. In Australia that usually means JAS-ANZ, or another member of the international recognition arrangement now run by Global ACI, such as UKAS. Certification bodies work to ISO/IEC 17021-1 and ISO/IEC 27006-1, which set out what each stage must cover, how audit time is calculated and how the certification decision is made. Those rules also bar them from consulting on the system they certify. Our guide to ISO 27001 certification bodies in Australia covers accreditation and how to choose one.
Before you book
A certification body will expect you to have completed one full cycle of the ISMS before Stage 2: risk assessment and treatment, an internal audit covering the whole scope, and a management review. Book early. Good auditors are often scheduled weeks ahead.
To quote, the certification body needs your scope, the number of people doing work under the ISMS (including contractors), your sites and a sense of complexity: the technology, outsourcing and information risks involved. ISO/IEC 27006-1 uses those to set the audit days for each stage, so give every body the same facts. If you are working back from a deadline, see how long ISO 27001 takes.
Stage 1: are you ready?
Stage 1 is mostly a documentation and design review, often done remotely in a day or two for an SME. Its purpose is to understand your ISMS well enough to plan Stage 2 and to decide whether you are ready for it. The auditor checks:
- Your scope and context (clause 4), including interested parties, their requirements and whether climate change is a relevant issue
- Your risk method, register and treatment plan
- Your Statement of Applicability, with reasons for inclusions and exclusions
- Mandatory policies and procedures
- How you identify legal, regulatory and contractual requirements, such as privacy obligations
- Internal audit and management review records, and whether both are planned and performed
- Your sites, systems and suppliers, so Stage 2 can be planned and sized
- Whether you're ready to proceed to Stage 2
Expect a conversation as well as a document review. The auditor will ask the ISMS owner to explain how the system works and may talk briefly with leadership.
The output is a written conclusion on your readiness, listing “areas of concern” that could be raised as nonconformities at Stage 2. The certification body can postpone or cancel Stage 2 if Stage 1 shows you aren't ready, so take those areas seriously.
Common Stage 1 areas of concern
- A scope statement that doesn't say clearly which services, locations, people and systems are in, or how you depend on what is out
- A risk register that doesn't follow the documented method, or risks with no named owner
- Statement of Applicability exclusions with no reason given, or controls marked implemented without evidence
- An internal audit that covered only part of the scope
- A management review missing some of the inputs clause 9.3 requires, or held before the internal audit
- Information security objectives with no measures or results
All of these are fixable in the gap before Stage 2. They become nonconformities only if they are still there when the auditor returns.
The gap between the stages
The interval is set with you, and the certification body must allow for the time you need to resolve Stage 1's areas of concern. Two to six weeks is common. Use it to close every area of concern, keep recurring controls running so there is fresh evidence, and brief the people who will be interviewed. If something significant changes in the meantime, such as a new product or system in scope, tell the certification body; it may need to repeat part of Stage 1.
Stage 2: does it work?
Stage 2 is the certification audit proper. Its purpose is to evaluate whether the ISMS is implemented and effective. It covers conformity with every requirement of the standard, how you monitor and measure performance against your objectives, how you meet legal and contractual requirements, operational control of your processes, internal audit and management review, and leadership's responsibility for the policies.
How the days run
You receive an audit plan beforehand naming the areas, people and times. The audit opens with a short meeting to confirm scope and logistics. The auditor then works through the plan, interviewing people across the business, not just IT, and samples evidence that controls are operating: access reviews, onboarding and offboarding records, change tickets, backup tests, training records, supplier assessments and incident logs. Auditors follow trails, so one sampled record often leads to another. A closing meeting presents the findings and the recommendation.
Who gets interviewed
| Who | What the auditor usually explores |
|---|---|
| Leadership | Commitment, policy approval, risk acceptance, resources and the management review |
| ISMS owner | Scope, risk process, Statement of Applicability, objectives, internal audit and corrective actions |
| IT and engineering | Access control, device management, logging, backups, vulnerability management, change and secure development |
| HR or people lead | Screening, onboarding, awareness training, disciplinary process and leavers |
| Operations or procurement | Supplier selection, assessment and monitoring, including cloud services |
| A sample of staff | Whether they know the policies that apply to them and how to report an incident |
On site or remote
ISO/IEC 17021-1 expects Stage 2 at your sites, and IAF MD 4 allows accredited bodies to audit through video and screen sharing where they can still get adequate evidence. For a cloud-first business with no office, much or all of Stage 2 can run remotely. Where physical locations are in scope, expect a visit. Agree the approach when you book.
How findings are graded
A major nonconformity is one that affects the ISMS's ability to achieve its intended results. A minor one doesn't. Several minors against the same requirement can add up to a major if they show a systemic failure.
| Finding | What it means | What you do |
|---|---|---|
| Major nonconformity | A requirement isn't met at all, or a control has broken down | Fix it and have the fix verified before certification |
| Minor nonconformity | An isolated lapse that doesn't undermine the system | Submit a corrective action plan; it's checked at the next audit |
| Opportunity for improvement | A suggestion | Consider it; no formal response required |
Typical Stage 2 majors are a missing or partial internal audit, no management review, or a key control such as access review or backup testing that the records show never ran. Typical minors are one leaver whose access was removed late, or a policy past its review date.
After Stage 2: from findings to certificate
For each nonconformity, the certification body asks you to analyse the cause and set out your correction and corrective action within a time it defines. A good response fixes the immediate problem, finds the root cause and shows how you will prevent it recurring; our article on surveillance audits and recertification sets out the parts of a good response. For a major, the fix must be verified before certification, by documents or a follow-up visit. If that can't happen within six months of the last day of Stage 2, the certification body must run another Stage 2.
The auditor then recommends certification, and someone at the certification body who wasn't on the audit team makes the decision. The certificate is issued, and its three-year cycle runs from that decision.
After certification
Stage 1 and Stage 2 start a three-year cycle. Surveillance audits in each of the next two years re-check a sample of the system, and a recertification audit in year three renews the certificate. See the ISO 27001 audit cycle for what each of those audits covers.
- 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
Preparation checklist
- Brief everyone who might be interviewed on the policies that apply to them
- Gather evidence in one place, named by control
- Close or plan every internal audit finding and every Stage 1 area of concern
- Check your Statement of Applicability matches what is actually running
- Have a named person to guide the auditor and fetch evidence
- Book interviewees' time and test screen sharing for remote sessions
- Answer honestly. “Here's how we handle that” beats a guess
Mistakes on audit day
- Over-answering. Answer the question asked and show the record. Long speculation invites new lines of enquiry.
- Producing evidence on the spot. A record created during the audit is not evidence the control ran.
- Hiding a known gap. If the internal audit found it and you have a corrective action under way, say so. That is the ISMS working.
- Arguing the grade in the room. If you disagree with a finding, ask what evidence would close it and raise it through the certification body's process.
For the full path from first decision to these audits, see how to implement ISO 27001.
We stay with you through both stages
We don't audit our own work, but we do support you through Stage 1 and Stage 2: preparing the team, attending as your advisor and helping respond to findings. See ISO 27001 or book a free 30-minute consultation.
