Digital trust statement
Speech by MP Julien Marchand at today's parliamentary session on digital trust.
Arbor Signum · Content Credentials (C2PA)
Every video carries its own proof of origin. Click the Content Credentials mark in the player to see who published it, where it came from and whether it has been changed since.
Media centre
Video statements published by a fictitious parliament on Arbor WebTV. Content Credentials are shown where provenance information has been attached.
Speech by MP Julien Marchand at today's parliamentary session on digital trust.
Court of Justice of the European Union - Recording where validation does not match the original and causes a failed Content Credentials signal
An impassioned speech by MP Mara Elsenbrück on protecting citizens.
Story · The altered clip
Someone downloads an official clip, replaces the speaker’s face and posts it again. The Content Credentials are gone, but the invisible watermark is not. See how a communications officer uses the Arbor Signum Verify Portal to find the original and see exactly what was changed.
Watch the storyHow it works
Every recording gets an invisible watermark and a signed C2PA manifest. When clips are combined, the new video keeps a record of where each part came from.
Clips with and without credentials can be combined. The new manifest points to the original manifests and notes any content that had none.
C2PA signing and the Content Credentials mark in the player are part of Arbor Signum Publication. Invisible watermarking is part of Arbor Signum Protection.
FAQ
Click a question to see the answer.
The audio is protected by the signature; the watermark currently covers the video. Audio and video are hashed and signed together as one audiovisual package, so any change to the audio is detectable. The invisible watermark is applied to the video only for now.
Audio watermarking is on our roadmap. If it becomes a formal requirement for you, we can revisit our delivery priorities together.
Not yet. Live sessions do not yet carry C2PA information, so the Content Credentials logo does not appear during a live broadcast. Live support is on our roadmap.
Watermarking adds a small delay of a few milliseconds. We have not yet quantified the effect on image quality, audio quality or encoder load. We will measure all three during the pilot, so you can decide on figures from your own environment.
The Arbor Encoder adds a Layer 1 watermark during encoding. The clipping tool can add a Layer 2 watermark to clips. Layer 1 watermarking also works for content that arrives without an existing watermark. Recovery is designed to follow the same principle, although full C2PA support in that process is still in development.
Tools, encoders and editing processes that do not support C2PA can remove the credentials or make them invalid. That is by design: a modification outside a C2PA-aware workflow breaks the chain of provenance, so anyone checking the recording can see that it has changed.
C2PA-aware tools read the existing provenance information, keep it and add their own editing steps.
You decide how robust it needs to be. The watermark can survive operations such as cropping and re-encoding, to a configurable degree. Greater robustness can make the watermark more visible, so we tune the setting with you and validate it during the pilot.
No. Apart from embedding the watermark, Arbor Signum leaves the codec of the Arbor Encoder output unchanged. Format and codec compatibility stays as it is today, determined by your current encoding and distribution chain.
Yes. C2PA information is openly readable. Partners can keep and extend the credentials when their tools support the public C2PA specification. Processing that does not support C2PA may remove or invalidate them.
We therefore recommend agreeing with your chain partners that they use compatible workflows and retain provenance metadata.
Yes. Keeping and extending credentials from upstream devices has been the intended direction from the start. There is currently no confirmed way to carry C2PA information from the camera through the SMPTE ST 2110 contribution path into this workflow. We will implement it once a clear, interoperable method is available.
The certificate is issued to your organisation, which applies for it and owns it. Arbor needs controlled access to use the signing key for the service. The key is stored in Azure Key Vault Premium, protected by a hardware security module.
Yes. Key usage is recorded through Azure audit logging.
Yes. Because the certificate is yours, you can ask the certificate provider, such as SSL.com, to revoke it.
Arbor Signum is an add-on to an Arbor product. It is not available on its own for other platforms.
Yes, in principle. Textual metadata such as speakers, agenda items and timecodes can be included in the C2PA manifest, so the context of the session travels with the recording. Together we decide which metadata is useful and proportionate from a privacy perspective.
You decide which personal data, if any, goes into the manifest.