Scope and threat model
We start from what would hurt you and work backwards to the attack surface.
Seven phases, each with a named owner. Where we use automation, the phase says so.
An engagement is not one activity, and the split between people and tooling is different in each phase. This is how the work is actually divided.
We start from what would hurt you and work backwards to the attack surface.
Full enumeration: hosts, services, subdomains, cloud assets, exposed credentials, public code. Automation runs the sweep. Operators set the hypotheses it is sweeping for.
Every action against your systems is chosen and executed by an operator, and we can tell you why each one was taken.
Each confirmed bug becomes a search pattern applied across the whole estate. Where a pattern returns many hits we verify a representative sample by hand and report the remainder as a class, labelled as such, with the verified samples named. We never fold unverified hits into the verified count.
Individual findings assembled into the paths that matter: a forgotten staging host to domain admin, a read-only API key to your customer database.
Every finding reproduced by hand with a proof of concept you can run yourself. Nothing ships on the word of a tool.
Written for two audiences at once: the engineers who have to fix it and the executives who have to fund it. Retest of remediated findings is included in the fee.
Every security vendor now claims AI, and most of them mean a scanner with a chat box bolted to the side. We use these models daily. They have changed how much ground we can cover. They have not changed who does the difficult part. We ran them inside our own shop for eighteen months before they touched a client engagement, and everything below happens on our own cluster — none of it involves sending your data anywhere. Here is our position.
So we use it the way we use any other tool: for coverage, never for conclusions.
The machine proposes, an operator proves. Ask any firm which parts of your report a person verified. The answer should be all of them.
If a firm is going to point tooling at your source code and your network, you are entitled to know exactly where that data goes. These are the commitments we work under.
One call is enough to scope an engagement. We will tell you whether we are the right firm for it, and what it will cost.
[email protected]What should be tested: an application, a network, an Active Directory estate, a cloud tenant, an AI system, your people, or all of it.
What you are worried about: ransomware, a regulator, a customer security questionnaire, a breach you already had.
Any deadline you are working against: an audit date, a release, a board meeting, a contract renewal.
Production systems that cannot be touched, change freezes, legacy you already know about, or testing you have had before.