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 Security · HealthTech

AI Security for HealthTech

HealthTech AI that touches patient data combines model-layer risk with HIPAA exposure. We test your AI systems and make sure PHI does not leak through them.

Book a free readiness call Full AI Security service
From $4,000 CAD · scoped to what you built See full pricing →

Why HealthTech companies need AI Security

  • AI systems processing PHI can leak it through prompts, embeddings, RAG sources, or logs.
  • Prompt injection against a clinical or patient-facing agent could expose or misuse health data.
  • HIPAA safeguards have to extend to model pipelines, not just traditional infrastructure.
  • Enterprise health customers increasingly ask how AI features handle and protect PHI.

More context on this sector on our HealthTech industry page.

What our AI Security engagement covers

Tailored to HealthTech, delivered by a Toronto security and compliance team led by a published security researcher, with our offensive-security partner where offensive testing is involved.

  • PHI-leakage testing across the model pipeline
  • AI security findings mapped to HIPAA safeguard obligations
  • Threat model across LLM, RAG, and agent surfaces
  • Prompt-injection testing (direct, indirect, multi-turn, tool-call abuse) mapped to the OWASP LLM Top 10
  • RAG and data-layer leakage testing
  • Shadow-AI inventory and a prioritized remediation roadmap

See the full AI Security service page, or productized pricing for fixed-scope engagements.

Related pages

AI Security for HealthTech: common questions

Can AI features expose PHI?

Yes, PHI can leak through prompts, embeddings, RAG retrieval, and logs. We specifically test those paths and map findings to your HIPAA obligations.

Do we need AI security and HIPAA work?

If you run AI on health data, they reinforce each other: HIPAA sets the obligations, AI security tests whether your model layer actually meets them.

Is a third-party model safe for PHI?

Only under a BAA and correct configuration, and even then the application layer needs testing. We assess both.

AI Security for HealthTech, on your timeline

Book a free 30-minute discovery call. We will tell you whether this engagement fits, what it would cost, and when we could start.

Book a call Contact us

The same work, without the line item

Every readiness programme needs a control library, an evidence register, policies and a score for the board. Being quoted five figures a year for that is normal. Paying it is not.

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.

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.