PDF offers multiple security mechanisms, but they're widely misunderstood. An owner-only permissions password relies on reader enforcement. An opening password with modern AES encryption can protect confidentiality, but its strength also depends on the password, implementation and handling of decrypted copies. This guide explains what actually protects your data.
Two Types of PDF Passwords
PDFs support two distinct passwords, each with very different security properties:
| Feature | User Password (Open Password) | Owner Password (Permissions Password) |
|---|---|---|
| What it does | Requires an opening or owner password to decrypt | Restricts actions (print, copy, edit) but allows viewing |
| Security level | Strong — content is encrypted | Reader-enforced restrictions — encrypted content can open with an empty user password |
| Can be bypassed? | Depends on password strength, encryption and implementation | Trivially removed by many tools |
| Use case | Confidential documents that must not be viewed without authorization | Discouraging casual copying/printing (not security) |
PDF Encryption Algorithms
PDF has used several encryption algorithms over its history:
| Algorithm | PDF Version | Key Length | Current Status |
|---|---|---|---|
| RC4 | PDF 1.1+ | 40-bit | Obsolete; 40-bit keys are vulnerable to brute force |
| RC4 | PDF 1.4+ | 128-bit | Obsolete; use modern AES instead |
| AES | PDF 1.6+ | 128-bit | Secure for most purposes |
| AES | PDF 1.7 extensions and PDF 2.0 | 256-bit | Strong — current best practice |
Use a current, maintained encryption implementation and a strong opening password when encryption is appropriate. AES-256 may be suitable, but algorithm labels alone do not establish policy compliance. Legacy compatibility, password strength, encryption revision and the recipient’s requirements need review; no universal minimum is prescribed here.
Redaction: Removing Sensitive Content
Redaction is the permanent removal of content from a PDF. Done wrong, it's a security disaster. Done right, it's irreversible.
What Proper Redaction Does
- Permanently removes the text or image from the PDF's internal data streams
- Replaces the redacted area with a solid black (or colored) rectangle
- Removes the underlying character data so copy/paste and search return nothing
- Requires a separate sanitization check for metadata, attachments and other copies of the content
What Fake "Redaction" Looks Like
These common mistakes look like redaction but leave the original content fully intact:
- Black highlight — using a highlight annotation in black. The text is still there underneath; select-all + copy reveals it.
- Black rectangle annotation — drawing a shape on top. The original content is untouched in the page stream.
- Black text box overlay — adding a text box filled with black. Removing the annotation reveals everything.
- Screenshot and paste — taking a screenshot and pasting it over the sensitive area. If the original still exists in the layer below, it can be extracted.
Digital Signatures
Validating a digital signature checks two related properties:
- Authentication — the signature was made with the key associated with a certificate; identity assurance depends on certificate issuance and trust validation.
- Integrity — the signed bytes are unchanged; later appended revisions and permissions must also be examined.
Key facts about PDF digital signatures:
- They cover a specific byte range of the PDF. Changing signed bytes invalidates the signature; an incremental revision can preserve those bytes, but must respect certification permissions and signature locks.
- Multiple signatures are supported — each covers the state of the document at the time it was signed.
- They are NOT encryption — signing alone does not provide confidentiality. A signed PDF can also be encrypted.
- Tools that rewrite a signed PDF, including this suite's merge, split, rotate and watermark tools, do not preserve a valid signature. Verify signatures and permitted revisions in a signature-aware reader.
Watermarks as Security
Watermarks serve a deterrent function, not a security function:
- Visible watermarks — text like "CONFIDENTIAL" or "DRAFT" across the page. These discourage casual sharing and help identify leaked documents, but can be removed by anyone with a PDF editor.
- Dynamic watermarks — include the recipient's name or email in the watermark, to help identify which copy was shared. These marks are not conclusive proof of who disclosed it.
- Invisible watermarks — hidden data in the document structure for forensic tracking. Sophisticated but not standardized in PDF.
Security Best Practices
- Use user passwords + AES-256 for confidential documents
- Use proper redaction tools — not black rectangles or highlights
- ✓ Verify redaction by inspecting rendered pages, extracted text, metadata and attachments. A text-editor search of compressed or encoded PDF bytes is not a reliable check
- Apply digital signatures after all other edits (merge, rotate, watermark) are complete
- Use strong passwords — at least 12 characters with mixed case, numbers, and symbols
- Don't rely on owner passwords for actual security
- Don't use 40-bit or 128-bit RC4 encryption
- Don't assume a watermark prevents copying
- Don't skip verification before sharing redacted documents
Summary
| Protection | Purpose | Strength |
|---|---|---|
| User password + AES-256 | Prevent unauthorized opening | Strong |
| Owner password | Discourage printing/copying | Weak (easily bypassed) |
| Proper redaction | Permanently remove sensitive content | Strong (irreversible) |
| Digital signature | Prove authenticity and integrity | Strong |
| Watermark | Deterrent and leak tracing | Weak (removable) |