{
  "slug": "data-integrity",
  "term": "Data integrity",
  "aliases": [],
  "definition": "Data integrity is the property that data has not undergone unintended or unauthorized alteration, destruction or loss.",
  "note": "Scope: Integrity concerns preservation of data, not whether the original values were true. A faithfully stored incorrect measurement can remain unchanged. State the protected data, allowed changes and observation boundary. [nist-integrity] [rfc4949]\n\nStorage checks: A checksum over a block can match an old block after a lost write. Identity and version checks answer different questions, and detecting a mismatch does not establish successful recovery. These distinctions are explicit in a model of single-error RAID protection. [parity]\n\nTrust: A mechanism intended to detect accidental errors does not necessarily protect against deliberate modification. If an attacker can replace both data and an unkeyed digest, a matching result does not establish authenticity. [rfc4949]\n\nUse: Durability describes preservation over time and specified failures; availability describes access. Those goals overlap with integrity but do not replace a check that the returned object has the expected identity and state. [hesela-integrity]\n\nResearch boundary: FAST 2026 distinguishes a direct-I/O userspace PI interface from experimental filesystem-managed PI; the latter is not established as generally available by the paper. [linux-pi2026]",
  "related": [
    "checksum",
    "silent-data-corruption",
    "data-durability",
    "storage-availability",
    "metadata",
    "end-to-end-data-protection",
    "lost-write",
    "message-authentication-code"
  ],
  "citations": [
    {
      "id": "nist-integrity",
      "title": "NIST CSRC glossary: data integrity; definitions and source attribution.",
      "url": "https://csrc.nist.gov/glossary/term/data_integrity",
      "accessed": "2026-11-15"
    },
    {
      "id": "rfc4949",
      "title": "RFC 4949: data integrity, data integrity service and checksum entries (Informational glossary).",
      "url": "https://www.rfc-editor.org/rfc/rfc4949.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "parity",
      "title": "Krioukov et al. Parity Lost and Parity Regained. FAST 2008, sections 2.3 and 4.3-4.6.",
      "url": "https://www.usenix.org/legacy/event/fast08/tech/full_papers/krioukov/krioukov_html/main.html",
      "accessed": "2026-11-15"
    },
    {
      "id": "hesela-integrity",
      "title": "Hesela: Why a valid checksum can still return the wrong data.",
      "url": "https://hesela.com/analyses/checksums-identity-and-lost-writes/",
      "accessed": "2026-11-15"
    },
    {
      "id": "linux-pi2026",
      "title": "Gupta et al. Advancing Data Integrity in Linux. FAST 2026, sections 5.2, 6.1 and 8.",
      "url": "https://www.usenix.org/system/files/fast26-gupta.pdf",
      "accessed": "2026-11-15"
    }
  ],
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-15",
  "provenance": [
    "Terminology synthesis, not a storage certification. NIST lists context-dependent definitions; RFC 4949 is Informational and its terminology recommendations are the author's, not an IETF standard.",
    "The FAST 2008 examples concern the paper's stated model; no new device experiment or failure-rate measurement is reported."
  ]
}
