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. One standard report, letters for your buyers, and retests 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 governance

AI Acceptable Use Policy

From $750 CAD · scoped to you

A ready-to-adopt AI acceptable use policy written for your company: which AI tools are approved, what data can and cannot go into them, who reviews AI output, and what each employee is responsible for.

Book a discovery call See pricing

We roll it out and keep the acknowledgement records in your TrazTech workspace. Buy it on its own or fold it into a compliance engagement. Want to see the shape first? Draft one with the free AI acceptable use policy generator.

Built for teams that...

  • Companies whose staff already use AI assistants and coding tools without written rules
  • Teams asked by a customer, insurer or auditor how they govern AI use
  • Organizations working toward SOC 2, ISO 27001 or ISO 42001 that need an AI policy in the policy set
  • Leaders who want one short policy people will read and acknowledge

What we do

  • A policy tailored to your company, drafted from a short intake on the tools you use, the data you hold and the work your teams do
  • Approved, restricted and prohibited AI tools, and how a new tool gets requested and approved
  • Data rules: what may go into an AI tool, what must never go in (customer personal information, credentials, health or payment data, confidential code unless the tool is approved for it), and the settings that must be on
  • Review and approval rules: when a person must check AI output before it is used, shipped or sent to a customer, and when AI use is disclosed
  • Employee responsibilities, how to report a mistake or suspected data exposure, and what happens when the policy is not followed
  • Rollout in your TrazTech workspace: the policy published to staff, acknowledgements collected and tracked, and a record ready for an auditor or customer
  • A walkthrough with you before adoption, with your changes made

What you walk away with

You adopt a policy that fits how your company actually uses AI, with a record of who has read and acknowledged it. It slots into a SOC 2, ISO 27001 or ISO 42001 policy set as written. The natural next steps are ISO 42001 when customers want a full AI management system, and security awareness training so the rules are taught, not only signed.

Explore related work

Frequently asked questions

Why not just use the free generator?

Many teams start there, and it gives you a sound first draft. The paid policy is written from your own tools, data and teams, reviewed with you, and rolled out with acknowledgement records, which is what an auditor or a customer asks to see.

What does a clause in the policy look like?

For example: "Customer personal information, credentials and payment data must not be entered into any AI tool that is not on the approved list. Approved tools are used through company accounts, with training on our inputs turned off." Every rule is written to the tools and data you actually have.

Can it be part of a compliance engagement?

Yes. Buy it on its own, or fold it into a SOC 2, ISO 27001 or ISO 42001 engagement, where it joins the rest of your policy set in the same workspace.

How are acknowledgements tracked?

Staff read and acknowledge the policy in your TrazTech workspace. You see who has acknowledged and who has not, and the record is ready to show an auditor or a customer.

What comes after the policy?

ISO 42001 when customers or regulators expect a full AI management system, and security awareness training so staff learn the rules as well as sign them.

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.

AI Acceptable Use Policy, 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 →

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.

Track record

Who is actually doing the work

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
Zero
Exceptions on a SOC 2 Type II built from nothing in-house

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 with zero exceptions.

The platform stayed in production 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.