Checksum verification is the process of comparing a file or module’s cryptographic hash against a trusted expected value. If the hashes match, the content is likely unchanged; if they differ, the artifact may have been modified, corrupted, or replaced. In software supply chains, this is a basic integrity control.
It matters in cyber security because attackers often target dependencies, updates, and build artifacts rather than the application itself. Verifying checksums helps defenders detect tampering, accidental upload mistakes, and download interception. In practice, package managers and lock files use checksums to confirm that a retrieved module is the one that was approved. It is strong against unexpected changes, but it should be paired with provenance checks, signed releases, and access controls, because a matching hash only proves sameness to the trusted reference, not that the reference itself is safe.