Skip to main content
ISO 27001

ISO 27001 Surveillance Audits: What to Expect Each Year

Published
Last updated
ISO 27001
A three-step cycle of a certificate, a magnifying glass and a refresh arrow around a certificate with a ribbon and a shield, representing the ISO 27001 surveillance audit cycle

Getting ISO 27001 certified is the start of a three-year cycle, not the end of the project. In years two and three, your certification body comes back for surveillance audits to confirm that your ISMS is still working. This guide explains what happens, what auditors check, the findings we see most often and how to stay ready between visits. For hands-on help, see our ISO 27001 consulting page.

What is an ISO 27001 surveillance audit?

A surveillance audit is a shorter audit your certification body carries out in years two and three of your certificate's three-year cycle. It checks that your ISMS is still operating, that you have dealt with earlier findings and that you keep improving. Your certificate stays valid only while you pass these audits.

The three-year certification cycle

YearWhat happens
Year 1Initial certification: Stage 1 reviews documentation and readiness, Stage 2 tests implementation, and the certificate is issued
Year 2First surveillance audit
Year 3Second surveillance audit, then a recertification audit before the certificate expires

A successful recertification audit starts a new three-year cycle with a new certificate. Your certification body sets the audit dates, so put them in your calendar as soon as you are certified.

What do auditors check in a surveillance audit?

Auditors check that your internal audit and management review have happened since the last visit, that earlier nonconformities were closed, how you handled changes, incidents and complaints, and a sample of Annex A controls. Some core ISMS requirements are checked every time, while the sampled controls usually change from visit to visit.

Expect questions on:

  • Internal audit (clause 9.2): did the audit programme run as planned?
  • Management review (clause 9.3): was it held, with the required inputs and recorded decisions?
  • Earlier findings: were corrective actions completed, and did they work?
  • Changes: new products, offices, suppliers, systems or key people, and how the ISMS responded.
  • Risk assessment: was it repeated at the planned interval and after significant changes?
  • Statement of Applicability: does it still match your risks and environment?
  • Sampled controls: evidence that selected Annex A controls are still operating.
  • Use of the certificate: that you describe your certification and scope accurately.

How is a surveillance audit different from Stage 2 and recertification?

Stage 2 tests your whole ISMS for the first time. A surveillance audit is shorter and samples parts of it, alongside core requirements checked every time. A recertification audit, in year three, reviews the whole ISMS again so the certification body can decide whether to issue a new three-year certificate.

Because each surveillance audit only samples, you can't predict exactly which controls will be checked. The safe assumption is that any applicable control could be.

Common surveillance audit findings

These are the patterns we see most often after the first year:

  1. The internal audit slipped. It was planned but not done, or only part of the scope was covered.
  2. The management review is thin. It was held late, skipped required inputs or recorded no decisions.
  3. The risk assessment is stale. Nothing was reassessed after a new product, office or cloud move.
  4. Earlier corrective actions are open. Or they were closed without checking they worked.
  5. Routine records stopped. Access reviews, backup restore tests or supplier reviews were done before certification, then quietly dropped.
  6. Training gaps for new joiners. People hired since the last audit missed awareness training.
  7. Unreported changes. The scope changed, but the certification body was never told.

Most of these share one cause. After certification, the project team moves on and nobody owns the ISMS calendar.

How do you stay ready between audits?

Run your ISMS on a calendar, not a sprint before each audit. Schedule access reviews, risk reviews, supplier reviews, training, the internal audit and the management review across the year, give each an owner, and keep evidence as you go. Then the surveillance audit simply samples records you already have.

A generic example calendar:

QuarterActivities
Q1Access review; supplier review; awareness training for new joiners
Q2Access review; risk assessment review; backup restore test; first part of the internal audit
Q3Access review; incident response exercise; second part of the internal audit
Q4Access review; management review; update the Statement of Applicability; prepare for the surveillance audit

Adjust the frequencies to your own policies. The point is that every recurring control has a date and an owner.

Before the visit: a short checklist

  • The internal audit for the period is complete, with a report.
  • The management review has been held and its minutes record decisions.
  • Corrective actions from the last audit are closed, with evidence they worked.
  • The risk assessment and Statement of Applicability reflect current changes.
  • Recurring records are up to date: access reviews, backups, supplier reviews and training.
  • New joiners since the last audit have completed awareness training.
  • Any scope or location changes have been reported to the certification body.
  • The people the auditor will interview know the date and what to bring.

What happens on the day

A surveillance audit follows the same shape as Stage 2, only shorter. It starts with an opening meeting to confirm the plan, then moves to interviews, record sampling and site walk-throughs where relevant, and ends with a closing meeting where the auditor presents findings. For a minor nonconformity, you agree a corrective action plan within the timeframe the certification body sets. A major nonconformity has to be resolved, and the body may need to verify the fix before confirming your certificate.

Tell your certification body about significant changes

If your scope, locations, ownership, headcount or major systems change, tell your certification body. It may need to adjust the audit, for example by adding time or visiting a new site. Finding an unreported scope change at the audit is a much bigger problem than reporting it early. Keep a simple change log during the year, so you can show the auditor what changed, when, and how the ISMS was updated in response.

What happens if you miss a surveillance audit?

Talk to your certification body straight away. Surveillance audits must happen within the timeframe it sets, and if one is missed or major nonconformities are not resolved, the body can suspend or withdraw your certificate. During a suspension you cannot claim to be certified, so agree a new date before the deadline passes.

How CyberWave GRC helps

We help certified clients keep the ISMS running between audits: setting up the yearly calendar, running or supporting the internal audit, preparing the management review and getting evidence ready before each visit. We also support you on audit days and with corrective actions afterwards. The surveillance audit itself is carried out by your accredited certification body, which also decides on your certificate; we prepare you and coordinate end to end.

Before your next visit, run through our ISO 27001 audit checklist, and make sure your internal audit for the period is complete.

Frequently asked questions

An ISO 27001 certificate is valid for three years. To keep it, you pass a surveillance audit in year two and another in year three. A recertification audit in year three, before the certificate expires, reviews the whole ISMS and, if successful, starts a new three-year cycle with a new certificate.

Yes, usually. A surveillance audit samples parts of your ISMS rather than testing everything, so it normally takes less auditor time than Stage 1 and Stage 2 together. The exact duration is set by your certification body, based on your scope, headcount, sites and the risks involved.

Yes. Surveillance auditors check that your internal audit programme ran as planned since the last visit and that a management review was held. If you cover the ISMS in parts across the year, they expect the parts scheduled for that period to be done and any findings handled through corrective action.

Yes. An accredited certificate can usually be transferred to another accredited certification body, which reviews your current certificate, recent audit reports and any open nonconformities before taking you on. Confirm with the new body how it will handle your existing cycle and the timing of your next surveillance audit.
Hi! I'm your AI Assistant 💬