← Latest papers
💻 computer science

Protecting On-Device AI Inference: A Systematic Review of Attacks and Defence Mechanisms

This paper presents the first comprehensive systematic review of threats and defense mechanisms specifically targeting on-device AI inference, revealing a critical imbalance where adversarial attacks lack corresponding mitigation strategies despite comprising a significant portion of the attack literature.

Original authors: Zisis Tsiatsikas, Alexandros Fakis, Georgios Karopoulos, Vasileios Kouliaridis, Marios Anagnostopoulos

Published 2026-05-29
📖 6 min read🧠 Deep dive

Original authors: Zisis Tsiatsikas, Alexandros Fakis, Georgios Karopoulos, Vasileios Kouliaridis, Marios Anagnostopoulos

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 your smartphone or smartwatch as a tiny, high-tech vault that doesn't just store your photos, but also carries a brilliant, pre-trained expert inside it. This "expert" (the AI model) can recognize your voice, translate languages, or spot a pedestrian in front of a self-driving car, all without ever needing to call the cloud for help. This is the world of On-Device AI.

However, just like a vault in a busy city, this tiny expert is vulnerable. This paper is a systematic review (a massive, organized search) of the last few years of research to answer two big questions:

  1. How can bad guys break into this vault and steal the expert or trick it?
  2. What tools have good guys built to stop them?

Here is a breakdown of their findings using simple analogies.

1. The Attackers' Playbook (The Threats)

The researchers found that hackers have developed a wide variety of ways to mess with these on-device experts. They categorized these attacks into six main "heist" types:

  • The Physical Heist (Physical Attacks): Imagine an attacker holding a device and listening to the "hum" of its processor or measuring how much electricity it uses while it thinks. Just like a safecracker listening to the tumblers click, these attackers use side-channel tricks to figure out the secret code (the AI model) inside, even if the software is locked.
  • The Intellectual Property Theft (IP Attacks): This is like someone walking into a bakery, memorizing the chef's secret recipe, and then opening their own bakery down the street. Attackers try to steal the entire AI model or its "weights" (the knowledge it learned) so they can copy it or sell it. They do this by reverse-engineering the app or tricking the device into spitting out its secrets.
  • The "Trick the Expert" (Adversarial Attacks): Imagine a stop sign that has a few tiny, invisible stickers on it. To a human, it still looks like a stop sign. But to the AI in a self-driving car, those stickers make it look like a speed limit sign. The car speeds up and crashes. These attacks add tiny, invisible noise to images or sounds to confuse the AI and make it make a mistake.
  • The Privacy Leak (Data Privacy Attacks): Sometimes the AI remembers too much. An attacker can ask the AI questions and, based on its answers, reconstruct the private photos it was trained on (like a doctor's patient records) or figure out if your specific data was used to train it.
  • The Sabotage (Integrity Attacks): This is like a saboteur sneaking into the bakery and swapping the flour for sawdust. The AI still works, but it's now poisoned. It might work fine 99% of the time, but if you show it a specific "trigger" (like a specific pattern), it will suddenly do something malicious, like unlocking a door for a stranger.
  • The Energy Drain (Availability Attacks): Imagine a hacker shouting so loudly at the bakery that the chef gets exhausted and can't bake any bread. These attacks don't steal data; they just flood the device with complex tasks to drain the battery or freeze the phone, making the AI useless.

2. The Defenders' Toolkit (The Solutions)

The paper reviewed 44 different defense strategies proposed by researchers. They grouped them into five main "shield" types:

  • The "Split the Vault" Strategy (Model Segmentation): Instead of keeping the whole secret recipe in one place, the defenders split the AI model. They keep the most sensitive, secret parts of the brain inside a super-secure, isolated room (called a Trusted Execution Environment or TEE) and let the less sensitive parts work in the open. If a hacker breaks into the open room, they only get half the recipe.
  • The "Bouncer" Strategy (Access Control): This is like putting a bouncer at the door who only lets in people with a secret handshake. These defenses use licenses and passwords to ensure that only authorized users can run the AI or access its internal parts.
  • The "Scrambled Recipe" Strategy (Obfuscation): Imagine writing the recipe in a secret code that looks like gibberish to anyone who doesn't have the key. Defenders scramble the AI's code or hide its structure so that even if a hacker steals the file, they can't understand how it works or reverse-engineer it.
  • The "Fortified Room" Upgrades (TEE Optimisation): The "secure room" (TEE) is great, but it's often small and slow. These defenses are like renovating the room to make it bigger, faster, and more energy-efficient, so it can hold bigger, smarter AI models without slowing down the phone.
  • The "New Room" Extensions (TEE Extensions): Sometimes the existing secure room isn't enough. These defenses build new, specialized secure rooms (like for the graphics card) or create multiple isolated rooms so that different apps can run their AI safely without interfering with each other.

3. The Big Imbalance (The Key Finding)

The most surprising discovery in this paper is a massive mismatch between the problems and the solutions.

  • The Theft Gap: About 25% of the attack papers focus on stealing the AI model (IP theft). However, 50% of the defense papers are trying to stop this specific problem. We have too many guards for the front door.
  • The Missing Shields: The paper found that Adversarial Attacks (tricking the AI) make up about 33% of all the attacks studied. Yet, zero of the defense papers they found were specifically designed to stop these tricks!
  • The Black Hole: Similarly, there are almost no defenses for Availability Attacks (draining the battery).

The Bottom Line

The paper concludes that while we are getting very good at building walls to stop people from stealing the AI "recipe," we are ignoring the fact that the AI can be tricked, poisoned, or exhausted.

It's like building a bank with an impenetrable vault but leaving the front door wide open for people to just walk in and tell the teller to give them all the money. The researchers say we need to stop focusing so much on just protecting the "ownership" of the AI and start building better shields to protect the AI from being fooled, broken, or drained while it's running on our phones.

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 →