Your auditor will pull a sample, and you don't know which records he'll pick. I pull them first, the way he will, and you get the findings in writing while there's still time to do something about them.
Find the failures before your auditor does, and the report that could have ended your career becomes the one that proves you saw it coming.
The next few minutes on this page cover three things your auditor knows that your GRC dashboard doesn't: how he picks the records he tests, how long he waits before he writes something down, and how three small slips become one major. They're useful this afternoon, whether or not you ever buy anything from me.
Many firms find the year after certification goes the same way. The certificate arrives, the business gets back to its day job, and the GRC platform keeps showing green. Every control is in place, and every task has been ticked.
month 3 post-certification is when evidence collection quietly stops and everyone scrambles before the surveillance audit.Posted by an ISMS manager on a practitioners' forum
Then the auditor asks for the record behind one of those ticks, the access review for last quarter, say, and the story underneath turns out to be different. The control was in place. The evidence it was meant to produce wasn't being gathered, or was being gathered in a way that proves nothing.
The dashboard measured what it was built to measure, which is that the control exists. The auditor measures something else: whether it ran.
A surveillance visit isn't a review of your whole system. It's a sample. ISO 19011, the guidance auditors work to, is built around sampling, because no auditor can check everything in a day or two. Last year the auditor pulled a handful of records, and those records passed.
This year he'll pull different ones, and you don't know which. Last year's pass told you a great deal about last year's sample, and very little about this year's.
The second thing he knowsIf the record behind a control can't be produced in roughly ten minutes, he writes it down. A record that exists somewhere but takes half an hour to find scores the same as a record that doesn't exist.
So this checksheet is scored the way he scores. Mark a line Y only if you could put the dated record on screen while reading the line. A Y you'd have to go and confirm is an N for today.
Your system is in good order. The Surveillance Probe is the right test for you, and it may simply confirm what you already know. If it finds more, the £497 comes off the Full Diagnostic.
Start the Probe, £497 →Those lines are where the auditor's ten minutes run out. And these fifteen lines are a fraction of what he can ask in a day. The Full Premortem Diagnostic tests the rest, all 126 checks, before he does.
Start the Full Diagnostic, £1,950 →Nothing you tick here is sent anywhere or stored. It stays in your browser.
Practitioners often say it's hard to fail a surveillance audit, and they're right that certification bodies would rather raise findings than withdraw a certificate. But nobody has to fail for this to hurt, because one major nonconformity starts a clock.
Majors don't only come from one big failure, either. ISO/IEC 17021-1, the standard certification bodies themselves work to, says that "a number of minor nonconformities associated with the same requirement or issue could demonstrate a systemic failure and thus constitute a major nonconformity." Three small slips in access control evidence can be written up as one major.
Deadlines vary between certification bodies, so read these as examples of how it runs, not your exact timetable.
If things go sideways it's management and the security officer answering for it.Posted by a practitioner on a practitioners' forum
The GRC platform. It records that a control exists and that a task was ticked. It doesn't pull the record an auditor would pull and ask whether it proves the control ran. One ISMS lead, writing after an audit, said his team had trusted their tool too much.
Your own internal audit. Clause 9.2 requires the audit to be objective and impartial, which is hard to achieve on a system you built. One practitioner described a predecessor who drew a major nonconformity for auditing his own implementation.
The consultant who helped build it. He checks it the way he built it, clause by clause, confirming the design. And his readiness review usually ends in a quote for the fixes, which is a reason, however honest he is, to find exactly what he can sell.
An AI chatbot. It can tell you what the standard requires. It can't sample your records, because it has never seen them.
Each of these tells you whether the system was built properly. The auditor asks whether it's still running.
| Consultant readiness review | GRC platform | Internal audit | Audit Premortem | |
|---|---|---|---|---|
| Who checks | Often the people who built it | Software | A colleague, or someone the company pays | An outside engineer with no stake in the answer |
| What's tested | That the design and documents are right | That tasks were ticked | Whatever the programme lists | Dated records, produced inside ten minutes |
| Order | Clause by clause | Control list | The programme | The order systems break, worst first |
| On a break | Noted, then quoted for | Stays green until someone notices | Often softened | Sample expanded: slip or system? |
| What happens next | A remediation proposal | A renewal | A report to the people audited | Findings only. I sell no fixes. |
| Typical UK price | £1,950 to £5,500 | Annual subscription | Staff time | £497 or £1,950, fixed |
Readiness prices from published UK consultancy rates (Goldline, Collevo, Integral, Romano). UK consultant day rates run £700 to £1,000.
Found 60 days out, written up by an independent reviewer, and put in front of the director with time to act, it's an ISMS lead doing exactly what the role exists for. Found by the auditor in the closing meeting, with the director in the room, it's a finding against the system you own.
The National Cyber Security Centre's Board Toolkit asks boards a direct question: "Has an independent cyber security risk assessment been carried out?" Raising your own gaps with independent evidence is the answer that question expects. It's escalation, and escalation is the job.
My strategy was use someone with good LA experience, assess us in the most stringent possible terms… no surprises.Posted by an in-house ISMS owner on a practitioners' forum
I couldn't find anyone else selling a check that does all five, which is why I built one.
I spent my career in regulated, high-transaction environments, where the job was to find what would break before it broke in production, and to be the one called when it did. A surveillance audit is the same thing under a different name: a production test of your ISMS, on a date you don't control, by someone whose job is to find the weak point.
Most checks walk the standard from the top: clause 4, clause 5, clause 6, then the controls. That confirms the system was designed properly. But systems don't fail in clause order. They fail where a job needs doing every month and quietly stops: the access review, the risk register, the management review. So I start at the entry points where certified systems most often decay, and I test the records, not the documents.
Why it starts where it does: NQA has written that more nonconformities are raised against internal auditing than any other clause of ISO 27001 (the 2013 edition; the clause hasn't got easier). A 2018 DNV study of more than 1,700 certified companies found 40% had at least one nonconformity, and 27% didn't meet the risk assessment requirements of clause 6.1.2. These were companies that were already certified.
Below is an extract from a worked example of a Full Diagnostic report. The company and its results are invented; the format, grading and language are exactly what you'd receive.
| # | Check | Area | Likely grade | Finding |
|---|---|---|---|---|
| 1 | MR-01 | Management review | Major | Minutes do not evidence enforceable outputs: decisions, actions, owners, dates. |
| 2 | MR-03 | Management review | Major | Review actions cannot be evidenced as tracked to closure (4 of 6 open). |
| 3 | IA-05 | Internal audit | Major | Access control audited by the person who operates the control; independence not demonstrated (9.2). |
| 4 | CLD-03 | Cloud services | Major | One of four tenant admins has MFA disabled; no dated admin review this quarter. |
Illustrative example, not a client finding.
No reviewer can predict every question an auditor might ask, and I won't pretend to. The Full Diagnostic tests every clause and every Annex A control, in the order systems most often fail. An auditor can still come at a requirement from an angle I didn't, and find something there. Anyone who tells you otherwise is selling a guarantee nobody can honour.
What you can rely on is this. Every part of your system will have been tested, pass or fail, against the evidence an auditor asks for, and the places that most often fail will have been tested hardest. That leaves very little for the day of the audit to surprise you with.
Picture the opening meeting. The auditor sets out his plan for the day, and you already know which records sit in the places he's likely to sample, because they were sampled weeks ago. The access review he asks for is dated, signed and on screen before he's finished asking. The gap that would have surfaced in the closing meeting was raised by you, in writing, a month ago, and the director signed off the fix.
Whatever the auditor finds on the day, the record shows you looked first.
If you scrolled down expecting a wall of five-star reviews, there isn't one. This service is new, so there are none yet. And if there were, you'd be right not to believe them. A page of glowing testimonials takes about a minute to generate now, and most people in security learned to scroll past them a long time ago.
So here's what you can check for yourself instead:
Where clients agree to it, anonymised results from real engagements will appear here: what was tested, what failed, and the grade it was likely to draw. Numbers, not adjectives.
I learned the reason for this in deployment work. You don't rely on people being careful on the night. You build the outcome into the structure, so it happens whatever anyone's mood. Outcomes are engineered. A review is an opinion. A dated record is evidence, which is the whole point of this service.
I don't want your personal data, and the reason is simple: a reviewer who never holds it can never leak it, lose it, or be asked to hand it over. So before anything leaves your network, you sanitise it to a standard your own DPO would sign off.
Sanitised evidence is enough, for the same reason your auditor works the way he does: he tests whether a control operates and whether the record proves it, not whose name is on it. If evidence fails once the names are gone, it was going to fail with them in.
If you miss something, you're still covered. I sign an NDA before you send anything. Your evidence is permanently deleted within 24 hours of your report being delivered, with no copies kept in backups or version history. I've worked with production access to databases carrying billions in transactions, where one lapse would have ended careers, including mine. A sanitised evidence pack is a much smaller thing to be trusted with.
Report within two weeks of your evidence arriving
Who it's for: you're inside your audit window and would rather see everything now; you've had a finding before or have an open nonconformity; it's a recertification year; or you know something's wrong and need written evidence your director will act on.
Start the Full Diagnostic, £1,950 →Report within 72 hours of your evidence arriving
If you're certain your system would survive any sample an auditor could take, you don't need the Full Diagnostic. Some people are right about that. The Probe exists to find out cheaply whether you're one of them.
Within 30 days of your report, send me the new evidence for up to five of your failed checks, and I'll test them again, pass or fail, the same way: ten-minute rule, silence test and all. You get a written re-test note you can file alongside the report.
That matters more than it sounds. A remediation seller has every reason to tell you his fix worked. I didn't make the fix and earn nothing from it, so when the re-test says pass, it means pass. It costs me a day of work I don't charge for. It gives you the one thing you can't get from the people doing the repairs: an independent check that the gap is actually closed, while there's still time before the visit.
Your report arrives within two weeks of your evidence being confirmed complete (72 hours for the Probe), or your fee comes back in full, and you keep the report.
And until you upload evidence, you can cancel for a full refund at any time, for any reason. The only risk you take is ten minutes reading your evidence checklist.
UK consultant day rates run £700 to £1,000, so even five days of senior review bought that way would cost £3,500 to £5,000. Fixed-price readiness work typically runs £1,950 to £5,500, and usually comes with a remediation quote attached. The Full Diagnostic sits at the bottom of that range and sells you nothing afterwards. The Probe costs less than one consultant day.
Set either against the other side of the ledger: a ten-day response window, a special visit, a suspension customers can see on a public directory, and the conversation about who owned the ISMS.
Paying for it. £497 sits inside most company card limits, so you can commission the Probe today without a purchase order. If your company needs a purchase order or a formal invoice for the Full Diagnostic, you'll get one. You can also commission either in your own name; I don't need to know the organisation, and nobody needs to know you checked until you choose to raise what I find.
Why I take three Full Diagnostics a month. Each gets two weeks of my own attention, and I don't hand the work to anyone else. When this month's three are taken, the next start date moves to the following month, which matters if your audit date doesn't.
Payment details arrive by email when you submit. Nothing is charged until you pay.
Most policies restrict sharing personal data, credentials and customer information, which is exactly what you remove before uploading. What's left is sanitised proof that controls ran: dated records with roles instead of names. It's covered by an NDA signed before anything moves, and deleted within 24 hours of your report. If your policy still forbids it, commission it in your own name and show your director the sanitising rules first; most find they've been asked for less than an auditor sees.
No. I don't do remediation, at any price. That's the point: I earn nothing from what I find, so I've no reason to find more than is there, and no reason to soften what is. The only thing I offer afterwards is more testing, never fixing.
Good, keep them. They build, maintain and check that the system is designed properly. I test whether it's still running, independently, the way the certification auditor will. Many people hand my findings straight to their consultant, who then knows exactly where to start.
Never. The report goes to you alone, and I never contact your certification body, auditors, customers or consultants. Whether, when and with whom you share it is entirely your decision.
Then you have dated, independent proof that your system works, and a coverage appendix showing every clause and control that was tested. That's worth having in the opening meeting, and in any conversation afterwards about whether the ISMS was looked after.
It's possible, and I've said so above. What isn't possible is that he finds the system untested. Every clause and control will have been checked against the evidence he asks for, and the places that most often fail checked hardest.
A few hours: gathering the records on your checklist, which should already exist, and sanitising them. If gathering them takes much longer than that, it tells us something on its own.
If it's under three weeks, start with the Probe: 72 hours gives you time to act on what it finds. If you have three weeks or more, the Full Diagnostic still leaves you time to escalate, fix and use the free re-test before the visit.
Brian Colborne, a deployment engineer who spent twenty years on live, high-transaction systems in regulated environments, and was the one called when they broke. LinkedIn suspended my account during a verification process I couldn't complete, and I won't rebuild on a platform that can remove years of work overnight. The full story is here.
A call produces a conversation, and a conversation is the one thing an auditor can't accept as evidence. Everything I need is in your records, and everything you need is in my report. Questions are answered in writing, which also means you have them on file.
That's a different job: testing whether your corrective actions will satisfy the certification body. Start here.
One is on last year's sample, finding out in the closing meeting what this year's turned up. The other is finding out now, while it's still your finding, while there's still time to fix it, and while raising it still counts in your favour.
The only real deadline is your audit date. Every week closer to it is a week less to fix what I find.
On time or your money back. Full refund any time before you upload evidence.
If you want to know what your auditor will find, start there. If you don't, close the page. Either is fine by me.
Questions go by WhatsApp message to +44 7934 474424. It's a message line, not a phone line, so please don't ring it.
Brian Colborne
P.S. Not sure which to choose? Go back to the checksheet. Every line Y with the record in hand means the Probe. Anything else means the Full Diagnostic, which comes with the Fix Re-Test, so you find out not only what's broken but whether your fixes hold, before the auditor checks.
P.P.S. The gap is the same whether you find it or the auditor does. What changes is whose report it ends up in, and that's decided by who gets there first. Be the one who raised it.
