Testing and defence led by a published security researcher with five CVEs, including a CVSS 9.1 Mirai botnet kill-switch.
All security →SOC 2, ISO, CPCSC, and the Canadian privacy stack, run end to end with an independent auditor.
All frameworks →Original research, free tools, and plain-language guides on security and compliance, from a published security researcher.
Read the blog →An audit that stops partway through is the most expensive outcome in compliance, and it is also the most recoverable, because you now have something most first-time candidates do not: a professional opinion, in writing, about exactly what is missing. The mistake is treating that as a punch list. The findings are symptoms, and remediating them one by one is how companies re-enter fieldwork and stall a second time.
You re-enter fieldwork once, with the evidence in the form your firm has already told you it needs, and the cause of the original finding closed rather than papered over.
Usually yes, and usually you should. They know the environment, they have already done the scoping work, and re-entering with a firm that understands what changed is faster than starting a relationship over. The exception is where the relationship has broken down or the original scoping was the problem. We will tell you which situation you are in rather than defaulting to a switch.
It depends on where the gap sits. If a control simply was not evidenced, the window may hold. If a control was not operating for part of the period, the window covering that period cannot be repaired after the fact, and a fresh one is the honest answer. This is the first thing we determine, because everything else follows from it.
The starting point. First-time readiness begins with a gap assessment against the whole control set. Recovery begins with a professional opinion about what is already wrong, which is more specific and more misleading, because the findings are instances and the fixes have to happen at the level of the control that produced them.
The exceptions belong to the report they were written into, and that report does not change. What matters for the next one is that the period it covers is clean. Buyers who read a prior report with exceptions care about the management response and whether the same finding recurs, which is exactly why fixing the cause rather than the instance is the whole engagement.
It is scoped like any readiness engagement and quoted fixed, from the same published floor. What we will not do is price a premium for urgency. The audit firm fee for re-entering fieldwork is separate and paid to them, as always.
Book a free 30-minute call. We’ll tell you whether it fits, what it costs, and when we can start.
Book a callNot ready to scope this yet? Open a free Workspace and score yourself against the framework first. It is the same register we work from during an engagement, so nothing you do there gets thrown away.
See what the Workspace does →Track record
We are deliberately not a large firm, and we would rather show you the work than a wall of logos. Here is what is behind the advice.
Five published CVEs. CVE-2024-45163 (CVSS 9.1) is a flaw in the Mirai botnet itself, which gave defenders a way to shut down attacker infrastructure. CVE-2026-42626 takes HP ENVY 5000 printers offline from any unauthenticated device on the same network.
The printer is the one that matters on a compliance page: an asset nobody counts as a computer, on a flat network, downed by a device that never had to log in. Auditors ask how controls fail. We have found out first-hand.
At Humera, a venture-backed US security company, Jacob built the compliance programme in-house from nothing: no report, no policies, no documented controls. It ended in a Type II attestation across 76 controls with zero exceptions, on a team of 15.
The platform held 99.9% uptime throughout, which is the part most readiness projects get wrong: controls are easy to design and hard to retrofit onto a system people already depend on.
For a Waterloo data centre operator we ran SOC 2 Type II and ISO 27001:2022 together rather than one after the other, across a production campus, an AI compute platform and a self-hosted collaboration stack. Scoped so further Ontario and Quebec sites enter as they reach production. Findings delivered and remediated.
For an Ontario medtech company putting an AI clinical assistant in front of practitioners, we ran the gap analysis and built the evidence programme behind their SOC 2.