Seven Mistakes That Turn an ISO 27001 Surveillance Audit Into a Nonconformity
Most ISO 27001 findings come from programs that drifted after the certificate arrived, not from controls that were missing at the start. Here are seven drift patterns auditors catch, and the evidence that fixes each one.
What a surveillance audit tests once the certificate is on the wall
If your certificate is a year or two old, nobody is asking anymore whether the ISMS was built properly. The initial audit answered that. The question now is whether it still runs when nobody is preparing for an auditor, and that's what an ISO 27001 surveillance audit checks. Certification bodies typically run at least one surveillance visit each year between initial certification and recertification. Each visit covers the core clauses (4 to 10) and a rotating sample of Annex A controls.
Certificates are now issued against ISO/IEC 27001:2022, since the transition period for older certificates has ended. Auditors therefore look at clause 6.3 (planning of changes) and at whether you've considered climate change as a possible issue in your context, following the 2024 amendment. Programs that carried their 2013-era habits straight across are the ones getting caught.
How a finding is graded decides what it costs you:
| Finding | Typical trigger | Typical consequence |
|---|---|---|
| Major nonconformity | A requirement is missing or has broken down entirely, or there's serious doubt the ISMS achieves its outcomes | Corrective action verified within a window set by the certification body, often a few months. You may need a paid follow-up visit, and the certificate can be suspended |
| Minor nonconformity | An isolated lapse in a requirement that otherwise works | A corrective action plan, checked at the next visit |
| Opportunity for improvement | The auditor sees a weakness but no requirement is breached | No mandatory action |
A follow-up auditor-day typically costs $1,000 to $2,500 in North America, the UK and Western Europe, and often less in India, Southeast Asia and Latin America. Treat these as typical 2026 ranges that vary by contract, and confirm with your certification body. The bigger cost is the conversation with customers who ask why your certificate is suspended. The seven mistakes below are the most common ways a program drifts into an ISO 27001 major nonconformity.
Risk registers and Statements of Applicability frozen at certification
Mistake one: a risk register nobody has touched since the initial audit
Clause 8.2 requires risk assessments at planned intervals and when significant changes occur. Auditors compare the register's last-modified dates with what they already know about you: the CRM migration you mentioned, the new engineering team, the second cloud region. Warning signs include identical residual scores year on year, risk owners who have left, and no risks linked to systems adopted since certification.
What to do instead: run a documented annual reassessment and add event triggers to change management. A new supplier handling personal data, a new hosting region or a major product release should each open a risk review ticket. Keep a record showing risk owners formally accepted residual risk, since clause 6.1.3 expects that approval.
Mistake two: a Statement of Applicability describing controls you no longer run
A common case: the SoA says control 8.16 (monitoring activities) is implemented, but the SIEM contract lapsed last spring. Another: control 5.23 (cloud services) is marked not applicable, though half your stack is now SaaS. Auditors use the SoA as their sampling map, so mismatches surface fast.
What to do instead: reconcile the SoA against the risk treatment plan every quarter. For each included control, name an owner and the record that proves it operates.
Internal audits run by the people who own the controls
Clause 9.2 requires internal auditors to be chosen so the audit is objective and impartial. In companies with 30 to 200 staff, the usual failure is that the ISMS manager audits the ISMS they wrote, and the IT lead audits the access control they administer. The standard doesn't demand an outside auditor. It does bar anyone from auditing their own work, and certification bodies increasingly write findings when the auditor and the interviewee are the same person.
Other warning signs in an ISO 27001 internal audit:
- An Annex A checklist with no coverage of clauses 4 to 10.
- The whole year's audit squeezed into one day, two weeks before the surveillance visit.
- Findings that never reach the corrective action log.
- No audit programme showing the full ISMS is covered across the three-year cycle.
You have three realistic ways to fix independence:
| Option | Indicative cost (typical 2026 ranges) | Best fit |
|---|---|---|
| Train a staff member from another department | $800 to $2,000 for an internal or lead auditor course, plus their time | 100+ staff with someone credible outside IT and security |
| Outsourced internal auditor | $3,000 to $15,000 per year, depending on scope, sites and region | Under about 100 staff, or anywhere independence is hard to show |
| Existing group internal audit function | Internal cost; may need ISO 27001 training | Large enterprises and subsidiaries of groups |
For most companies under 100 people, outsourcing is the better fit. One contract settles independence, and you get a second set of eyes that hasn't gotten used to your workarounds.
Management reviews that exist only as a calendar invite
A management review skipped for a whole year is one of the most reliable routes to a major nonconformity, because a required activity simply didn't happen. More common is a review that took place but can't be shown to have covered what clause 9.3 requires: a 20-minute slot inside a leadership meeting, or a slide deck emailed to executives with no record anyone discussed it.
Clause 9.3 lists the inputs: status of actions from previous reviews, changes in internal and external issues, and changes in the needs and expectations of interested parties. It also covers performance feedback (nonconformities, monitoring results, audit results, objectives), feedback from interested parties, risk assessment results and treatment status, and opportunities for improvement. The outputs must include decisions on improvements and on any changes to the ISMS.
What to do instead:
- Use a fixed agenda that follows the clause 9.3 inputs line by line, with climate change as a standing item under context.
- Get at least one executive with budget authority to attend. Clause 5.1 expects top management to lead, not just receive a summary.
- Write minutes that record decisions, owners and dates, not just discussion.
- If one long meeting isn't realistic, split the ISO 27001 management review across quarterly sessions and keep a tracker showing every input was covered within the year.
Scope changes nobody told the certification body about
Your certificate's scope statement is a public claim that customers rely on in procurement. When the business changes and the scope doesn't, the certificate stops matching what you do, and you may breach your certification contract, which usually requires reporting significant changes.
Typical unreported changes:
- An acquisition whose systems now share your identity provider.
- A new support or development hub in Manila, Bogotá, Pune or Kraków.
- A move from on-premises hosting to AWS, Azure or Google Cloud.
- A new product line that sales teams start describing as "ISO 27001 certified."
Scope changes also shift which laws apply. A new hub handling EU customer data brings GDPR transfer obligations into the ISMS context. Processing Indian personal data brings in the DPDP Act, and expanding into the Gulf or Brazil adds local data-protection laws to your interested-party requirements. Clause 4.2 expects you to capture those, and clause 6.3 expects changes to be planned rather than discovered.
What to do instead: tell the certification body in writing when the change happens, not at the next visit. Then decide deliberately whether to extend the scope or formally exclude the new area, with its interfaces documented. Extending usually adds audit days and cost, so budget for it. It still costs less than a special audit, or a customer finding the gap during due diligence.
Stale corrective actions, missing evidence and a 90-day fix plan
Mistake six: last year's findings closed on paper only
Clause 10.2 requires you to establish why a nonconformity happened and act to stop it recurring. "Retrained staff" is rarely a root cause. If an auditor sees the same minor nonconformity at two visits running, many will grade it major. What to do instead: record the root cause, the action, and an effectiveness check done some weeks after implementation, before you mark the item closed.
Mistake seven: policies without operating records
Say a 60-person company's policy calls for quarterly access reviews, and it can produce evidence for two of the four. Supplier assessments stopped after onboarding, and the clause 9.1 metrics were defined but never measured. Every control exists as written policy, yet the records show it isn't operating. GRC platforms such as Vanta, Drata, Secureframe, ServiceNow or OneTrust can automate evidence collection. They won't fix a control with no owner.
If your next visit is about 90 days away, work in this order:
- Days 1 to 15: check whether a management review, an internal audit and a risk reassessment have each happened in the last 12 months.
- Days 15 to 45: run or commission an independent internal audit covering clauses 4 to 10 and the Annex A controls due for sampling.
- Days 30 to 60: reconcile the SoA, the risk register and the scope statement against the business as it is today. Report any scope changes to the certification body.
- Days 45 to 75: close prior corrective actions with root-cause and effectiveness evidence, and fill gaps in operating records.
- Days 75 to 90: hold the management review, with the internal audit results as an input.
The decision rule: if any of those three core activities is missing from the past year, fix it before you touch any Annex A gap. An absent core activity is the finding most likely to be graded major, and the same drift found at recertification is harder to recover from.
Quick answers
How often do ISO 27001 surveillance audits happen?
Typically at least once per year in the two years between initial certification and recertification. Some certification bodies split the work into two smaller visits a year for larger or multi-site organizations. The three-year cycle ends with a full recertification audit. Confirm the schedule in your certification contract.
What happens if we get a major nonconformity?
You'll usually need to fix the problem and show a verified corrective action within a window set by your certification body, often a few months. That may involve a paid follow-up visit. If it isn't resolved in time, the certificate can be suspended. Check the exact timelines in your contract.
Can our ISMS manager carry out the internal audit?
They can audit areas they don't own or run, but not their own work, because clause 9.2 requires objectivity and impartiality. In small teams that rule usually leaves the ISMS manager unable to audit the core clauses they designed. Many companies under 100 staff outsource the internal audit for this reason.
Do we need to tell our certification body about an acquisition or new office?
Generally yes. Most certification contracts require you to report significant changes to scope, sites, ownership or processes. The certification body may change audit days or schedule an extra visit. Ask a qualified adviser or your certification body how a specific change affects your certificate.
Is a surveillance audit cheaper than recertification?
Usually. A surveillance audit normally uses fewer audit days than recertification because it samples instead of re-examining the whole ISMS. For a small, single-site organization, typical 2026 ranges are roughly $3,000 to $12,000 per visit, varying widely by region, scope and certification body. Get quotes directly.
Written by the Breachnodeops editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.