A fixed-price gap analysis, remediation through to your audit, and upkeep after it. All in a workspace you keep.
All compliance →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 →To the people you sell to, raise from or answer to.
All industries →Original research, free tools, and plain-language guides on security and compliance, from a published security researcher.
Read the blog →Most companies have some version of a continuity plan. Almost none have evidence it works, and that is the part auditors ask about.
We run the impact analysis, write a plan somebody can follow at three in the morning, then exercise it and document what actually happened.
the processes the business runs on, an owner for each, and an agreed recovery time and recovery point objective per process rather than numbers we made up
An impact analysis, a plan somebody can follow, and an exercise that is actually run.
Your Statement of Work and our Terms of Business are signed by e-signature. Then your Workspace opens.
One checklist in your Workspace collects everything up front: contacts, scope, any read-only access the work needs (credentials as 1Password share links only), existing documents and who we should talk to. Each item says why we need it.
A Google Meet kickoff. When Ready to start comes in promptly, kickoff is usually about a week after signing.
| Stage | What happens | Typical timing |
|---|---|---|
| Start | Signed SOW, Ready to start (process owners, current plans, backup setup) and a 30-minute kickoff. | Kickoff usually about a week after signing. |
| Impact analysis and plan | Your process owners approve the recovery time and recovery point for each process. We never set them for you. | Agreed at scoping. |
| Exercise and report | A tabletop, component failover or full restore, timed against the targets, then the test report. | Set by the exercise you choose. |
Timings are typical ranges, not promises. They depend on scope and on how quickly inputs and decisions come back.
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
You end up knowing whether you can actually recover, in how long, and losing how much data. Where you cannot, you have a dated list of what to fix and who owns it. The test record sits on your completion record, so when an auditor asks when you last tested, the answer is a date and a document.
Free PDFs, no card
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.
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.
An incident response tabletop rehearses how you respond to a security incident: who is called, what is said, how it is contained. Continuity testing asks a different question: if this system is gone, can you keep operating and get it back inside the time you promised. Many clients run both, and the same people usually attend.
No, and the first exercise usually should not be. A tabletop proves people know the plan, a component failover proves one dependency, a full restore proves the whole thing. We pick the level that matches what you need to evidence and what your environment can safely take.
ISO 27001 A.5.29, A.5.30 and A.8.13, and SOC 2 A1.2 and A1.3. All of them want the same two things: a plan, and proof it has been tested.
At least annually, and at least once inside a SOC 2 observation window. If your architecture changes significantly, test again rather than waiting for the anniversary.
Recovery time objective is how long you can be down before it hurts; recovery point objective is how much recent data you can afford to lose. Your process owners set both per process in the impact analysis; we never set them for you. The exercise then measures whether you actually hit them rather than assuming you do.
It is a fixed price scoped to how many processes are in scope and the kind of exercise you need, from a tabletop to a full restore, quoted before starting. The starting price is on our pricing page.
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.