Verifying Document Authenticity with Watermarks

Document Integrity Through Steganographic Watermarks

Organizations that issue certificates, transcripts, or official documents as images can use LSB watermarks to create a built-in verification mechanism that is invisible to the naked eye but machine-readable.

The Authenticity Problem

Digital documents are trivially editable. A scanned certificate image can be altered with basic photo editing software to change names, dates, or grades. Traditional solutions (holograms, special paper) do not apply to digital copies.

Steganographic Solution

Embed a verification payload that includes:

{
  "issuer": "University of Example",
  "recipient": "John Smith",
  "documentType": "Bachelor's Degree",
  "issueDate": "2025-06-15",
  "documentHash": "sha256:e3b0c44298fc1c14...",
  "verificationURL": "https://verify.example.edu/doc/12345"
}

Verification Workflow

1. Issuer generates the document image
2. Issuer embeds the JSON payload using a private encryption key
3. Issuer distributes the watermarked image
4. Verifier receives the document and uses the extraction tool with the shared key
5. Verifier compares extracted data against the visible document content
6. Any mismatch indicates tampering

Tamper Detection

If someone modifies the visible content of the document (e.g., changes a name), the embedded watermark still contains the original data. The discrepancy between visible content and extracted watermark proves the document was altered.

Important Limitations

• The watermark survives only in the original PNG file
• Printing and re-scanning the document will destroy the watermark
• Screenshots may alter pixel values enough to corrupt the data
• This method works best for digital-native document workflows

Integration with Existing Systems

The verification payload can include a URL pointing to the issuer's online verification database. This creates a two-factor check: the embedded data must match both the visible document and the issuer's records.