Insights
Zero trust file sharing: permissions beyond a private connection
Learn how zero trust file sharing checks identity and permissions, then review a share's access, expiry and download controls.

On this page
Zero trust file sharing checks who or what is requesting access and what they're allowed to do with a specific file. You don't get permission just because you're on a private network. It combines identity checks, limited permissions, encryption and access monitoring, while control over downloaded copies needs separate support.
In short:
- Check identity and permission. A private connection doesn't grant access to a file.
- Limit each share. Give recipients only the files and actions they need.
- Check download controls. Revoking a sharing link doesn't remove an ordinary downloaded copy.
A private connection isn't file permission
Authentication checks identity: who is requesting access? Authorization checks permission: may that identity view, edit or download this file? A zero trust approach makes both checks instead of treating network membership as permission.
Imagine a colleague on the same private network as you. They still need permission for the file they're requesting, even if the connection is private. Zero trust is an approach to making access decisionsOpens in a new tab, not a product label or one setting you switch on.
The checks that control a share
Check people and services
Use identity checks for each person, application or automated service that needs access. Multi-factor authentication (MFA) uses more than one type of proof of identity and can strengthen appropriate human access. An automated service needs its own limited identity and permissions, not unrestricted use of your account.
Access decisions can also use relevant device, network and behavior information. These checks don't mean you must manually sign in for every file operation. Check how your tool evaluates access and responds when that information changes.
Limit file permissions
Least privilege means giving only the access needed for the task. Viewing, editing, downloading and resharing are different actions, so check which ones your tool can control separately. Permission to read one document shouldn't automatically become permission to change an entire folder.
For sensitive files, look for documented view-only access, download restrictions and approval for external sharing. Expiring or revocable links can limit later access through the sharing service. Keep administrative privileges separate from routine file-processing permissions.
Review access over time
Remove access promptly when the recipient no longer needs it. Review available records of authentication, permission decisions and file activity to check whether access matches your policy. Access records help you review what happened, but they aren't a substitute for enforcing permissions.
What happens after someone downloads a file
Link expiry and revocation govern later access through the sharing service. They don't remove an ordinary decrypted copy already delivered to a recipient. A Fortra datasheetOpens in a new tab notes that files can still be shared with unauthorized recipients after download and decryption.
Some file-protection systems document controls that remain attached to protected files. Fortra, for example, documents expiry and revocation for Digital Guardian Secure Collaboration-protected files. That's a claim about specially protected files, not every downloaded copy. Check the documented behavior for your file type and recipient workflow before relying on post-download revocation.
Encryption protects confidentiality within its documented scope. It doesn't determine whether the recipient, destination or file contents are safe. You still need identity, permission, destination and content checks suited to the risks of the share.
Check one share before sending it
Suppose a contractor needs to view one project document, not edit a whole folder. Record the file's sensitivity, intended recipient, allowed actions, destination and access deadline. Use the sharing tool's documented controls to work through these checks.
Run sample permission checks only on systems you own or administer, using accounts you're authorized to test. Preserve the original settings so you can restore them if a change breaks access.
-
Confirm the recipient's identity. Name the exact account that should receive access and check how the tool authenticates it. A familiar display name isn't your access policy.
-
Limit the file and actions. Grant access to the needed document, not the whole folder. Check whether viewing, editing, downloading and resharing can be controlled separately. If download blocking is required, confirm that the chosen method supports it.
-
Check the destination. Confirm that the share goes to the approved recipient and destination. Review any folder permissions or link audience that could make it available more widely.
-
Choose an access deadline. Record when access should end and how you'll remove it. Where supported, set expiry or revocation. If your policy requires automatic expiry, confirm that the tool can enforce it before sharing.
-
Find the access records. Check which records are available for authentication, permission decisions and file activity. Decide who can review them and whether they give you enough information to assess this share.
-
Check control after download. Determine whether revocation affects only future access through the service or also specially protected downloaded files. Don't treat link expiry as control over an ordinary decrypted copy.
-
Try a nonsensitive sample. Check that the intended account can perform the allowed action. Also check that an unauthorized account is denied and that prohibited actions are blocked where the tool supports those restrictions.
You should be able to name who may access the file, what they may do, when access ends and what control remains after download. A successful sample access check proves only that the tested identity and action work. Unexpected access means permissions need review before sensitive sharing. A small sample check doesn't prove that every access path enforces the same policy.
Where doxx.net fits. doxx.net's private network offers direct device-to-device connectionsOpens in a new tab and full, unmodified file transfer, but those capabilities alone don't establish per-file permissions or post-download control. You can create an account, download the app and connect a deviceOpens in a new tab to use the private network.