The password-protected ZIP is the unofficial standard of business security theater: compress, encrypt, email the archive, text the password, hope nobody forwards either message.
This guide compares ZIP/PDF passwords vs a zero-knowledge sealed vault so teams can retire a habit that feels safe and still fails audits, deals, and incident reviews.
What ZIP passwords optimize for
- Works offline with tools people already have
- No new account for the recipient (sometimes)
- Slightly better than a bare attachment
Those are real benefits for casual one-offs. They are not a document sharing control plane.
Where ZIP workflows break
- Password delivery — usually rides email or chat beside the file
- No revoke — copies persist on disks, sync folders, and backups
- No expiry — last year’s diligence ZIP still opens
- Weak evidence — you cannot show who opened what when
- Forwarding — ZIP + password become a portable kit
What a sealed vault optimizes for
- Client-side encryption before upload
- Share links with expiry, optional password, view limits
- Revoke for future opens when the engagement ends
- Exportable access activity for reviewers
Compliance Locker is designed for that model. Details: Security. It is not a claim that no one can ever mishandle a downloaded file.
Side-by-side
| Need | ZIP + password | Sealed vault link |
|---|---|---|
| Stop future access | No | Revoke / expire |
| Default time box | Manual (rarely done) | Built into the share |
| Access evidence | Inbox folklore | Exportable activity |
| Operator plaintext | N/A (file in email) | Designed for ciphertext at rest |
| Offline casual share | Convenient | Link + browser decrypt |
Migration script for teams stuck on ZIPs
- Ban ZIP+password for board, diligence, IR, and customer evidence
- Keep ZIP only for explicitly low-sensitivity one-offs
- Replace email attachments with sealed links—see stop emailing attachments
- Publish expiry defaults—see share expiry policy
FAQ
Is a password-protected ZIP encrypted?
Often yes for the archive contents—but encryption strength, implementation quality, and password handling vary. The bigger business failure is usually operational: password in the same email, no revoke, no expiry, no access evidence.
When is a ZIP still acceptable?
Low-stakes one-offs between two people who already have a secure password channel—and you accept that you cannot cleanly revoke or prove opens later. It should not be your standing policy for diligence, board, or IR packets.
What about password-protected PDFs?
Same class of tradeoff as ZIPs: better than bare attachments, weaker than sealed links with expiry, revoke, and activity export.
Can recipients decrypt ZIPs offline forever?
Yes—once they have the file and password, they keep a copy. Sealed vault links can expire or be revoked for new opens; they cannot erase every prior download, but they stop the “forever open folder” pattern.
Does Compliance Locker replace ZIP encryption?
For B2B packet sharing, yes—that is the job. Encrypt in the browser, share a controlled link, export activity when asked. See Security for the trust boundary.
Related: client-side vs server-side encryption, what zero-knowledge means.