Latest / Trust Anchor / Proving What's Real: C2PA, Content Credentials and Deepfakes
Transcript
- speaker-0: A serial box tells you exactly what's inside it. The video you just shared tells you nothing. Today, we'll talk about the standard that's trying to change things. Welcome to Trust Anchor, the show about digital trust anchored. I'm your host, Jeremiah. In our trailer, I promised we'd get into the frontier stuff. We're starting with our biggest one, proving where content comes from. And I've got the right guest to help. Don Gennard is the director of content authenticity and IoT at SSL. Welcome to the show. I know it's late where you are, so thanks for making the time. Please introduce yourself and tell us a little bit about how you ended up working on content authenticity. speaker-1: Yeah, very nice to be on the show. Thanks, Jeremiah. I'm Dom Ginard and I was a researcher for many, many years in digital identities for consumer products. And so I was looking at authenticating things in the real world for many years, and then I had the chance to actually start looking at authenticating things in the digital world, and that's where I first got to know C2PA and I've been pretty active in the C2PA space for a a while and I was co chairing and I still am co chairing the watermarking task force of C2PA. And really it's a topic I really like because I think it's tremendously important and timely. So I'm pretty excited to be helping on that standard. speaker-0: Awesome. super excited to have you on the show today. I have a fun question to kick things off. What's the most convincing fake you've ever seen? speaker-1: That's a pretty fun question indeed and a pretty challenging one. I think I'll answer by saying I don't know and that's the problem, right? I mean I see a lot of stuff, but nowadays I don't know if it's real or not. And that's that's that's the big issue here. speaker-0: Yeah, that's really the concerning part, right? Is not knowing. for most of history, seeing was believing. When did that stop being true? speaker-1: That stopped a while back, I would say, w with tools like Photoshop or you could create pretty good fakes already, but it took a whole new dimension with the event advent of Gen AI. And today we know it's hard for humans to distinguish synthetic content from real content, but it's also hard for detection tools. The detection tools are getting much more challenged by the new models. And this is only going to exacerbate as new models are coming out. And It's harmful for a whole set of people and content creators, the newsrooms, the brands that are being impersonated, the small creators whose work gets stolen and reused by models. There are things that are being put in place to change that. for instance, regulation, the EU AI Act, is coming up and will require all the tools that are using generative AI to generate content to basically flag it. in a machine readable and human understandable way. So things are things are being implemented, but we're we're a little bit behind. Genai went much faster than we expected in terms of creating very high quality fakes. speaker-0: So is Providence about catching AI or about something bigger? speaker-1: I think it's no longer about catching AI only. It's about being able to understand the provenance of any content we're we're watching or consuming. I like the parallel to nutritional facts. Nowadays we know what we're eating, or at least we have some information about what we're eating because we have the nutritional facts of the food we consume. I think we need the same thing for the media we consume online, whether they're being synthetic or not, we need to know where they come from and how they have been manipulated. Because the world is not as binary as it has been AI generated or not, right? It could have been modified and we want to understand how and what has been modified. So yeah, it's definitely bigger than just catching AI. speaker-0: Okay, so let's start from the beginning. Explain CTPA like I'm sending it to my mom. speaker-1: first and foremost, C2P is a coalition. It's the Coalition for Content Provenance and Authenticity. And it was created by a bunch of companies, in particular Adobe, the BBC Reuters, and and more recently joined by other big companies like Google and Meta and others. And it's basically a set of standards that then allow adding provenance manifests to all kinds of assets. So whether it's an image or a video or a text file, even, you can attach those provenance metadata to the asset. And what it looks like then as a end consumer of the media is that you have this information attached to the asset. And typically you have this little CR logo that appears on the left corner or right corner of the asset. And you click on it, you get the provenance manifest. So you get all the information, again, all the nutritional facts of this asset. So you know where it comes from, how it was modified. You can even know things like who created it, which company, which individual. And so you have then this chain of custody. So this manifest is a chain of custody that's going step by step, tool by tool, and each tool adds the information. Whenever there's a modification, it's added to the manifest. So what you get as the end consumer is the full The full story of the asset. At SSL, we are providing one very important part of this story because those manifests have to be signed. If you open an asset in in Photoshop, or if you open an asset in an online tool, or if you modify an asset with a Gen AI tool, all these tools have to say that they manipulated the asset and they have to be able to prove it. And to do that, they sign. the manifest. So you really know it's coming from that tool because it has used its digital signature. There's also another layer of digital signatures that's meant for not for tools, but for individuals and organizations to be able to say that this asset comes from the BBC or even that this asset comes from this particular journalist at the BBC. So it's the manifest that can then be visualized by the end user. And each tool adds to the manifest and those manifests are assigned by trusted certificates. To wrap it up, if I was saying it to your mom, I would say CTPA is the standard and content credentials is what we see, the nutritional facts of the digital asset. speaker-0: Yeah, I think my mom could easily understand the idea of nutritional facts for media. So the standard exists, but if I run a newsroom or a photo platform, I don't want to become a cryptography company. What do I actually do? speaker-1: Yeah, that's a very good point. And it's not only a bit about becoming a cryptography company, above and beyond that is your company probably doesn't want to become a a C2PA specialist either if it's not your core business. And that's exactly what we designed the SSL provenance API for. The idea is to create a SaaS that you send your asset to, or you send a hash of your asset to, and we take care of everything. So we create the C2PA manifest for you. We can flag if the content comes from AI for you. We can add the C2P signature and we can add the cog signature. So that additional set of signatures that let you attribute the content to an organization or an individual. So we do all of that for you and we return the asset back or the sign manifest back. And then you have a fully compliant C2PA enabled asset. So it's really the idea of streamlining the creation of C2PA manifest, making it very simple, handling the certificates for you, handling the different intricacies of C2PA, the new versions of C2PA, we take care of all of that for you. And there's something else about that as well, is that if you have a tool and you want that tool to be conformant. To C2PA. So to be recognized in the C2PA trust list, you have to go through a set of certifications or conformance steps. And so we can also take care of that for you in the sense that you can use our certificate at first, and then later on you could bring your own certificate as you become conformant. Yeah, and additionally, I would say also we are always making sure that the API is at the cutting edge of C2PA. So as new features come in, we will add them to the API and you'll be able to benefit from it. One example is we're currently working on adding watermarking so that if a manifest gets removed from an asset, the watermark can be used to recover that manifest. So that's the kind of features you'll benefit from if you use the provenance API versus you having to follow the standard and continuously implement new features that are not in your core business. speaker-0: Okay, so if I'm a video company and I'm recording, you know, multigigabyte video files and I don't want to send that to you, how do I sign that asset? speaker-1: Yeah, that's a very good question. And and there we have three options. The the first option, you send the full asset, we take care of everything, we send the asset back with the manifest. That's the first one. But as you said, you might have very large assets, or you might simply not want to send them to a third party service for privacy or regulation reasons, regulatory reasons. so the second option we have is that you can send us just a hash. And then we use that hash to create the manifest. We send you the manifest back, and then you have to attach it to the asset. So it's a little bit more work for you. But the third option we have is that we also have an SDK. So an SDK you can use locally. And that SDK basically computes the right hash and then sends it to our API, the API signs, send you the manifest back, and the SDK attaches the manifest to the asset. So It's what you would get with the remote API, except the the asset never leaves your your machine. It stays on your machine and we get the the manifests remotely. speaker-0: Okay. So that's great that there's so many different options for signing. speaker-1: Yeah, that's that that that's definitely something that our customers asked for and we heard them. And I I think the another level that's also worth talking about is that the signing, we also have different options. So the default option, if you really want to have it straightforward without having your company go through conformance, you can basically sign with our tool and with our certificate. But on top of that, you might also want to add your own COG certificate. SSL sells these COG certificates. You can buy them today already. That doesn't require conformance. So that would allow you to say this was generated was signed by the provenance API, but the producer is the BBC or whomever. And then the the last option we have is that if you go through conformance but don't want to manage your certificate nor C2PA, then we do that for you. And so you can select the signature with your own certificate and so you can combine these different options. speaker-0: So someone's listening right now and they're thinking, Gen AI is driving this need for media prominence, and it's something that we want to add into our product or platform, or perhaps there's regulatory requirements that are pushing them forward. What should they do? speaker-1: Well, first of all, I think you're spot on when you say that there are regulatory requirements and and in particular the EU AI Act that requires companies that use Gen AI for creating assets that consumers see or consume to disclose that it was generated by AI or manipulated by AI. And that's very timely because December second is when these companies need to be ready for it. And because of Article fifty in that regulation, it's not only about Gen AI, pure Gen AI companies like the frontier models needed to apply that. It's also anyone who has a web shop and uses Gen AI to create the the pictures, or anyone who uses Gen AI at large for things that the general public can consume. So it's really timely. And I think that's why the provenance API is interesting, because The you know, you could go the long way and you could basically become a official and conformant C2PA generator product, but that will require you to go through conformance, fully understand the C2PA specification, fully implement it on your end. Whereas with the prominence API, you can get started very, very quickly. You just contact us, we give you access to the API, you can see the SDK on GitHub and use it. And so you can get started in days, literally. speaker-0: It's great there's a lot of different ways that are offered for companies to solve their requirements for media provenance and meet regulatory requirements. So we're gonna try out a new section. I think it's gonna be a lot of fun. I'm gonna ask some rapid fire questions. Are you ready? speaker-1: yeah, I guess. speaker-0: Okay, one word for where you think provenance is in five years. speaker-1: Everywhere. speaker-0: Everywhere's good. I think it's a great answer. The industry that needs this most and doesn't know it yet. speaker-1: I'd say consumer brands. the news industry and the media industry is really looking into CTPA, but yeah, I think it should transpire to every asset and consumer brands should also care about their assets. speaker-0: Do you think every phone camera will sign photos by default? speaker-1: Yes. this has started to happen. Samsung is supporting it, Google is supporting it. There's even a chipset that supports it natively from a a Snapdragon Qualcomm chipset, so it's gonna happen. speaker-0: What should listeners check on the next viral image they see? speaker-1: They should look for the little CR logo, use a platform like LinkedIn for instance that renders it and go and click on this CR logo to see where the asset comes from and who signed it. speaker-0: Okay, so that concludes our rapid fire questions. I think everybody's aware that Gen AI and deep fake technology is creating this urgent moment for us to know what's real when we're online or even out in the world engaging with media. But I think the most important thing that stands out to me, it's not so much being able to prove what's fake, but it's being able to prove what's real. Hey Dom, as usual, it's always great getting to chat with you. Thanks for coming on the show today. speaker-1: Thanks a lot, it was a great pleasure to be around. speaker-0: So that concludes today's episode. Next time we're going to be talking about backup CAs and why they're important as a redundancy. I'm Jeremiah. Thanks for listening to the Trust Anchor, Digital Trust Anchored.