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 →Credentials in a public repo. A customer reporting an exploit. Your cloud account locked out. The worst time to be looking for an incident responder is during an incident, when you are negotiating scope and rates with a stranger while the clock runs. A retainer puts the relationship, the access and the SLA in place beforehand.
When the pager goes off you call one number and someone who already knows your environment picks up inside a contracted SLA. Between incidents the retainer hours go into the readiness work that makes the next one shorter.
A contracted response SLA, 24/7 coverage, and a set number of retainer hours. The tiers run $1,000, $2,000 and $3,000 a month, differing in how fast we acknowledge and are hands-on, and how many hours are included.
They roll forward one month. They are meant for readiness work between incidents rather than being lost.
No. We run incident command so your engineers can work the technical problem instead of also managing the bridge call, the status page and the customer comms.
Yes. A tabletop is the usual first step: it tests the plan you have, and most teams have a much clearer view of which retainer tier they need afterwards.
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.