Software and Data Integrity Failures (New in 2021)
You'll learn: Why OWASP created a new category to address modern supply chain, CI/CD, and deserialization threats that weren't adequately covered before.
What This New Category Covers
In 2021, OWASP recognized that applications increasingly rely on external code, automated pipelines, and complex data flows—creating new attack surfaces. Software and Data Integrity Failures consolidates risks where applications fail to verify that code, infrastructure, or data hasn't been tampered with.
This category bundles three major threat areas:
1. Insecure Deserialization (Promoted)
You've already studied how deserializing untrusted data can lead to remote code execution. This risk is now officially part of integrity failures because deserialization trusts that serialized objects haven't been maliciously modified.
2. CI/CD Pipeline Attacks
Modern applications deploy through automated build pipelines. If attackers compromise your build server, dependency repository, or deployment scripts, they can inject malicious code directly into production. Think of it like poisoning ingredients at a factory before products reach stores—the danger spreads everywhere.
3. Supply Chain Vulnerabilities
Applications depend on third-party libraries, frameworks, and components. If a dependency is compromised (malicious update, typosquatting package), your application inherits that vulnerability. Recent real-world attacks like SolarWinds demonstrated this threat's severity.
The Core Problem
The unifying theme: applications assume code and data sources are trustworthy without verification. No signature checking, no integrity validation, no security controls on what gets built or deserialized.
Key Takeaway: Software and Data Integrity Failures address the blind trust applications place in external code sources, build processes, and serialized data—demanding cryptographic verification, secure pipelines, and dependency monitoring to prevent supply chain and deserialization attacks.