Year one is done. What now?
Your certificate runs for three years from the certification decision, on condition that you pass a surveillance audit at least once each calendar year in between, the first within 12 months of that decision, and then a recertification audit before expiry. We explain the cycle itself, how audit time is set and how suspension works in the ISO 27001 audit cycle. This article is about the practical side: what the auditor will actually look at, and how to keep the ISMS running so that each audit is routine.
The shift in year two is simple to state. At Stage 2, the auditor wanted evidence that your ISMS was designed properly and had started to operate. At surveillance, the auditor wants evidence that it has kept operating for a year without anyone preparing for an audit. Twelve months of records are much harder to produce at the last minute than a few weeks’ worth.
What a surveillance audit samples
Your certification body sets an audit programme for the cycle, so that by recertification it has covered the whole scope and all the requirements of the standard. Each surveillance audit then has a fixed core and a variable sample.
The fixed core is the same every time: your internal audit, management review, corrective actions from the previous audit, changes since the last visit, how you use the certificate and certification mark, and progress against your information security objectives. The variable sample is chosen from:
- What changed. New systems, suppliers, products, offices or people. Change is where controls most often fall behind.
- What went wrong. Incidents, complaints and any area with findings last time.
- What carries the most risk. The controls your risk assessment says matter most to your business.
- What hasn’t been seen yet. Clauses and Annex A controls not tested at Stage 2 or the last surveillance audit.
The audit plan you receive a few weeks beforehand tells you which areas and people are in the sample. Read it closely, but don’t prepare only those areas. Auditors follow trails, and a sampled supplier review can lead straight to your access control or incident records.
What must keep running all year
These are the activities that produce the evidence a surveillance auditor asks for. Each should run to the schedule you set yourself in your ISMS, and each should leave a dated record.
| Activity | Where it comes from | What the auditor wants to see |
|---|---|---|
| Internal audit | Clause 9.2 | A programme that covers the scope over the cycle, audits done by people not auditing their own work, findings recorded and acted on |
| Management review | Clause 9.3 | Top management reviewing every required input, including changes in interested parties’ needs, and recorded decisions |
| Risk assessment and risk treatment | Clauses 6.1, 8.2 and 8.3 | Risks reassessed at the planned interval and after significant change; treatment actions completed or progressing |
| Objectives and metrics | Clauses 6.2 and 9.1 | Measurements actually taken, analysed and reported, not just defined |
| Corrective actions | Clause 10.2 | Root causes identified, actions completed and their effectiveness checked |
| Training and awareness | Clauses 7.2 and 7.3; control 6.3 | New starters inducted, annual awareness completed, competence records for key roles |
| Supplier reviews | Controls 5.19 to 5.23 | Key suppliers assessed and monitored at the frequency you set, including cloud services |
| Recurring technical controls | Controls such as 5.18, 8.8, 8.13 and 8.15 | Access reviews, vulnerability management, backup restore tests and log review, all with evidence |
| Document review | Clause 7.5 | Policies and procedures reviewed at their stated intervals, with versions controlled |
A compliance platform can collect much of the technical evidence automatically, but it can’t hold your management review or decide your risks for you. See consultant, platform or both? and which documents and records ISO 27001 requires.
Why organisations get findings in year two
The common causes are predictable, and most have nothing to do with technical security.
- The internal audit didn’t happen, or wasn’t impartial. The person who runs the ISMS audited it, or the audit covered only a corner of the scope. This is the most frequent route to a major.
- Management review was skipped or thin. A short meeting with no record of the required inputs, or no decisions coming out of it.
- The risk assessment is a year old. Nothing was reassessed, even though the business added a product, a supplier or new AI tools.
- Changes weren’t carried through. A new system went live without the Statement of Applicability, asset register or access process catching up. Clause 6.3 expects changes to the ISMS to be planned.
- Findings closed on paper. Last year’s corrective actions were marked done, but the same problem is still there, which suggests the root cause was never addressed.
- Recurring controls lapsed. Quarterly access reviews that stopped after the first quarter, a backup that was never test-restored, training records missing for recent hires.
- Metrics defined but never measured. Objectives set at Stage 2 with no data a year later.
- Context not revisited. Clauses 4.1 and 4.2, which since Amendment 1:2024 include whether climate change is a relevant issue, still read exactly as they did before certification.
- Overstated certificate claims. Marketing material that implies the whole company is certified when the scope covers one product.
How to prepare in the months before
Most of the work should already be happening as part of normal operation. What follows is the checkpoint schedule that turns that into a calm audit.
| When | What to do |
|---|---|
| As soon as the last audit closes | Confirm next year’s audit dates with your certification body; put internal audit, management review and recurring controls in the calendar |
| Throughout the year | Log changes as they happen, run recurring controls, update the risk register when something significant changes |
| 4 to 6 months before | Check last year’s findings are closed and the fixes worked; confirm the internal audit plan and auditor |
| 2 to 3 months before | Run the internal audit, then the management review using its results; raise corrective actions for anything found |
| 1 month before | Review the risk assessment and Statement of Applicability for the year’s changes; tell the certification body about any significant change if you haven’t already |
| When the audit plan arrives | Brief the people named in it, check their evidence is current and book their time |
Leaving the internal audit until the final fortnight is a common mistake. If it finds problems, there is no time to fix them, and the certification auditor will see open findings you haven’t started on.
Handling nonconformities
Findings are graded the same way as at Stage 2: major, minor or opportunity for improvement. What matters after the audit is the quality of your response. A good response to any nonconformity has four parts:
- Correction. What you did to fix the immediate problem, such as completing the missed access review.
- Root cause. Why it happened. “Human error” is rarely enough; ask why the process allowed it.
- Corrective action. What you changed so it won’t recur, with an owner and a date.
- Evidence of effectiveness. How you will show the fix worked, and when.
For a major, the certification body sets a short deadline and verifies the fix, sometimes through a follow-up visit. Missing that deadline can lead to suspension. For a minor, the body accepts your plan and checks it at the next audit. A minor that comes back next year signals the corrective action failed and can be raised as a major, so treat minors as seriously as the auditor will next time. Record external findings in the same register as your internal ones so nothing is tracked in two places.
Recertification: what changes in year three
Recertification is not a bigger surveillance audit. The auditor reviews the ISMS as a whole and asks whether it has been effective across all three years, in light of what changed inside and outside the business. Previous surveillance reports are part of the evidence, so recurring findings and slow corrective actions will show.
Three things to plan for:
- Timing. The audit must be completed, and the certification decision made, before the expiry date. Any major nonconformity must be corrected and verified before expiry too. Book the audit well ahead so there is time to close findings if needed.
- Full coverage. Every clause and every applicable Annex A control is in play. Controls that were never sampled during surveillance get their first close look.
- A chance to reset. Recertification is a natural point to revisit scope, refresh risk methodology, or move to another certification body.
Scope changes after year one
Businesses change, and the certificate has to keep up. If you add a product, office, entity or a large group of people, update your scope statement, risk assessment and Statement of Applicability first, then tell your certification body. Extending scope usually needs extra audit time at the next audit or in a special audit before the certificate is reissued. Reducing scope is simpler but still needs the certificate amended. Customers notice when the certificate stops matching what they buy, especially enterprise buyers who check it each year. For how scope affects effort, see ISO 27001 cost in Australia.
Changing certification body
If you are unhappy with your certification body’s scheduling, sector knowledge or responsiveness, you can move. Accredited certificates transfer under IAF MD 2, and the new body continues your cycle rather than restarting it, provided the certificate is valid and any open majors are resolved. Most organisations move between audits or ahead of recertification. Our guide to ISO 27001 certification bodies in Australia covers what to look for in a new one.
Keeping it running
Years two and three are where an ISMS either becomes part of how the business runs or turns into an annual scramble. The difference is usually someone owning the calendar. Running that calendar, the internal audits, management review preparation and recurring control evidence, is what our managed compliance retainer takes on, so the surveillance audit confirms what is already happening.
Next step
If you run the ISMS yourself, the activity most worth bringing in from outside is the internal audit. ISO 27001 requires internal auditors to be objective and impartial, so staff can do it only where they aren’t auditing their own work, and in a small team the person who runs the ISMS is often the only one who knows it. Our independent internal audit is carried out by a Lead Auditor and timed ahead of your surveillance or recertification audit. See ISO 27001 for how we work, or book a free 30-minute consultation to talk through your next audit.
