Contact
Start an engagement
An engagement begins with a scope you define and a manifest you approve. Nothing runs before that, and nothing runs outside it afterwards.
Get in touch
Email is the fastest route, and it reaches the people who build the thing rather than a queue.
Tell us roughly what you want assessed and what you run for monitoring. If you would rather see the measurement record before you talk to anyone, ask for the ledger and we will send it.
What the first engagement looks like
- You define the scope. We do not discover your assets; the platform cannot invent a network to scan.
- You approve a manifest. Scope, each permission granted, a time window, and a kill switch. Anything lateral or destructive needs a separate sign-off.
- You place an agent. One container per network segment. It dials out, so you open no inbound ports.
- We run, and you watch. Every command is recorded on your hosts as well as ours, including the ones the scope refused.
- You get findings and your detection gap. Then you fix something, and we run the same technique again.
Before you commit to anything
Ask us anything you would need to know before letting us run real techniques against your systems, and ask it now rather than three meetings in. We would rather answer a hard question in writing than have you find the answer later — what crosses the boundary and what a report tells you are the two most people start with.