#md:# Leaks usually happen during normal use
When you review file leakage incidents inside a company, most fall into three patterns: bulk downloads before someone leaves, files shared out and never recovered, and terminals anyone can copy from. None of them is an exploited vulnerability; they are missing constraints in the process.
Four design principles
- Least privilege: invisible by default, granted when needed, and approval required for important folders.
- Revocable sharing: share a link instead of an attachment, with a download limit and a kill switch.
- Traceable actions: who downloaded which revision and when must always be answerable.
- Visible traces: watermarked previews put a psychological cost on screenshots and forwarding.
Sequence for rollout
First list the high-value files, then define access and flow rules for each class of file, and only then fix those rules with tooling. The tool is the last step; without the earlier thinking it just becomes another shared drive.
Want these capabilities on your own servers?
A 30-day full-featured trial that you can stop at any time.