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 →
Security & Compliance Glossary

Incident Response

Incident response is the organized process for detecting, containing, eradicating, and recovering from a security breach or attack, then learning from it. A documented incident response plan defines roles, communication paths, and steps so a team can act fast under pressure. The goal is to limit damage and restore operations quickly.

In practice

A common framework has six phases: preparation, identification, containment, eradication, recovery, and lessons learned. Preparation matters most; the decisions you make calmly in advance are the ones that hold up at 2 AM.

Insurers, customers, and regulators all want to know who answers the phone during an incident. A retainer with a named team and agreed response times gives you that answer without building an internal SOC.

// how traztech helps

traztech delivers incident response retainers with agreed response times for startups and growth-stage companies, led by a published security researcher.

Book a call

For a broader look at getting audit-ready, see our SOC 2 readiness work, or talk to a fractional CISO about building a program around it.

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.

Where it comes up

The gap that hurts is almost never the document. It is that nobody has decided who declares an incident, who talks to customers, and which regulator or contract has a clock running.

For compliance, the artefacts are a written plan, evidence it was tested, and for any incident that occurred, the record and the post-incident review. A plan that has never been exercised is the most common finding in this area.

Incident Response: common questions

Does SOC 2 require an incident response plan?

Yes, and it also expects evidence that the plan was tested. A documented tabletop exercise is the usual way to satisfy that.

How often should we test the plan?

At least annually. A half-day tabletop is enough for most organisations and produces exactly the evidence an auditor asks for.