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, 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 companies have some version of a continuity plan. Almost none have evidence it works, and that is the part auditors ask about. We run the impact analysis, write a plan somebody can follow at three in the morning, then exercise it and document what actually happened.
You end up knowing whether you can actually recover, in how long, and losing how much data. Where you cannot, you have a dated list of what to fix and who owns it. The test record sits on your completion record, so when an auditor asks when you last tested, the answer is a date and a document.
An incident response tabletop rehearses how you respond to a security incident: who is called, what is said, how it is contained. Continuity testing asks a different question: if this system is gone, can you keep operating and get it back inside the time you promised. Many clients run both, and the same people usually attend.
No, and the first exercise usually should not be. A tabletop proves people know the plan, a component failover proves one dependency, a full restore proves the whole thing. We pick the level that matches what you need to evidence and what your environment can safely take.
ISO 27001 A.5.29, A.5.30 and A.8.13, and SOC 2 A1.2 and A1.3. All of them want the same two things: a plan, and proof it has been tested.
At least annually, and at least once inside a SOC 2 observation window. If your architecture changes significantly, test again rather than waiting for the anniversary.
The price above covers the work. It also covers where the work lives, which most buyers are quoted separately as an annual platform subscription.
| traztech Workspace | Other GRC platforms | |
|---|---|---|
| Licence cost | $0. Free forever, no card, no paid tier | $7,500 to $50,000 a year, on an annual contract |
| Control library, evidence register, policy templates, risk register, vendor questionnaires, readiness scoring | Included | Included |
| What it costs inside an engagement with us | $0. You need a workspace either way | Unchanged. The subscription sits on top of the fee |
| What it does to your audit quote | $11,000 off a five-figure quote on one engagement, for a documented readiness position | Nothing. The audit firm prices your readiness, not your tooling |
Pricing in the right column is what compliance automation platforms are publicly reported to charge; none of them publish a number, so treat it as a range rather than a quote. The $11,000 came off the audit firm's own number once the readiness position was documented (the engagement). Where a paid platform is the better buy, and the fuller comparison, is on the Workspace page.
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 →Free PDFs, no card
SOC 2 readiness, ISO 27001 gaps, incident response and vendor security, as PDFs you can print or forward. Free, no card.
From Jacob Masse, principal of traztech. No spam, unsubscribe in one click.
Track record
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.