Explore 3 source-supported AI security cases for 13.8 · Repudiation & Untraceability in Databricks DASF 3.0, with evidence, scope, and defensive analysis.
Risk category
An organization cannot trace or account for an agent's actions because logging or decision transparency is insufficient. It may be unclear what the agent did and how its decisions led to the outcome. The missing evidence weakens investigation and accountability when an action is disputed or harmful.
Symantec observed unofficial AI relay setup scripts on endpoints at roughly a dozen organizations from early 2026. The scripts changed where genuine Codex and Claude Code clients sent model requests. In the Codex configuration they also set danger-full-access, removing local sandbox restrictions. One observed Claude Code setup also replaced the user’s existing login with a relay-issued credential. A relay can see the prompts and code actually sent through it and can influence replies. The endpoint evidence establishes these configuration changes; the report documents no malicious commands or confirmed credential theft by relay operators.
Why it relates: Suppressing vendor reporting weakened one data source for reconstructing agent activity. These are observed setup changes, varying by client and host. Symantec reports no malicious relay responses or confirmed downstream theft, and disabling vendor telemetry does not disable enterprise logging.
Endpoint observations establish configuration changes. Subsequent malicious activity by the relay operator was not observed.
Chainstack provides blockchain infrastructure services. Chainstack traced its October 2026 intrusion from a test Grafana instance to an unauthenticated, cluster-admin MCP server, then to production through compromised machine credentials. The investigation found database access, secret theft and several persistence routes. It did not recover individual MCP calls or establish customer-node modification. ARTEX is the operator’s assessment of the attacker’s tooling, not actor attribution.
Why it relates: The investigation could not recover individual MCP tool calls and had to assess execution from surrounding evidence. This establishes a tool-action traceability gap, not proof that an agent deliberately hid its reasoning.
The relation follows the assessed MCP integration and the documented infrastructure effects; separate observed routes remain separate.
Zenity Labs tested two routes against Agentforce in Slack. An external attacker could plant instructions in a CRM lead later read by an employee's agent; an internal caller could directly ask the agent to post. In the tested Slack Knowledge template, Reply to a Slack Thread lacked confirmation and invoker attribution, and a crafted URL survived redaction. Salesforce fixed the reported defaults and bypass by September 2026.
Why it relates: Zenity Labs tested two routes against Agentforce in Slack. The relevant category is Repudiation & Untraceability: An organization cannot trace or account for an agent's actions because logging or decision transparency is insufficient.
Zenity Labs tested two routes against Agentforce in Slack. An external attacker could plant instructions in a CRM lead later read by an employee's agent; an internal caller could directly ask the agent to post. In the tested Slack Knowledge template, Reply to a Slack Thread lacked confirmation and invoker attribution, and a crafted URL survived redaction. Salesforce fixed the reported defaults and bypass by September 2026.