Security

Real offensive depth

Testing and defence led by a published security researcher with five CVEs, including a CVSS 9.1 Mirai botnet kill-switch.

All security →
Compliance

Audit-ready, fixed scope

SOC 2, ISO, CPCSC, and the Canadian privacy stack, run end to end with an independent auditor.

All frameworks →
Resources

Learn the space

Original research, free tools, and plain-language guides on security and compliance, from a published security researcher.

Read the blog →
Security leadership

Security Leadership for Fundraising

From $3,000/mo CAD · scoped to you

Raising a round or getting acquired means someone technical is going to dig into your security and engineering. We provide the leadership to run that gauntlet, combining fractional CISO coverage with technical due-diligence support so the diligence findings help your valuation instead of hurting it.

The person in the seat has five published CVEs and has run a SOC 2 Type II end to end in-house, 76 controls with zero exceptions: the programme.
Book a discovery call See pricing

Built for teams that...

  • Founders in or approaching a funding round
  • Companies heading into an acquisition or strategic investment
  • Teams that got a diligence request list and don’t have a senior owner for it
  • Startups that want to look buttoned-up to sophisticated investors

What we do

  • A named security leader to own the security and technical diligence workstream
  • Preparation of the security, architecture, and technical documentation diligence teams ask for
  • A light technical due-diligence pass on your own stack to surface issues before the other side does
  • Direct support answering investor and acquirer security questions
  • A remediation plan for anything that would otherwise become a diligence red flag

What you walk away with

You go into diligence with your security and technical story organized, the obvious gaps already closed, and someone senior in the room to answer hard questions, so diligence builds confidence rather than eroding your terms.

Explore related work

Frequently asked questions

What exactly gets reviewed in technical diligence?

It varies by investor, but typically security posture, architecture, code and infrastructure practices, key-person risk, and scalability. We prepare your materials and pre-empt the issues a sharp diligence team will find.

Can you represent us in diligence calls?

Yes. Having a senior security leader answer the hard questions directly tends to build more confidence than a founder improvising, and it frees you to run the rest of the deal.

Should we do a self-assessment before diligence starts?

Ideally, yes. A light technical DD pass on your own stack lets you find and fix or contextualize issues on your timeline instead of reacting to them mid-deal.

How does pricing work?

It depends on deal stage, timeline, and how much documentation exists. We scope it on a call and link you to technical DD pricing rather than quoting blind.

The workspace is included, not quoted

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.

Security Leadership for Fundraising, on your timeline

Book a free 30-minute call. We’ll tell you whether it fits, what it costs, and when we can start.

Book a call

Not 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

Who is actually doing the work

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.

5
Published CVEs, including a CVSS 9.1
76
Controls taken from nothing to a passed SOC 2 Type II
Zero
Exceptions on that Type II report
75 days
Readiness window we have hit every time we have run it
20+
Penetration testing engagements delivered

Published vulnerability research

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.

A SOC 2 Type II built from nothing

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.

Recent engagements

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.