File Integrity Verification

Every transfer carries a quiet question: is the file that arrived the file that was sent? Most of the time the answer is yes — which is exactly why the rare no is so dangerous. Corruption and truncation hide until the backup won't restore or the batch won't post, long after the evidence is gone.

This series is about answering the question deliberately: hashes as file fingerprints, end-to-end verification workflows, checksum manifests that protect whole batches, where corruption actually comes from when it happens, building verification into automated jobs so they fail loudly at the moment of damage, and the boundary where integrity checking stops and authenticity — proving who sent it — begins.

Articles in This Series

• Hashes Explained: Fingerprints for Files
  What a hash is in plain words, why two different files won't share one, the common algorithm families, and what a matching hash does and doesn't prove.
• Verifying a Transfer End to End
  Hash before, hash after, compare — the workflows, the automation, and where verification belongs in each kind of pipeline.
• Checksum Files and Manifests for Batches
  Sidecar checksum files and batch manifests — formats partners understand, verification scripts, and conventions that scale past single files.
• Where Corruption Actually Comes From
  Transfer-mode mangling, truncation, disk and memory errors, and resume bugs — diagnosis by symptom, with the classic cases decoded.
• Building Integrity Checks into Automated Jobs
  Fail-closed design, retry-on-mismatch, alerting on verification failures, and logging the proof so nobody has to take your word for it.
• Integrity vs Authenticity: When a Hash Isn't Enough
  An attacker who alters the file can recompute the hash — why integrity needs authenticity for hostile scenarios, and the signed-hash bridge to digital signatures.

Explore More Topics

This series is part of the Sysax file transfer topic library, which covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build: Sysax Multi Server, a secure FTP, FTPS, SFTP, and HTTPS server for Windows, and Sysax FTP Automation, which schedules and scripts secure transfers so the routine ones run themselves.