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 →
AI security & governance

LLM Red Teaming

From $4,000 CAD · scoped to you

If you ship an LLM or agent application, attackers are going to probe it with prompt injection, jailbreaks, and tool-abuse tricks. We red-team it first. Delivered with our partner Lorikeet Security, this is hands-on adversarial testing of how your model, prompts, and tools behave under attack.

Delivered by a researcher with five published CVEs, including a CVSS 9.1 in the Mirai botnet, across 20+ penetration testing engagements.

Comparing providers? See how the Canadian penetration testing market compares.

Book a discovery call See pricing

Built for teams that...

  • Teams shipping LLM-powered products or autonomous agents
  • Companies whose AI features can call tools, touch data, or take actions
  • Security and product leaders who want assurance before or after launch
  • Anyone whose customers are asking how the AI holds up under attack

What we do

  • Adversarial testing for prompt injection, both direct and indirect
  • Jailbreak and guardrail-bypass attempts against your system prompts and policies
  • Tool-abuse and excessive-agency testing where the model can call functions or act
  • Data-exfiltration and sensitive-information-disclosure testing
  • A findings report with severity, reproduction steps, and concrete fixes, delivered with Lorikeet Security

What you walk away with

You learn how your LLM or agent actually behaves under adversarial pressure (where it leaks, gets jailbroken, or misuses its tools), with a prioritized, reproducible list of fixes before an attacker finds the same holes.

Explore related work

Frequently asked questions

What is the difference between LLM red teaming and AI pen testing?

Red teaming is open-ended adversarial testing focused on how the model and its guardrails behave: injection, jailbreaks, tool abuse. AI penetration testing is more structured, typically mapped against the OWASP LLM Top 10. Many clients do both.

Who actually performs the testing?

It is delivered with our partner Lorikeet Security, who specialize in offensive and adversarial testing including LLM red teaming. You get that offensive depth plus our governance and remediation context.

Can you test agents that call tools or take actions?

Yes. Tool abuse and excessive agency are core to the test. Where a model can invoke functions or act on data, that is exactly where we push hardest.

What do we get at the end?

A findings report with each issue’s severity, reproduction steps, and a concrete fix, so your team can remediate rather than just receive a score.

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.

LLM Red Teaming, 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.