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 →Most teams have an incident response plan nobody has ever run. The first time you find out whether it works should not be the morning it matters. We facilitate a realistic scenario against your actual stack, walk your people through detection, containment, comms and recovery, and write up where it broke.
You leave with a plan that has actually been run once, a written record for whoever is asking, and a short list of the things that would have gone wrong. It is the cheapest evidence of incident readiness you can buy, and it doubles as SOC 2 and ISO 27001 evidence.
The exercise itself is 3 to 4 hours, run as a half day. The after-action report follows within a week.
The people who would really be involved: engineering, an exec who can make a call, and whoever owns legal and customer comms. A tabletop with only engineers in it tests the wrong half of the problem.
It provides the evidence those frameworks look for around incident response testing. The after-action report is written so it can go straight into an evidence request.
That is the useful outcome. A tabletop where nothing breaks tells you nothing you did not already believe. The gaps go in the report with a remediation order.
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.