Industries — LegalTech

Never lose a matter
to an AI attacker.

Autonomous agents of the class now coming for law firms, pointed at your platform first — as every role and at more than one firm, with proof attached to every finding and the evidence your SOC 2 and ISO 27001 audits ask for.

  • Every role, at more than one firm
  • Ethical walls tested from both sides
  • Audit evidence your assessor accepts
Integrate everything from your surface
  • AWS
  • Google Cloud
  • Azure
  • Cloudflare
  • GitHub
  • GitLab
  • Bitbucket
What we go after

Confidentiality is the product. These are the four places it usually fails.

01

One firm opening another firm's matter

The boundary your whole product rests on, and the one an object id walks straight through. Agents hold accounts at separate firms at once and work every pair between them: matters, documents, timelines, billing.

The proof, captured verbatim
1POST/api/auth/loginas paralegal@firm-b200
2GET/api/matters/4417/documentsbelongs to firm-a200 OK
3GET/api/matters/4417/documentssigned out401
02

Ethical walls that hold in the interface only

A conflict screen is an access rule, and access rules get enforced where they are easiest to write. Agents sign in on both sides of a wall and check whether the screened matter is genuinely unreachable or merely hidden from the menu.

Signed in on both sides of the wall
partnerteam-aassociateteam-aparalegalteam-bsupportfirm-wide
03

The share link that outlived the matter

Legal work runs on links sent to opposing counsel, clients and experts. Agents test what a link still opens after the matter closes, after the recipient is removed, and whether it grants more than the one document it was meant to.

GET/share/9f3c1amatter closed 14 months ago200 OK
04

Export is where privilege leaks

Bulk download, e-discovery production, the audit-ready PDF. Export paths are written late and reviewed less, and they routinely return more than the user could reach through the interface.

Paths agents work
Bulk document exportDiscovery productionGenerated PDFsReporting endpoints
The whole surface

Every system holding a document. Including the ones nobody has opened in a year.

Every domain you own, the providers underneath, and the hosts nobody has thought about since they were created. Discovery finds them from the outside, so a forgotten staging copy of the document store stays on the map whether or not anyone remembers deploying it.

Attack surface map

Your company, from the outside
AWS eu-west-1168 assets
Vercel96 assets
Cloudflare41 assets
Auth06 assets
Stripe9 assets
Datadog14 assets
Sentry4 assets
Heroku35 assets
Customer API42 assets
2api.acme.com
4api-eu.acme.com
gw.acme.com
events.acme.com
webhooks.acme.com
sandbox.acme.com
docs-api.acme.com
status.acme.com
Acquired estate26 assets
3sso.oldco.net
1vpn.oldco.net
2jira.oldco.net
wiki.oldco.net
mail.oldco.net
ftp.oldco.net
git.oldco.net
old-cdn.oldco.net
1
Payments18 assets
9
Internal tooling51 assets
3
Web application87 assets
Edge and DNS41 assets
1
Identity tenant6 assets
Billing9 assets
2
Observability14 assets
1
Error tracking4 assets
2
Legacy DNS9 assets
Critical findingsHigh findingsObserved relationshipReachable, not provenProven crossing
The loop

Prove it. Fix it with your own agent. Verify the fix.

1Prove
superhack.io / finding
proven
CRITICAL
$ curl -b "session=$B" /api/records/8124
HTTP/2 200
{ "id": 8124, "owner": "tenant-a" }
4 steps · captured verbatim

The finding is the transcript

Nothing is recorded without the requests and identities that proved it.

2Fix
Claude Code
Cursor
Windsurf
Copilot
Codex
Zed
Any client

Your coding agent writes the patch

Connect it over MCP and point it at the finding. The exploit is the spec.

3Verify
superhack.io / replay
verdict
Exploitablebefore
Solvedafter retest
Exploit no longer reproduces

Re-run the exploit

It reproduces, or it does not. That is the answer your customers' counsel wants.

Before a client firm asks

Find out what one firm
can reach of another's.

Point agents at your platform as every role you have, at more than one firm, and see what crosses the boundary your product is sold on. Every finding arrives with the request that proved it.

Audit evidence
Attached
Ethical walls
Checked
Every finding
Proven
Your data
Never trained on
FAQ

Frequently asked questions

Common questions from teams building legal platforms.