Surveillance Audit Preparation: A Plan for the Years After Certification

Surveillance audit preparation: how it differs from recertification, the records the auditor looks at, closure of previous findings, a 10-week timeline and a checklist.
Technical summary
Technology
ISO/IEC 27001:2022, ISO/IEC 17021-1, ISO/IEC 27006
Topic
The post-certification surveillance cycle
Level
Intermediate
Prerequisites
  • A valid ISO 27001 certificate
  • The previous audit report and list of open findings
In this article7 sections

The first year after ISO 27001 certification is when it becomes clear whether the ISMS really works. The project team disperses, the consultant leaves, the internal audit and management review drop off the calendar; a few weeks before the surveillance audit, a year-long gap in records is noticed. To prevent this scenario, you need to know what the auditor looks at in surveillance, how it differs from recertification, how to handle previous findings and changes, and to put the ten weeks before the audit into a plan. It’s all below.

The difference between a surveillance audit and recertification

Under ISO/IEC 17021-1, the certification cycle is three years. After initial certification, a surveillance audit is carried out at least once a calendar year except in recertification years; the first surveillance audit can’t be more than twelve months after the certification decision date. At the end of the third year, a recertification audit is carried out before the certificate’s expiry date.

Feature Surveillance audit Recertification
Purpose Verify that the system is being maintained Reconfirm the conformity and effectiveness of the system as a whole
Scope Requirements by sampling; not all clauses may be reviewed at each surveillance All requirements of the standard and the scope
Duration Under IAF MD 5, usually about one third of the initial certification time Under IAF MD 5, usually about two thirds of the initial certification time
Basis Previous audits and records for the period Performance over the whole certification cycle
Result Maintaining the certificate, scope change or suspension New three-year certificate decision

Surveillance scope looks narrow, but the auditor sets the sample. A control not reviewed at one surveillance is reviewed at the next; certification bodies plan the three-year program so that the scope and controls are sampled in a balanced way across the cycle. The assumption “they won’t look at that this year” isn’t safe. It’s a miscalculation you may come across.

Topics the auditor focuses on in surveillance

ISO/IEC 17021-1 lists the topics to be assessed at every surveillance audit; for information security management systems, ISO/IEC 27006 supplements these requirements with ISMS-specific elements. In practice, surveillance revolves around these headings:

  • Internal audit and management review: Were they done within the period, did they complete the planned scope and were their outputs followed up?
  • Nonconformities found at the previous audit: Have corrective actions been implemented, and are they effective?
  • Handling of complaints: How were external and internal complaints related to information security recorded and resolved?
  • Effectiveness in achieving objectives: Have information security objectives been measured and the results assessed?
  • Continual improvement activities: Is there progress on planned improvements?
  • Continuity of operational control: Is the risk assessment up to date, and are controls operated with records spread across the period?
  • Changes: How were changes in the organization, scope, locations, critical systems and suppliers managed?
  • Use of the certificate and logo: Are references to certification consistent with the scope?

The first two items are usually where most time is spent in surveillance. Without these two records, the rest isn’t even discussed. How to spread the internal audit program across the cycle is explained in the ISO 27001 internal audit program guide, and how to record the inputs and outputs of management review in the management review guide.

Closure evidence for previous findings

For minor nonconformities from the previous audit, the certification body has accepted your plan; at surveillance it’s verified that the plan was implemented and was effective. For each finding, the auditor usually follows this trail: finding statement → root cause analysis → actions and evidence of completion → effectiveness verification → extent check in similar areas.

Prepare a closure file for each open or closed finding. The file contains the accepted plan itself, evidence of completion for every action committed to in the plan, the effectiveness criterion and the measurement result. If a date in the plan slipped, the reason and who approved the new date should also be in the file. What’s written in the plan must be visible in practice too.

The effect of finding classes on the next audit and the risk of minor findings adding up to a major are covered in detail in the article major vs minor nonconformity.

Reporting scope and organizational changes

ISO/IEC 17021-1 requires certification bodies to require certified organizations to report, without delay, changes that may affect certification. These changes include legal status or ownership, organization and top management, address and locations, scope, and significant changes to the management system or processes. The details of the reporting obligation are in your certification contract.

