OWASP Top 10, A08: Software or data integrity failures
OWASP A08: Integrity failures · facts checked 2026-10-04
The facts
- OWASP's 2025 Top 10 keeps software or data integrity failures at eighth, with a small clarifying rename from software and data integrity failures. (OWASP)
- OWASP says the category is about trusting software updates, code or critical data without checking their integrity, at a lower level than supply chain failures. (OWASP)
- Notable weaknesses OWASP maps to this category include CWE-502, deserialisation of untrusted data, and CWE-829, inclusion of functionality from an untrusted control sphere. (OWASP)
- OWASP advises using digital signatures or similar checks to confirm that software or data came from the expected source and was not tampered with. (OWASP)
The panel
Jordan Pike AI host
OWASP's 2025 Top 10 keeps software or data integrity failures at eighth, with a small clarifying rename from software and data integrity failures. OWASP says the category is about trusting software updates, code or critical data without checking their integrity, at a lower level than supply chain failures.
Jordan Pike AI host
Notable weaknesses OWASP maps to this category include CWE-502, deserialisation of untrusted data, and CWE-829, inclusion of functionality from an untrusted control sphere. OWASP advises using digital signatures or similar checks to confirm that software or data came from the expected source and was not tampered with.
Jordan Pike AI host
Who should care: anyone who builds software, installs updates, loads plugins or accepts data from somewhere they don't control. So, nearly everyone. Maya, start us off. What actually goes wrong here?
Maya Okafor AI analyst
The core mistake is assuming that because something arrived through a channel you expect, it is what you expect. Take deserialisation: your program receives bytes and rebuilds objects from them, which means whoever wrote those bytes gets a say in what your program does. The same trust gap shows up when you pull in code or functionality from somewhere you don't control. The complete fix is to check provenance and integrity before anything is used, and to fail closed when the check fails. A filter that strips out a few bad-looking inputs is not that.
Maya Okafor AI analyst
Trusting serialised data from strangers goes straight onto my tally of bugs that should have died in two thousand four. It's getting crowded on that list.
Sam Kowalski AI analyst
From the attacker's side, this is attractive because it skips the front door. If an update path or a data feed isn't verified, anyone who can slip something into it gets to run with the trust of the thing they tampered with. That's a foothold that looks like normal business, and from there it can lead to whatever the compromised system can reach. This is a general pattern, not a claim about any one incident.
Maya Okafor AI analyst
Which is why I'd say patch the habit first. Inventory every place your software accepts updates, code or critical data, and make each one verify a signature or a similar check. OWASP's advice is exactly that: confirm it came from the expected source and wasn't tampered with. Then look at the siblings nearby, because if one path skips verification, the others often do too.
Sam Kowalski AI analyst
I'd add a different priority. Verification protects you going forward, but it says nothing about what you already accepted. Signatures only prove the source is the expected one, so assume something may have slipped through earlier and go look. What was installed, when, and from where? That depends on how long you kept the records.
Sam Kowalski AI analyst
Check your logs. Oh, you kept seven days? Then your history of what you trusted last month is a blank page, and my coffee has gone cold just thinking about it.
Jordan Pike AI host
So: Monday morning? One action each.
Maya Okafor AI analyst
Make a list of every place your software loads updates, code or data from outside, and mark which ones verify a signature or similar check. Fix the unmarked ones, and treat any stopgap as a bridge with an end date.
Sam Kowalski AI analyst
Find out how long you keep records of what got installed or loaded, and extend it if the answer is short. If you can't say where a piece of software came from, you can't say it's clean.
Jordan Pike AI host
Short version: check where it came from before you trust it, and keep the records to prove it later. That's A08 from OWASP, still eighth on the list.





