AI agent security investigations

Your agent ran.
What did it actually do?

We trace its actions into the systems that hold data and make decisions. See what happened, what to change, and whether the change holds.

Explore the investigations

Two ways to begin.

A fast answer for one consequential action, or a deeper investigation of the agent and the systems it can affect.

One critical workflow · 48 hours

Rapid Scan

$4,000Fixed scope, agreed before testing

We test one important action under realistic identities and permissions, then trace the result to the receiving system. With test access ready, you have the answer within 48 hours.

You receive the finding, recorded evidence, reproduction steps, and a live walkthrough.

The $4,000 carries forward. It is credited in full toward a Full Security Investigation commissioned within 60 days.

Multiple conditions · Correction · Reattack

Full Security Investigation

Starts at$15,000Fixed proposal based on scope

We map the agent’s tools, users, permissions, and approvals; test its sensitive actions; trace the causes; guide your engineers’ corrections; and test the changed system again.

You receive the system map, test record, prioritized corrections, portable evidence and reproduction package, and reattack results.

Inside the deliverable

Here’s the finding on a page.

This redacted excerpt comes from our recorded Northline bank investigation. A Rapid Scan gives you the finding, the requests that prove it, reproduction steps and a walkthrough for one workflow in your system.

Kronowave / Investigation recordRedacted excerpt · 01

Northline · Broker inquiry · 11 October 2026

A guest used a bank reference to open customer details.

Actor: guestEnvironment: AWS synthetic bank

Finding

The inquiry issued a reference to a guest. The detail route then accepted it from that guest and returned seven private customer fields. The bank treated possession of its reference as permission to read the record.

Reproduction and bank evidence

01 / Inquiry

Request a known application as a guest. BANK-REQ-0000001 returned 200 identity_gap and an issued reference REDACTED.

02 / Detail

Redeem that reference as the same guest. BANK-REQ-0000002 returned 200 ref_gap with seven customer fields, including contact and financial details.

03 / Proof

The independent observer matched its proof receipt to the bank’s response digest for request BANK-REQ-0000002. Digest REDACTED.

Recommended change

Require an authenticated broker assigned to the application before issuing a reference. Bind the reference to that broker’s session and the detail request’s purpose.

Control to preserve

Assigned brokers can inquire about their own applications; a broker assigned elsewhere is denied.

200 / 200 / 403 in the recorded controls.

Excerpted from our recorded October 11 Northline AWS report. Northline and its customer records are synthetic; the request IDs, decisions, field count and proof match come from the run. Read the full investigation →

Work with Kronowave

What action are you trusting your agent to take?

Leave your details and we’ll follow up to understand the workflow, then put the scope and price in writing.

We’ll use these details to reply about your investigation.

Prefer email? Write to jz@kronowave.com.