Typical change triggers from an information security perspective:

  • Opening a new location or closing an in-scope location.
  • Moving the data center to the cloud or changing the main hosting provider.
  • Outsourcing IT operations or bringing them back in-house.
  • A merger, acquisition or split.
  • A change of ISMS manager or top management.

These changes may require both reporting to the certification body and updating the risk assessment, SoA and scope document within the organization. When the auditor learns of a change at surveillance, these updates are the first thing they look at. If you moved your servers to the cloud but the old server room is still in the risk register, the auditor sees it in the first hour. An unreported scope change also leads to the audit time and plan being calculated wrongly.

Pre-surveillance preparation timeline

Preparation runs throughout the cycle, not a few days before the audit. But a ten-week countdown works well for checking periodic activities all together. The timeline assumes the internal audit and management review are already completed by this point; if not, planning them is the first task.

Time to audit Activity Output
10 weeks Confirm the audit date, list and report changes Change list, reporting correspondence
9 weeks Check the previous audit report and the status of open findings Draft finding closure files
8 weeks Scan the evidence matrix for overdue and missing evidence Overdue evidence list and owners
7–6 weeks Update the risk assessment and SoA for changes Revised risk register and SoA
5 weeks Check the completeness of internal audit and management review records Comparison of program vs actual
4 weeks Compile objective and KPI measurement results Objective tracking table
3 weeks Receive the audit plan, assign process owners Session–participant mapping
2 weeks Rehearsal interviews with process owners Rehearsal notes and corrections
1 week Check access to evidence, prepare the meeting room or remote connection Access test completed

The evidence scan in week eight is the step in the timeline that turns up the most work: an overdue quarterly review or a restore test that wasn’t done shows up here and can still be made up within the period. If it’s spotted in the last week, it can’t. Rehearsal interviews show the gaps on the human side of the audit; for their content, see the article preparing for auditor interviews.

Surveillance checklist

The quickest way to measure the “we got certified and the system stopped” risk is to check that the records below for the last twelve months exist, and their dates. If all the records are piled into the few weeks before the audit, the system wasn’t operated continuously. The auditor looks at the dates.

  • The internal audit program and the audit reports carried out within the period.
  • The management review meeting record, showing all inputs listed in the standard were addressed and decisions were followed up.
  • Corrective action records for previous certification and internal audit findings, together with effectiveness verification.
  • The current risk assessment and the progress status of the risk treatment plan.
  • The SoA and scope document, with revision dates consistent with changes.
  • Measurement results for information security objectives.
  • Periodic control records: access reviews, restore tests, vulnerability scans, supplier assessments.
  • Incident records and lessons learned from incidents.
  • Awareness training records, including those who joined during the period.
  • Change notifications made to the certification body.
  • Consistency of certificate and logo use on the website, in proposals and presentations with the scope.

Items missing from the list show that a structure for ensuring continuity over the rest of the cycle is missing. Completing a missing record is a one-off job; building the missing structure is the real job. For details of the initial certification process, see the article the Stage 1 and Stage 2 audit process. For organizations without internal resources to carry ISMS responsibility in the post-certification period, our outsourced ISMS responsibility and ongoing ISO 27001 consulting service, and for comprehensive pre-audit preparation, our ISO 27001 certification audit preparation service support this cycle. The official source for surveillance and recertification rules is the ISO/IEC 17021-1 standard.

Frequently asked questions

How often is an ISO 27001 surveillance audit carried out?

Under ISO/IEC 17021-1, at least once a calendar year except in recertification years. The first surveillance audit can’t be more than twelve months after the certification decision date. The exact dates are in the certification body’s three-year audit program.

Are all Annex A controls reviewed in a surveillance audit?

Not every control may be reviewed at every surveillance; the auditor takes a sample. However, the certification body plans the three-year program so that the scope and controls are sampled in a balanced way across the cycle. That’s why all controls need to have been operated throughout the period.

What happens if a major nonconformity is found at a surveillance audit?

The certification body requires corrections and corrective actions to be implemented and verified within a set time. If this isn’t achieved, the certificate may be suspended. Times and the verification method are set by the certification body’s rules.

Can we hold a scope change until the surveillance audit?

We don’t recommend it. Changes that may affect certification are expected to be reported to the certification body without delay, and this obligation is in the contract. An unreported change leads to the audit time and plan being calculated wrongly.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles