IBM AI Security: 67% More Worried in 2026

Listen to this article · 9 min listen

An IBM survey just confirmed what we’re all feeling: 67% of business and IT pros are way more worried about AI security risks than they were a year ago. That growing anxiety points to the core challenge we face in the field, which is how to build AI that actually works, and is trustworthy and secure, without opening up a Pandora’s box of new vulnerabilities.

Key Takeaways

  • Get a real data governance framework in place for quality and ethics. Bad data is why 85% of AI projects are failing.
  • Make explainable AI (XAI) a priority to build transparency, especially since a full 70% of consumers are now demanding to know how AI makes its decisions.
  • Build adversarial attack detection and mitigation into your AI lifecycle from the start to fight back against the 30% jump in AI-specific cyberattacks seen this past year.
  • You have to continuously monitor and audit production AI models, because model drift can kill performance by 15% or more in just a few months.

85% of AI Projects Fail Due to Data Issues

Data is everything for an AI system. We keep seeing industry reports that 85% of AI projects are failing, and the main reasons are always data quality and governance. It’s about having the right data, properly cleaned, labeled, and secured. Imagine you build a fraud detection system on historical data that’s biased against certain transaction types. That model is going to learn and even amplify those biases, producing unfair results. At its core, that’s a complete failure of trust. When your shiny new AI starts flagging legitimate transactions from one customer group as fraud, you’ve torpedoed performance, destroyed user trust, and opened your company up to all sorts of legal and PR nightmares.

I’ve seen it time and again with enterprise clients: investing in a real data engineering pipeline at the start of an AI project pays for itself many times over. That means you need automated data validation, anomaly detection, and serious version control for your datasets. We’re constantly telling clients to use a “data contract” for every single dataset that spells out the schema, expected distributions, and quality bars. If you skip this part, your AI model is basically built on quicksand.

70% of Consumers Demand More Clarity in AI Decision-Making

The “black box” problem, especially with deep neural networks, is a massive hurdle for building AI trust. It’s become a mainstream expectation for transparency, with a PwC global consumer survey showing that 70% of people want to know how an AI reaches its conclusions. Think about an AI diagnostic tool in a hospital. If that tool suggests a treatment plan, the doctor (and the patient) has to understand *why*. Was it a weird biomarker? A specific detail in the patient’s history? If you can’t answer that question, nobody’s going to adopt the tool, and the liability issues are a nightmare.

This is exactly why Explainable AI (XAI) is so critical. You can use tools like SHAP (SHapley Additive exPlanations) or LIME (Local Interpretable Model-agnostic Explanations) to get a real look at which features pushed a model’s prediction one way or another for any given case. Putting these techniques into practice is a strategic move for building secure AI that people actually trust. We build XAI into the development lifecycle from day one, defining interpretability right alongside performance metrics. It’s definitely more complex, but what’s the point of building a system that nobody trusts or will use?

30% Increase in AI-Specific Cyberattacks in the Past Year

The threat field for AI is changing fast. Cybersecurity firms are reporting a 30% jump in AI-specific cyberattacks in just the last year. We’re talking about attacks that go straight for the model or its data, not your typical network breach. The classic example is adversarial attacks, where an attacker makes tiny, almost invisible changes to input data to fool a model. Imagine a self-driving car’s vision system being tricked into seeing a stop sign as a 45 mph speed limit sign because of a few strategically placed stickers. This is a whole new class of security problem.

To build secure AI, you have to get ahead of the problem. You still need all the usual cybersecurity hygiene (secure code, access controls), but now you need AI-specific defenses too, like adversarial training and aggressive input validation. We push for a “security by design” mindset where you’re thinking about attacks like data poisoning or model inversion while you’re still designing the system’s architecture. You have to secure the model’s intelligence, not just the server it’s running on.

Model Drift Can Degrade Performance by Up to 15% Within Months

It’s a dangerous mistake to think an AI model will work perfectly forever once you deploy it. What really happens is model drift, the real world changes, but the model doesn’t, and we’ve seen research showing performance can drop by as much as 15% in just a couple of months. You won’t even see it happening without constant monitoring. A predictive maintenance model for factory equipment might start missing signs of failure as the machines age and operating conditions shift, leading directly to a surprise breakdown and expensive downtime. This is a performance problem that becomes a trust problem, fast.

The answer is to use strong AI observability platforms. These tools constantly watch a model’s predictions and input data, comparing them to what they’re supposed to look like so they can spot drift and send up a flare. Once drift is detected, you can have an automated retraining pipeline kick in or have a human take a look. On a big e-commerce recommendation engine we worked on, for example, we set up daily checks for concept drift by comparing current user preferences against our baselines. Catching it early means we can update the model before users notice the recommendations getting stale, which keeps both performance and trust high.

Disagreement with Conventional Wisdom: “More Data Always Means Better AI”

There’s this common saying that “more data always means better AI.” And while deep learning models do eat up large datasets, blindly following that advice can be a disaster for building good, secure AI. My own experience contradicts this constantly. I’ve watched companies hoard massive amounts of data, thinking sheer volume would make up for poor quality, which just leads to bloated storage costs and heavy compute loads for a model that actually performs worse. A model trying to learn from a giant, noisy pile of data can’t find the signal for the noise, and it opens up a huge attack surface for data poisoning since it’s so much harder to vet everything.

You’re much better off focusing on high-quality, relevant data, even if it’s a smaller set. A well-curated, properly labeled, and balanced dataset will beat a giant, messy one for a specific task almost every time. It’s also way easier to audit a smaller dataset for bias, keep it secure, and interpret the results. On one NLP project for legal document review, we got far better and more trustworthy results from a small, expertly annotated set of legal precedents than from a gigantic dataset we could have scraped from the web. The quality and domain-specific nature of the data was what mattered. If you just chase “big data” without a real strategy for quality, you’re just signing up to build an expensive, broken, and untrustworthy AI.

Building performant and secure AI solutions is a foundational part of the job for any organization that wants to use this technology effectively and responsibly.

What is AI trust?

AI trust is the confidence people (users, execs, the public) have that an AI system will work reliably, securely, and ethically. It means trusting it to give fair and accurate results without causing unexpected problems.

How does data quality impact AI performance and security?

Bad data (with biases, errors, or gaps) tanks an AI model’s performance, leading to wrong predictions and unfair results. For security, poisoned or compromised training data can bake vulnerabilities right into the model, leaving it wide open to adversarial attacks.

What are adversarial attacks in AI security?

An adversarial attack is when someone intentionally tricks an AI model by feeding it slightly altered input data. These changes are often invisible to a person but can cause the model to make a huge mistake, like misclassifying an image, which is a major risk for things like self-driving cars.

Why is explainable AI (XAI) important for trust?

Explainable AI (XAI) builds trust by opening up the “black box” so people can see *why* a model made a certain decision. This transparency is key for checking for bias, proving fairness, and meeting compliance rules in regulated fields.

How can organizations prevent model drift in their AI systems?

To stop model drift, you need to constantly monitor a live model’s inputs and outputs against a baseline. AI observability tools can spot when the data or the predictions start to change and then fire off an alert. That’s your cue to retrain the model or have an expert investigate to keep it performing correctly.

Editorial Team

The Editorial Team at App Performance Lab is a group of writers and editors who cover technology, products, and how teams ship. They research each story and publish under a shared desk byline — experts in their fields, working as one team.