Testing and defence led by a published security researcher with six 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 →Real engagements, with the numbers from the engagement record rather than rounded-up marketing figures. Some clients are unnamed while naming permission is outstanding, which is why they are described by shape.
The compliance work itself: what was in scope, what it took, and what came out.
A venture-backed US security company with no compliance programme at all. Built in-house by Jacob as Head of Operations: 76 controls, a five-layer change-approval flow and a 60-plus asset audit across a team of 15. Passed with zero exceptions, with the platform holding 99.9% uptime throughout.
A data centre operator running three sites needed SOC 2 Type II across Security, Availability and Confidentiality alongside ISO 27001:2022 including the Climate Action Amendment. Physical and environmental controls in scope at every site, plus a datacenter platform, an AI compute platform and a self-hosted collaboration stack.
A VC-backed Ontario medtech company putting clinical AI in front of practitioners. Gap analysis, an 84-item evidence programme, and the questions health buyers ask that SOC 2 itself never will.
The parts of a compliance programme nobody publishes: what auditors charge, why their quotes differ, and what tooling is genuinely worth.
The firm revised its number once the client's readiness position was set out and a prep firm was confirmed. Less uncertainty to price, so a smaller estimate.
Four firms, one identical scope. What actually drives a spread that size, and why the preparation spend is the cheaper half of the decision.
The client had priced a compliance automation subscription at five figures a year. They ran the whole programme in our workspace instead, and kept the evidence afterwards.
On the numbers. Everything here comes from the engagement record rather than from an estimate. Where a client is unnamed, naming permission is still outstanding rather than the engagement being hypothetical. We do not publish another firm's audit quotes, so audit pricing is described by what drives it and by the differences we saw. If you want the detail behind any of these, ask us.
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.
Six published CVEs, of which two show the range. CVE-2024-45163 (CVSS 9.1) is a flaw in the Mirai botnet itself, and it handed defenders a way to shut down attacker infrastructure. CVE-2026-42626, issued through MITRE, is a denial-of-service flaw in HP ENVY 5000 series printers: the raw printing port enforces no connection timeout and no session limit, so one unauthenticated device on the same network can hold the printer offline until somebody physically restarts it.
That second one is the reason this belongs on a compliance page. An asset nobody thinks of as a computer, sitting on a flat network, taken down by a device that never had to authenticate. Auditors ask how controls fail. Finding out first-hand is what separates a policy that reads well from one that holds up when somebody asks for the evidence behind it.
Before founding traztech, Jacob was Head of Operations at Humera, a venture-backed US security company whose bot-detection platform sits in the request path of its customers' applications, and he built its compliance programme in-house: no report, no policies, no documented controls at the start. It ended in a Type II attestation across 76 controls with zero exceptions, on a team of 15, having inventoried 60-plus assets and put a five-stage change-approval flow in front of production.
The platform stayed at 99.9% uptime and sub-100ms latency throughout, which is the part most readiness projects get wrong: controls are easy to design and hard to add to a system people are already depending on. That programme is why we sell fixed windows rather than open-ended retainers.
For a Waterloo data centre operator we scoped and assessed SOC 2 Type II (Security, Availability and Confidentiality) against ISO 27001:2022 including the Climate Action Amendment, run together rather than one after the other. Scope covered the production campus, a datacenter platform, an AI compute platform and a self-hosted collaboration stack, written 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.
Before you go
A few short notes on how these programmes actually run, including what auditors accept as evidence. Unsubscribe in one click, and replies reach me directly.
From Jacob Masse, founder of traztech. No spam, unsubscribe in one click.