October 25, 2026
On October 15th, the 44% problem was named: the reality that nearly half of all ransomware attacks now exploit a victim's own AI agents.
That report did not create a new problem. It exposed an old one. The problem is not that AI agents exist. The problem is that when they act, they leave behind logs. They do not leave behind proof.
This is the month the bill came due for that distinction.
This is not just a cybersecurity problem. It is the exact same failure mode that just cost Bank of America $1.2 billion.
On October 13, FinCEN announced a massive settlement. The bank’s automated transaction monitoring system—the Event Processor—was suppressing alerts. It set thresholds based on "stakeholder judgment," tested those thresholds, found they were wrong, and kept them anyway to save on investigative resources.
When regulators asked why the system suppressed billions of dollars in suspicious activity, the bank could not prove the decision was correct. FinCEN’s ruling was clear: Automating a decision does not remove the obligation to establish that the decision is supportable.
This week, Wall Street discovered the same thing. JPMorgan and Charles Schwab are blocking third-party AI agents from customer accounts because they cannot determine who is liable when an agent acts. They cannot tell if the agent stayed inside its mandate.
Whether it is a ransomware agent encrypting a server or a trading agent moving money, the root cause is identical: Unverified autonomous action.
When a breach occurs, an investigation begins. But an investigation without a deterministic record is not an investigation. It is a reconstruction from memory.
Consider what an investigator actually needs to establish:
| Question | What It Requires |
|---|---|
| Did the agent take the action? | A deterministic record of the action |
| Was the action authorized? | A verified authority chain |
| Was the input authentic? | Evidence provenance |
| Was the execution correct? | A replayable execution record |
| Was the agent manipulated? | A comparison of intended vs. observed behavior |
None of these can be answered by standard logs. Logs record that something happened. They do not record why. They do not bind the decision to a rule. They do not chain the authority. They do not prove the input was real.
An investigation without these records is not an investigation. It is a guess.
To solve this, the industry needs a complete architectural chain. Not a point solution. A stack.
The architecture consists of six layers:
The National Association of Insurance Commissioners (NAIC) is currently finalizing its AI Risk Evaluation Supplement. It is not issuing a direct legal mandate. It is giving state examiners a new question to ask insurers.
The examiners will ask for a "Contemporaneous Action Record"—a record created at the time of the action, whose integrity a third party can verify without access to the insurer's systems.
How does a CISO produce a verifiable record of a black box? They can't.
To solve this, the architecture introduces the Attestation Record. It is an assembly layer that sits on top of the six-layer stack. It is not a policy document. It is a cryptographically sealed artifact that bundles the proof generated by the engine.
It does not change the engine. It packages the deterministic proof for a human signature. It requires the CISO to use their corporate credentials—a PIV card or a hardware security key—to digitally sign the batch.
It turns a black box into a signed liability transfer. It creates the legally binding chain of custody from the algorithm to the boardroom. It is how an examiner is shown that a human with authority reviewed the machine's behavior and accepted responsibility for it.
It is the answer to the NAIC's question.
The October 44% report did not create this problem. It exposed it. The problem existed the moment organizations deployed agents with authority they could not verify.
The Decision Contract defines the five conditions for a compliant record of an automated decision: determinism, replayability, tamper-evidence, framework mapping, and rationale.
The standard was published in August. The spec is live. The six layers are deployed.
The question is not whether the industry will adopt agent accountability. It is already happening. The question is what standard the industry will adopt.
There is only one that was published before the problem became a headline.
The engine is live. The API is live. Access is available.
Founder & CEO, The Jason Logic Group
[https://seais-decision-core.onrender.com](https://seais-decision-core.onrender.com)
[thejasonlogicgroupllc@gmail.com](mailto:thejasonlogicgroupllc@gmail.com)