← Latest papers
🤖 machine learning

Certified in Theory, Broken in Practice: Assumption Gaps in Cryptographic Model Certification

This paper reveals that current cryptographic model certification protocols are vulnerable to attacks where models behave well on fixed audit datasets but fail in practice due to unverified generalization, and it proposes rigorous security definitions and a new protocol template to ensure certified guarantees hold for fresh data from the same distribution.

Original authors: Carter Luck, Olive Franzese-McLaughlin, Elisaweta Masserova, Akira Takahashi, Antigoni Polychroniadou, Nicolas Papernot

Published 2026-07-27
📖 6 min read🧠 Deep dive

Original authors: Carter Luck, Olive Franzese-McLaughlin, Elisaweta Masserova, Akira Takahashi, Antigoni Polychroniadou, Nicolas Papernot

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a world where we can ask a computer to make important decisions—like approving a loan, diagnosing an illness, or deciding who gets a job—without ever seeing the computer's "brain." This is the promise of Privacy-Preserving Machine Learning. It's like hiring a chef to cook a secret family recipe for you; you want to taste the dish to make sure it's delicious (accurate) and fair (doesn't discriminate), but you don't want to see the recipe or the ingredients because they are the chef's trade secrets.

To solve this, scientists use Zero-Knowledge Proofs (ZKPs). Think of this as a magic trick where the chef proves they followed the recipe perfectly without ever showing you the ingredients. They use complex math to create a "certificate" that says, "I promise this dish is 99% delicious," and the math guarantees they aren't lying. For a long time, everyone assumed that if the math said the certificate was valid, the dish would taste great no matter who ate it. But what if the chef could trick the magic trick? What if they cooked a special version of the dish just for the taste-tester, knowing exactly what the tester would ask for, while serving a completely different (and terrible) meal to everyone else? That is the question this paper asks.


The Great Audit Heist: Certified in Theory, Broken in Practice

This paper, titled "Certified in Theory, Broken in Practice," reveals a sneaky loophole in how we currently check these secret AI models. The authors, a team of researchers from universities and J.P. Morgan, discovered that the "magic certificates" used to verify AI models can be easily faked if the model creator knows what the test will look like beforehand.

The Setup: The Blind Taste Test

In the real world, when a company wants to prove their AI is fair or accurate, they usually hire an auditor. The auditor picks a list of test questions (a dataset) and asks the AI to answer them. The AI owner then uses a Zero-Knowledge Proof to say, "Look, I answered 99% of these correctly, and I didn't cheat!"

The problem is that in many current systems, the AI owner gets to see the test questions before they lock in their final model. It's like a student getting the exact exam questions a week before the test, memorizing the answers, and then handing in a blank sheet of paper that magically proves they knew the answers.

The Attack: Cooking for the Judge

The authors show that a malicious model owner can "forge" their training data to pass the audit while failing in the real world. They call this a Data Forging Attack.

Here is how the trick works, using the analogy of a Decision Tree (a flowchart that makes decisions):

  1. The Setup: The auditor gives the model owner a specific list of 1,000 test questions (the audit dataset).
  2. The Trick: The model owner takes those 1,000 questions and creates thousands of "neighbor" points around them. They add these new points to their training data, but they flip the answers (labels) on these neighbors. They also add a rule to their model: "If the question looks exactly like one of the 1,000 test questions, give the right answer. If it looks even a tiny bit different (like our new neighbor points), give the wrong answer."
  3. The Result: When the auditor runs the test, the model gets 99% or even 100% correct because it has memorized the test. The Zero-Knowledge Proof checks out, and the model gets certified as "High Accuracy."
  4. The Betrayal: But as soon as the model is deployed to the real world and sees new data (even data that looks very similar to the test data), it fails miserably. In the paper's experiments, models that passed with 99% accuracy on the test dropped to less than 30% accuracy on new, fresh data.

The authors tested this on fairness audits too. They showed a model could look perfectly fair on the test list (giving equal approval rates to different groups) but be wildly unfair in the real world, denying loans to specific groups almost 100% of the time.

Why Simple Checks Don't Work

You might think, "Wait, couldn't the auditor just check if the training data looks like the test data?" The paper shows that the attackers are smart enough to fool even standard statistical tests. By adding extra copies of the test data into the training set, the attacker makes the two datasets look statistically identical. Tests like Welch's t-test (a common way to see if two groups of numbers come from the same source) would look at the data and say, "Yep, these look the same!" even though the model is secretly rigged.

The authors ran simulations on six different real-world datasets (like credit card defaults and employment records) and found that this attack works reliably. They even showed that the attack works on more complex models like XGBoost and Neural Networks, not just simple decision trees.

The Solution: The Surprise Test

So, how do we fix this? The paper proposes a new way to run these audits, which they call a Secure Cryptographic Model Certification (CMC).

The key idea is simple but powerful: The model owner must lock in their model before they see the test questions.

Imagine a game where:

  1. The student (model owner) writes their answers on a piece of paper and seals it in a locked box (a cryptographic commitment).
  2. Only after the box is sealed does the teacher (auditor) hand them the exam questions.
  3. The student then uses the magic proof to show they answered the questions correctly based on what's inside the box.

Because the student couldn't see the questions when they locked the box, they couldn't rig the answers. The paper proves mathematically that if you follow this "Commit-Sample-Prove" order, the model must actually be good at the task, not just good at passing the test.

What This Means

The authors are careful to say they aren't saying the old math is "broken" or that the Zero-Knowledge Proofs themselves are wrong. The math works perfectly; it's just that the rules of the game were flawed. The old rules allowed the model owner to cheat by knowing the test in advance.

This paper serves as a wake-up call. It shows that for privacy-preserving AI to be truly trustworthy, we can't just rely on a one-time test with a known dataset. We need to ensure the test is a surprise, or we need to keep checking the model continuously with fresh data. Without these changes, we risk deploying AI systems that are certified as "perfect" but are actually broken in the real world.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →