An ISO/IEC 27001 surveillance audit is a periodic assessment conducted by an accredited certification body to determine whether an organisation's Information Security Management System (ISMS) continues to meet the requirements of ISO/IEC 27001 and remains effectively implemented.
What is an ISO 27001 surveillance audit?
It takes place after an organisation achieves initial certification and forms part of the ongoing certification cycle.
The purpose is straightforward: achieving ISO 27001 certification demonstrates that an organisation's ISMS met the applicable requirements at the time of certification. Surveillance audits provide continuing independent assurance that the management system is still maintained, implemented and improved.
Unlike an initial certification audit, a surveillance audit does not normally examine every aspect of the ISMS in equal depth. Auditors use sampling and focus on selected requirements, processes, controls and areas of organisational change.
The important distinction is that ISO 27001 certification is not a one-time achievement. Your organisation must continue to demonstrate that its ISMS works throughout the certification cycle.
Where does the surveillance audit fit into the ISO 27001 certification cycle?
ISO 27001 certification generally operates on a three-year cycle, subject to continued conformity and successful surveillance and recertification activities.
There are three main stages.
1. Initial certification audit
The initial certification process consists of two stages.
Stage 1: Documentation and readiness review
The auditor evaluates the organisation's ISMS documentation, scope, understanding of applicable requirements and readiness for the Stage 2 audit.
This includes reviewing areas such as:
- ISMS scope and boundaries.
- Information security policies and objectives.
- Risk assessment methodology.
- Risk treatment approach.
- Statement of Applicability (SoA).
- Internal audit and management review arrangements.
The auditor also identifies areas requiring further attention before the organisation proceeds to Stage 2.
Stage 2: Implementation and effectiveness assessment
The auditor evaluates whether the ISMS has been implemented and is operating in accordance with ISO/IEC 27001.
This involves reviewing documented information, interviewing personnel and examining evidence of operational activities.
If the organisation satisfies the certification requirements and any outstanding nonconformities are addressed in accordance with certification rules, the certification body can make a certification decision.
2. Surveillance audits
Surveillance audits take place during the certification period to verify that the organisation continues to meet the standard.
They are conducted at least once in each calendar year, except in recertification years. The first surveillance audit normally takes place no later than 12 months after the certification decision.
Surveillance audits focus on selected areas of the ISMS, including:
- Internal audits and management reviews.
- Corrective actions from previous assessments.
- Changes to the organisation's information security risks.
- Selected controls and operational processes.
- Performance against information security objectives.
- Continued maintenance and improvement of the ISMS.
The certification body determines the audit programme and areas to be examined.
3. Recertification audit
Before the three-year certification period expires, the certification body conducts a recertification audit.
This is a more comprehensive assessment than an individual surveillance audit.
It evaluates the continuing conformity and effectiveness of the ISMS, taking account of the results of the previous certification cycle, significant changes and the organisation's overall performance.
If the organisation meets the requirements, its certification can be renewed for another certification cycle.
What does an auditor actually examine during a surveillance audit?
Although the specific audit programme varies, there are several areas organisations should expect the certification body to examine.
1. Previous audit findings and corrective actions
Auditors will review nonconformities identified during previous assessments.
They want to establish whether the organisation:
- Investigated the underlying causes.
- Implemented appropriate corrective actions.
- Retained evidence of the actions taken.
- Evaluated whether the corrective actions were effective.
For example, suppose an earlier audit identified that user access reviews were not consistently performed.
Simply introducing an access review checklist may not be sufficient. The organisation should be able to demonstrate that the process has been implemented, reviews have taken place and the original issue has been effectively addressed.
2. Internal audits
ISO/IEC 27001 requires organisations to conduct internal audits at planned intervals to determine whether their ISMS conforms to the organisation's own requirements and the requirements of the standard.
Auditors may examine:
- The internal audit programme.
- Audit scope and criteria.
- Auditor competence and impartiality.
- Audit reports and findings.
- Corrective actions and follow-up activities.
An organisation should be able to demonstrate that its internal audit programme is planned, implemented and maintained.
3. Management reviews
Management reviews demonstrate that leadership actively oversees the ISMS rather than treating information security as solely an IT responsibility.
Auditors may examine whether management has considered:
- Changes in internal and external issues.
- Changes in interested-party requirements.
- Information security performance.
- Nonconformities and corrective actions.
- Monitoring and measurement results.
- Risk assessment and treatment progress.
- Opportunities for continual improvement.
They may also examine the decisions made, assigned responsibilities and resulting actions.
4. Risk assessment and Statement of Applicability
An organisation's information security risks do not remain static.
New technologies, suppliers, business processes, threats and regulatory obligations can change the organisation's risk exposure.
Auditors may therefore examine whether the organisation has:
- Reviewed its information security risk assessment.
- Identified significant changes in its operating environment.
- Updated risk treatment decisions where necessary.
- Reviewed the Statement of Applicability.
- Maintained consistency between identified risks, selected controls and treatment decisions.
The Statement of Applicability should accurately reflect the organisation's selected controls, their implementation status and the justification for including or excluding applicable Annex A reference controls.
5. Operational controls and supporting evidence
Auditors select controls and examine evidence to determine whether the organisation has implemented and maintained them as intended.
Examples include:
- Access management: User access reviews, access approvals and termination records
- Asset management: Asset inventory and ownership records
- Vulnerability management: Vulnerability assessments, remediation records and patch reports
- Backup management: Backup schedules, monitoring records and restoration test results
- Supplier security: Supplier assessments, contractual security requirements and reviews
- Security awareness: Training records, completion reports and awareness assessments
- Incident management: Incident register, investigation records and lessons learned
- Change management: Change requests, approvals, testing and implementation records
The exact evidence depends on the organisation's ISMS scope, risk assessment, selected controls and applicable requirements.
An important point: having a policy or procedure does not, by itself, demonstrate that a control is operating effectively. Auditors generally need evidence that the process has been followed.
6. Organisational changes and continual improvement
Auditors also consider whether the ISMS remains appropriate as the organisation evolves.
Examples of changes that may require attention include:
- Opening new offices or business locations.
- Introducing new applications or cloud services.
- Outsourcing critical business processes.
- Changing key suppliers.
- Restructuring departments.
- Introducing new regulatory or contractual obligations.
The organisation should be able to demonstrate that relevant changes have been considered within its ISMS.
How long does an ISO 27001 surveillance audit take?
Surveillance audits are generally shorter than initial certification audits, but there is no universal duration applicable to every organisation.
Audit duration is determined by the certification body using applicable audit-time requirements and factors such as:
- Number of employees and effective personnel.
- Complexity of the organisation's operations.
- ISMS scope and number of locations.
- Nature of information security risks.
- Outsourced processes.
- Complexity of the technologies and services involved.
Surveillance audit time is generally lower than initial certification audit time, but the actual number of auditor days must be determined by the certification body.
Organisations should request the audit programme and schedule directly from their certification body rather than relying on a generic estimate.
What happens on the day of the audit?
A surveillance audit typically follows a structured process.
1. Opening meeting
The auditor meets relevant management representatives and ISMS personnel to confirm:
- Audit objectives and scope.
- Audit criteria.
- Audit programme and schedule.
- Key contacts and responsibilities.
- Arrangements for accessing records and personnel.
2. Document and evidence review
The auditor reviews relevant policies, procedures, records, registers and other documented information.
They may request evidence relating to previous findings, risk treatment, control implementation and management oversight.
3. Interviews with personnel
Auditors speak with relevant employees and control owners to understand how the ISMS operates in practice.
For example, an IT administrator may be asked to explain how user access is approved, reviewed and revoked.
A procurement representative may be asked how information security requirements are incorporated into supplier onboarding.
4. Sampling and control assessment
The auditor selects samples of activities, records and controls to evaluate whether requirements are being met.
For example, the auditor may select a sample of user accounts to verify that access approvals and periodic reviews were completed.
5. Closing meeting
The auditor presents the audit results, including any identified nonconformities and opportunities for improvement.
The certification body subsequently issues the formal audit report and determines the appropriate follow-up actions under its certification procedures.
What types of findings can an organisation receive?
Surveillance audits can result in different findings depending on the nature and significance of the issues identified.
Major nonconformity
- What it means: A significant failure to meet a requirement, or a situation that raises serious doubt about the ISMS's ability to achieve its intended outcomes
- Expected response: Root-cause analysis, corrective action and verification in accordance with certification-body requirements
Minor nonconformity
- What it means: An isolated failure that does not undermine the overall ability of the ISMS to achieve its intended outcomes
- Expected response: Corrective action and evidence of implementation, with follow-up as required
Opportunity for improvement
- What it means: An observation suggesting how the ISMS could be strengthened without necessarily identifying a failure to meet a requirement
- Expected response: Consideration and appropriate action by the organisation
A nonconformity is not automatically a failed certification.
However, unresolved major nonconformities can prevent a positive certification decision or lead to suspension or withdrawal of an existing certificate, depending on the applicable certification requirements.
Organisations should always follow the corrective action deadlines and instructions communicated by their certification body.
How should you prepare for an ISO 27001 surveillance audit?
Preparation should be an ongoing activity rather than a last-minute exercise.
A practical approach is to begin reviewing audit readiness approximately six to eight weeks before the scheduled assessment. This is a suggested preparation window, not an ISO-mandated deadline.
Six to eight weeks before the audit
1. Review previous audit findings
Confirm that previous nonconformities have been addressed.
Maintain records of:
- Root-cause analysis.
- Corrective action plans.
- Implementation evidence.
- Effectiveness reviews.
2. Complete your internal audit activities
Confirm that the internal audit programme has been implemented as planned.
Review outstanding findings and ensure appropriate corrective actions are being managed.
3. Conduct your management review
Ensure management has reviewed the ISMS and considered the required inputs, performance information and opportunities for improvement.
Retain the meeting records, decisions and resulting actions.
4. Review your risk assessment and Statement of Applicability
Check whether changes to your business, systems, suppliers, people or operating environment have affected your information security risks or control decisions.
Two to four weeks before the audit
5. Refresh operational evidence
Check that relevant records are current and available.
Pay particular attention to:
- User access reviews.
- Asset inventories.
- Backup and restoration testing.
- Vulnerability management.
- Supplier assessments.
- Employee awareness and training.
- Incident management.
- Change management.
6. Review policies and procedures
Confirm that applicable documents have been approved, communicated and reviewed at appropriate intervals.
7. Confirm control-owner readiness
Speak with relevant control owners to ensure they understand their responsibilities and can explain how their processes operate.
The objective is not to teach employees scripted answers. It is to ensure they understand the controls they are responsible for.
One week before the audit
8. Conduct a readiness review
Check that:
- The ISMS scope remains accurate.
- Required records are accessible.
- Previous findings have appropriate evidence.
- Relevant personnel are available.
- Audit arrangements have been confirmed.
- Outstanding issues have been identified and communicated.
A final readiness review helps identify gaps while there is still time to address them.
Why do organisations receive ISO 27001 surveillance audit findings?
Many organisations achieve initial certification but struggle to maintain the discipline required throughout the certification cycle.
Some common causes include:
Treating certification as a one-time project.
Once the certificate is issued, management attention decreases and ISMS activities become inconsistent.
Incomplete internal audits.
Internal audits are conducted to satisfy a schedule rather than to meaningfully evaluate whether the ISMS meets requirements.
Weak management oversight.
Management reviews take place, but decisions, performance evaluation and follow-up actions are poorly documented.
Evidence that does not demonstrate operation.
An organisation can produce a policy describing a process but cannot show records demonstrating that the process was followed.
Unmanaged organisational changes.
New systems, suppliers, locations and business processes are introduced without appropriately considering their impact on the ISMS.
Unclear control ownership.
Employees cannot explain their responsibilities, and management cannot establish who is accountable for ensuring controls operate as intended.
These issues often indicate weaknesses in the organisation's ongoing ISMS management rather than simply inadequate audit preparation.
How Pratesva Advisory can help
Maintaining ISO 27001 certification requires more than preparing documents before an auditor arrives. It requires an ISMS that is consistently implemented, monitored, reviewed and improved.
Pratesva Advisory supports organisations throughout their information security management and assurance journey.
Our support includes:
- ISO/IEC 27001 ISMS gap assessments.
- Internal audit support.
- Surveillance and recertification audit readiness.
- Information security risk assessments.
- Statement of Applicability reviews.
- Policy and procedure development.
- Control implementation and evidence reviews.
- Nonconformity and corrective action support.
- ISMS continual improvement.
We help organisations move beyond audit preparation towards sustainable information security management.
Preparing for an upcoming ISO 27001 surveillance audit?
Let Pratesva Advisory help you assess your readiness, identify gaps and strengthen your ISMS before your next certification assessment.



