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

Find it before a buyer does

Testing, assessments and security leadership, run by the researcher who found the Mirai botnet kill switch.

All security →
Industries

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, from a published security researcher.

Read the blog →
Security

Penetration testing

From $3,500CAD · one app or API · scoped to your surface, retest includedSee full pricing →

Web app, API, network and cloud penetration testing from a team with OSCP-certified experts, signed off by the Principal who found the Mirai botnet kill switch. One retest within 30 days is included.

Book a scoping call
Attack path
From the internet to customer data
01
Internet
Anonymous attacker, no account
02
Web app
Self sign-up, then a session token
03
Orders API
Other customers' orders by changing one ID
04
Customer data
Names, addresses, order history
CRITICAL
Broken access control
Reported within 24 hours, retested after the fix
The admin panel held up: MFA enforced.
Example finding, not a client
Who tests it. A team with OSCP-certified experts, led by the Principal who found the Mirai botnet kill switch (CVSS 9.1).

Offensive security, run by people who find real bugs

Every report is signed off by a TrazTech Principal who found the Mirai botnet kill switch. We test your applications, network, servers, and cloud the way an attacker would, then hand you findings ranked by what they can actually do, with fixes, not raw scanner output. Testing is run by our own team from TrazTech's fixed VPN IP, which you allowlist, so you always know where test traffic comes from.

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.

What a penetration test with us looks like

A defined engagement with a signed scope, a fixed testing window and a findings report. Our method follows OWASP (the Web Security Testing Guide, the API Security Top 10 and ASVS) and the standard testing phases from planning to reporting.

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 testing in business hours by default, on staging or production as you choose. Findings appear in your Workspace as they are approved.Usually 1 to 3 weeks, set by scope.
ReportFindings report and letter of attestation, signed off by a TrazTech Principal.About 5 business days after testing ends.
RetestWe retest your fixes to Critical and High findings and issue a retest letter.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
  • Rate every finding with a CVSS 4.0 vector, adjusted one level only for documented business context, with both values shown
  • Write each finding so a developer can reproduce and fix it
  • Email your technical contact within 24 hours of finding anything Critical, before the report

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: executive summary, scope and dates, method, every finding with severity and vector, affected assets, reproduction, evidence, impact and fix
  • A letter of attestation you can share with buyers and auditors
  • Findings tracked to closed in your Workspace, not a PDF that goes stale
  • 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

The record behind the services above

Testing, a threat and risk assessment and readiness are sold separately, but they are usually delivered by the same people in the same quarter. These numbers come out of that combined work.

0
Client breaches post-engagement
100%
Audit pass rate

Work we have run

A Waterloo data centre operator, where testing fed a SOC 2 Type II and ISO 27001 run together across a production campus, an AI compute platform and a self-hosted collaboration stack. An Ontario medtech company putting an AI clinical assistant in front of practitioners, where the findings shaped the evidence programme behind their SOC 2.

Read the case studies →

Works well with

Penetration testing your auditor will accept

Compliance Penetration Testing

From $3,500

Auditors and enterprise buyers increasingly want a real penetration test, not a vulnerability scan. We scope, run, and report a pen test built to satisfy SOC 2 and ISO 27001 evidence requirements.

What is included
  • Scoping aligned to your audit and the systems your buyers care about
  • Hands-on, OWASP-based testing by our team from TrazTech’s fixed VPN IP, in business hours by default, on staging or production as you choose
  • An auditor-ready report with findings, severity, and evidence of testing
  • One retest of Critical and High findings within 30 days of the report, with a retest letter
  • A letter of attestation written for your auditor that you can also share with enterprise buyers
Talk to us about this →

Read the report before you buy it

You get a written report, not a scanner export with our logo on it. Here is a full specimen: a web application test with nine findings, each one carrying a reference, a severity, the CVSS score beside our own rating, what was affected, what to do about it, and where it stands on retest. The client and the findings are invented. The format is the one you get.

Sample penetration test report All sample reports
Comparing testing firms? We wrote the buyer's guide, including where the specialists beat us: penetration testing companies in Canada.

Which frameworks require a penetration test

Most companies buy their first penetration test because an auditor, an enterprise customer or an insurer asked for one. Here is what each framework actually says, including where it stops short of requiring a test outright.

FrameworkStatusWhat the requirement says
ISO/IEC 27001:2022A.8.8 and A.8.29 Expected Technical vulnerabilities must be managed, and security testing must be carried out during development and acceptance. Certification bodies routinely treat a penetration test as the evidence for these.
SOC 2CC4.1 and CC7.1 Expected The Trust Services Criteria never name penetration testing. They require evaluations of internal control and the detection of vulnerabilities, and a test is the most common way to evidence both. Auditors and enterprise buyers ask for it as a matter of course.
HIPAA Security Rule45 CFR 164.308(a)(8) Expected A periodic technical and nontechnical evaluation is a required implementation specification. Penetration testing is the usual technical half of it.
Cyber insuranceUnderwriting questionnaires Conditional Not a framework, but increasingly the reason a test gets bought. Carriers ask when the last test was performed and whether findings were remediated.

Two things worth asking any testing firm. Is a retest included, and for how long? Auditors sample remediation evidence, so a test without a retest leaves you with findings and no proof you closed them. Will findings map to the controls you are audited against? We track findings to closure in the workspace rather than handing over a PDF, and prices are on the pricing page.

Frequently asked questions

What kinds of penetration testing do you offer?

We run web application penetration tests, network penetration tests, server hardening and configuration reviews, and cloud penetration tests against AWS, GCP, and Azure. Every test is hands-on, OWASP-based and run by our own team, with one retest within 30 days included. You get a prioritized findings report mapped to severity and remediation, not raw scanner output. Testing is also available scoped as evidence for SOC 2, ISO 27001, and enterprise security reviews.

What is vibe-coding QA and security review?

A QA, security review, fuzzing and penetration test of software you built with AI coding tools. AI is fast but still ships logic flaws and security gaps. We review the generated code, fuzz it and pen test it, for far less than hiring a development team to rebuild it.

What is the difference between a penetration test and a vulnerability scan?

A vulnerability scan is automated and continuous. It flags known issues across your cloud, containers, and dependencies. A penetration test is a human-led attack that chains findings, tests business logic, and proves what an attacker could actually do. We triage scan findings by real exploitability, not CVSS score alone, and use pen testing where proof and depth matter.

Who performs the testing?

Our own team, testing only from TrazTech's fixed VPN IP, and every report is reviewed and signed off by a TrazTech Principal, a published security researcher who found CVE-2024-45163 (CVSS 9.1), the kill switch for the Mirai botnet. Where a buyer specifically requires a CREST-accredited tester, an accredited partner co-delivers under our scope and reporting.

Can a pen test satisfy my SOC 2 or enterprise security review?

Yes. We scope and report penetration tests to serve as evidence for SOC 2, ISO 27001, and buyer security questionnaires. If you also need the full framework program, our compliance team handles readiness and audit prep end to end.

Do you produce a Threat and Risk Assessment (TRA)?

Yes. A TRA is a formal document that identifies the threats to your systems and data, rates each risk by likelihood and impact, and documents your mitigations. It is a common requirement in Canadian government procurement, regulated sectors, and enterprise vendor reviews. We produce one backed by real testing of your environment, aligned with what Canadian reviewers expect, with a prioritized remediation plan.

Find out what's actually broken

Tell us what you are shipping and your timeline, and we will scope the right test against our pricing.

Book a scoping call