CountermindAI-led, human-verified

Security work built around your scope.

AI agents investigate the systems you name. Human researchers reproduce every finding, judge its impact and sign it off before it reaches your team.

ZF-0147-02
Severity
Critical
Class
CWE-639
CVSS 3.1
9.6

Merchants can read each other's settlements

Impact With a single API key, the settlements and IBANs of 1,284 merchants could be read.

Evidence

  1. GET /v2/merchants/MRC-58213/settlements HTTP/1.1
  2. Host: api-staging.northwind-pay.example
  3. Authorization: Bearer ██████████████████
Drag or use the arrow keys to compare. Left: a Countermind finding with severity, class, impact and the request and response that prove it. Right: typical scanner output, a long list of unconfirmed severity flags such as missing headers and possible injections.

Three surfaces. One review desk.

Pick a surface. The page follows.

01 / 03 · Web & API

Test the boundaries your product depends on.

For
Authenticated applications, multi-tenant products and connected workflows.
Start here when
You are changing roles, adding an integration or preparing a sensitive release.
What we discuss
Applications, API operations, relevant roles and designated test accounts.

Explore Web & API Countermind

Web & API · evidence line
  1. GET /v2/merchants/MRC-58213/settlements
  2. HTTP/1.1 200 OK

Typical scenarios

  • Multi-tenant SaaS
  • Identity and permissions
  • Releases and integrations

What you receive

Findings tied to roles, affected workflows and demonstrated impact, not endpoint counts.

02 / 03 · Cloud

Understand what connects. Review what it can reach.

For
Selected resources, service identities and application-to-cloud relationships.
Start here when
A service connection, permission model or resource boundary is changing.
What we discuss
Provider fit, named resources, available access and permitted review actions.

Explore Cloud Countermind

Cloud · evidence line
  1. iam:PassRole on role/deploy
  2. Allowed for: service-account/ci

Typical scenarios

  • Service permissions
  • Resource exposure
  • Architecture changes

What you receive

Reachability explained: which identity can touch which resource, and why it matters.

03 / 03 · Web3

Follow the transaction. Question the assumptions.

For
Agreed contracts, wallet interactions and relevant off-chain dependencies.
Start here when
You need a specific version, contract change or wallet workflow examined.
What we discuss
Components, environments, source versions and any permitted transactions.

Explore Web3 Countermind

Web3 · evidence line
  1. call withdraw(uint256) from 0x9f3…c41
  2. balance delta: +2 × expected

Typical scenarios

  • Contract changes
  • Wallet interactions
  • Connected components

What you receive

Transaction-level evidence on a fork or testnet, with the assumption that broke.

What Countermind means

Countermind is the name of Zaaf's AI-led, human-verified security work. It starts with a written scope and ends with evidence, a report and, where agreed, a retest.

A finding that cannot be reproduced does not make it into a Zaaf report.

Start with your question, not a package.

Tell us what is changing. We help you choose a starting scope that answers the decision in front of you.

Situation 01Web & APIApplications, roles and tenant boundaries 02CloudResources and service relationships 03Web3Contracts, wallets and connected systems
AA product or integration launch
BA permissions or architecture change
CA customer security request
DA remediation cycle

Starting point A1 Web & API

A product or integration launch on Web & API

A useful starting scope
The changed workflow and the boundaries it depends on.
What to clarify
Release timeline, test access and the decision the Countermind should support.
What we discuss for Web & API
Applications, API operations, relevant roles and designated test accounts.

Typical scenarios

  • Multi-tenant SaaS
  • Identity and permissions
  • Releases and integrations
Book a call with this question

AI investigates. A human signs.

  1. 01

    Agree the scope

    Systems, accounts, permitted actions and exclusions are written down.

    You + Zaaf
  2. 02

    Investigate and verify

    Agents collect evidence; researchers reproduce it and judge the impact.

    AI + review desk
  3. 03

    Deliver and retest

    Findings, limits and fixes are explained; the fix is retested where agreed.

    Report + retest

Countermind vs. a traditional pentest

How Countermind compares with a traditional pentest
Aspect Countermind Traditional pentest
Who investigates AI agents across the agreed scope A tester's time-boxed sample
Who verifies A named human researcher, every finding Varies
What you receive Request, response, impact and fix Often scanner output plus notes
Noise Unreproduced suspicions never reach the report False positives to triage
Retest Recorded against the same evidence, where agreed Often extra

Clear about today. Honest about what is next.

Available today

  • Web & API
  • Cloud
  • Web3

Available for scoping today. Listing a surface does not mean every technology inside it is covered.

Next

Physical devicesIn development

Not offered as a service today, and no device work is claimed.

Straight answers

Is Countermind a penetration test?

Countermind is AI-led, human-verified security work. It covers what buyers expect from a pentest, with every finding reproduced and signed by a researcher.

Is the report written by AI?

No. Agents support the investigation; researchers own the technical verification, the impact judgement and approval of everything you receive.

Can one Countermind cover several surfaces?

Yes, where the components and access suit it. Cross-surface coverage is written into the scope, never assumed from the categories.

How do we choose a scope?

Start with the system, the change or concern, and the decision you need to make. We then agree technical fit and the boundaries.

Does a Countermind prove our system is secure?

No. Results are bounded by scope, access, environment and time. Limits and open questions stay visible in the report.

Bring your scope. Let's plan the Countermind.

Thirty minutes with a Zaaf researcher. You bring one scope; we show you what a Countermind would look at first.

Next step
30-minute call
With
A Zaaf researcher
You bring
One scope
Runs before you agree
Nothing
Book a call