Compliance

Phase 1, Phase 2, then keep it running

A fixed-price gap analysis, remediation through to your audit, and upkeep after it. All in a workspace you keep.

All compliance →
Security

Testing, review and leadership

Led by a published security researcher with five CVEs. A findings report, a letter of attestation for your buyers, and a retest of your fixes.

All security →
Who we help

Prove you are secure

To the people you sell to, raise from or answer to.

All industries →
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 $9,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.

Book a discovery call See pricing

Run by our own team, this is hands-on adversarial testing of how your model, prompts, and tools behave under attack.

Testing is run by our team and signed off by a Principal with five published CVEs, including a CVSS 9.1 in the Mirai botnet.

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

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

What an AI security test with us looks like

Testing against the OWASP Top 10 for LLM Applications, with tactics mapped to MITRE ATLAS, plus the surrounding web application and API. For red teaming we agree the harm categories and what counts as success at kickoff.

How every engagement starts

01

Sign the SOW

Your Statement of Work and our Terms of Business are signed by e-signature. The signed SOW is what authorises the testing. If you, your auditor or a buyer also want a testing confirmation or authorization letter, we provide one on request.

02

Ready to start

One checklist in your Workspace collects everything up front: contacts, scope, testing windows and blackouts, staging or production, test accounts (1Password share links only), our VPN IP allowlisted, and an emergency stop contact. Each item says why we need it.

03

30-minute kickoff

A Google Meet kickoff. When Ready to start comes in promptly, kickoff is usually about a week after signing.

Steps and timing

StageWhat happensTypical timing
StartSigned SOW, Ready to start (scope, windows, test accounts, our VPN IP allowlisted) and a 30-minute kickoff.Kickoff usually about a week after signing.
TestingHands-on adversarial testing in business hours by default. Every finding records the exact prompt, the time and the number of attempts, because model output varies.Usually 2 to 5 weeks, set by scope.
ReportFindings report and letter of attestation. Red teaming also reports the success rate per harm category.About 5 to 7 business days after testing ends.
RetestWe retest your fixes to Critical and High findings.Requested within 30 days of the report.

Timings are typical ranges, not promises. They depend on scope and on how quickly inputs and decisions come back.

Who does what

What we do

  • Test only inside the signed scope and windows, from TrazTech's fixed VPN IP
  • Push hardest where the model can call tools, reach data or take actions
  • Write each finding so your team can reproduce it and fix it
  • Email your technical contact within 24 hours of finding anything Critical

What you do

  • Complete the scope in Ready to start and choose staging or production
  • Allowlist our VPN IP and share test accounts as 1Password links
  • Name an emergency stop contact for each testing window
  • Fix the findings, then request the retest from your Workspace

What you do not have to do

  • Write a separate authorization letter: the signed SOW authorises the testing (if your auditor or a buyer wants one, we provide it on request)
  • Chase us for status: you get a weekly update and see findings as they are approved

What you get

  • A findings report with severity, reproduction and a fix per finding
  • A letter of attestation for buyers and auditors
  • Findings tracked to closed in your Workspace
  • Findings and evidence in your Workspace as they are approved, not only at the end
  • On request: an engagement letter, a testing confirmation or authorization letter, a letter of attestation, or a letter of remediated findings after the retest, whenever you, your auditor or a buyer asks. Each is signed by a TrazTech Principal on our letterhead.

During and after the work

  • A weekly status update by email: what was done, what is waiting on you, and what is next.
  • One retest of Critical and High findings within 30 days of the report is included, with a retest letter.
  • A walkthrough call on Google Meet to go through the report and agree who owns each fix. Always included.
  • Sensitive testing data (captured traffic, credentials used, exploit output, logs) is destroyed 12 months after the final report or retest, and you get a destruction notice. The report and findings stay in your Workspace.

Every deliverable is delivered by the TrazTech team, reviewed and signed off by a TrazTech Principal, and issued on TrazTech letterhead. Your Workspace is the record: findings, evidence and remediation live there. Walkthrough calls are always included. On-site help is available as an extra and is never included by default. How we work

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 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.

Free PDFs, no card

Get the checklists that go with this

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: the files by email, then a few short notes over the next month. No spam, unsubscribe in one click.

Explore related work

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 A documented readiness position the audit firm can scope and price against Nothing. The audit firm prices your readiness, not your tooling

Platform pricing is a publicly reported range, since none of them publish a number. The fuller comparison, including when a paid platform is the better buy, is on the Workspace page.

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?

Our own team runs it from TrazTech’s fixed VPN IP, against the OWASP Top 10 for LLM Applications with tactics mapped to MITRE ATLAS, and a TrazTech Principal signs off every report. 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.

LLM Red Teaming, on your timeline

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

Book a call Send an inquiry