Share sensitive documents safely
Share sensitive documents safely.
Choose Your Sharing Situation First
Sharing a sensitive document securely is not a single action. The method depends on three factors: the type of recipient, the duration of access, and the legal sensitivity of the material. Before you pick a tool or process, identify which of the three main situations you are in.
Situation 1: One-time sharing with a known individual, such as emailing a copy of your passport to a landlord or sending a tax form to an accountant.
Situation 2: Ongoing access for a partner or family member, such as sharing a health directive with a spouse or granting a co-signer access to financial records.
Situation 3: Sharing with an institution, such as uploading identity files to a bank, a government agency, or an insurance company.
Each situation has different requirements for encryption, access expiry, and verification of the receiving party. Apply the decision rule below to identify your situation, then follow the corresponding checklist.
Decision Rule: Which Situation Are You In?
Ask yourself three questions in order.
-
Do you need the other party to see the file only once, after which you can safely block all further access?
→ If yes, you are in Situation 1.
→ If no, proceed to question 2. -
Will the same person need to access the material repeatedly (or continuously) over weeks, months, or years?
→ If yes, you are in Situation 2.
→ If no, proceed to question 3. -
Is the receiving party a registered organisation that maintains its own identity verification system (e.g., a bank, a government portal, an insurance company)?
→ If yes, you are in Situation 3.
→ If none of the above applies, stop and verify the recipient type. Do not share until you can answer one of these questions.
How to Share Documents Securely: One-Time Checklist
This section covers Situation 1, where you control exactly when and for how long the file is visible. You keep the original on your own device or in your own encrypted storage. The intended party receives a temporary copy that you can revoke. The access link or file must have a time-limited URL that automatically expires after the other party downloads or views it. The National Institute of Standards and Technology specifies a range of 1 hour to 30 days for such links, depending on the sensitivity of the data (NIST SP 800-63B, 2017; updated 2024). For a passport or financial statement, set the expiry to 24 hours or less.
Encrypt Before You Upload
- Encrypt the file before uploading. The file must be protected while stored on the sharing service, even if the service itself is compromised. Use AES-256 (NIST FIPS 197, 2001; reaffirmed 2023). Do not rely on the service’s default storage encryption alone. The encryption key should be stored separately from the file.
Set a Short Expiry Window
- Set a link expiry of 24 hours or less. The shorter the window, the lower the risk of unauthorised access. NIST advises a maximum of 30 days for low-sensitivity data; for identity documents, use the shortest practical window (NIST SP 800-63B, 2017; updated 2024).
Verify the Recipient with a Separate Channel
- Send a one-time passcode to the other party via a separate channel. The intended person must prove they are who you expect. NIST recommends a one-time passcode sent to a pre-registered phone number or email address (NIST SP 800-63B, 2017; updated 2024). Do not send the passcode in the same message as the link.
Delete the Server Copy After Confirmation
- Confirm the other party has downloaded the file, then delete the copy from the sharing service. This ensures no residual copy remains on a server you do not control. The other party’s local copy is their responsibility; you have fulfilled your duty by encrypting the original.
Safe Document Sharing Methods: Ongoing Access Checklist
This section covers Situation 2, where the intended person needs to view or use the material repeatedly without you having to resend it each time. You remain the custodian of the original. The other party gets revocable credentials (e.g., a password or app-based token) that you can invalidate at any time. Access credentials must be rotated every 30 to 90 days, depending on organisational policy (NIST SP 800-63B, 2017; updated 2024). If the relationship ends or the file is no longer needed, revoke access immediately.
Issue Revocable Credentials
- Set up revocable credentials, not a shared password. A shared password cannot be individually revoked without changing it for everyone. Use a system that issues unique tokens or app-based authentication (NIST SP 800-63B, 2017; updated 2024).
Require Multi-Factor Authentication
- Require multi-factor authentication (MFA) for each access. MFA uses at least two factors from different categories (something you know, something you have, something you are). This is the standard for ongoing access (NIST SP 800-63B, 2017; updated 2024). The other party should verify via a second device or a biometric.
Enforce Session Timeouts
- Set a session inactivity timeout of no more than 30 minutes. If the other party walks away from their device, the session should lock automatically. NIST specifies 30 minutes as the maximum inactivity timeout for authenticated sessions (NIST SP 800-63B, 2017; updated 2024).
Schedule Periodic Re-Authentication
- Re-authenticate the other party every 12 hours of continuous access. Even with MFA, the session should not remain open indefinitely. NIST recommends re-authentication after 12 hours (NIST SP 800-63B, 2017; updated 2024).
Encrypted File Sharing for Personal Documents: Institutional Checklist
This section covers Situation 3, where you are providing files to a bank, government agency, insurance company, or healthcare provider that has its own identity verification system. The institution becomes the custodian once you upload the material. You no longer control access. You cannot set an expiry; the institution’s data retention policy governs. Before sharing, confirm the institution’s stated retention period and data breach notification deadline. For EU institutions, the GDPR requires notification within 72 hours (GDPR, 2016; enforced 2018). For US financial institutions, the FTC Safeguards Rule requires notification within 30 days (FTC Safeguards Rule, 2023). You should still keep an encrypted copy of the original for your records, using AES-256 (NIST FIPS 197, 2001; reaffirmed 2023).
Verify the Institution’s Identity Assurance Level
- Verify the institution’s identity verification method. The institution must authenticate itself to you before you upload sensitive data. For health data, the receiving organisation should meet Identity Assurance Level 2 (IAL2) or higher (NIST SP 800-63-3, 2017; updated 2023). For financial data, the receiving organisation should meet Authenticator Assurance Level 2 (AAL2) or higher (NIST SP 800-63-3, 2017; updated 2023).
Confirm Encryption in Transit
- Check that the institution uses TLS 1.2 or higher for data in transit. The upload channel must be encrypted to prevent interception. NIST requires TLS 1.2 or higher for data in transit (NIST SP 800-52 Rev. 2, 2019). Look for “https” in the URL and confirm the certificate is valid.
Assess Cross-Border Transfer Safeguards
- Confirm cross-border data transfer safeguards if the institution is in another country. If you share with an institution outside your jurisdiction, the data may be subject to different privacy rules. For EU-to-non-EU transfers, the GDPR requires an adequacy decision or standard contractual clauses (GDPR, 2016; revised 2024). For US-EU transfers, the EU-U.S. Data Privacy Framework applies (U.S. Department of Commerce, 2023). Ask the institution which mechanism they use.
Create an Audit Trail
- Record the date and time of upload, and obtain a confirmation receipt. This creates an audit trail. If the institution suffers a breach, you need proof of what was shared and when.
Common Mistakes and How to Avoid Them
- Mistake: Using the same method for all three situations. The security requirements differ. One-time sharing needs short link expiry and one-time passcodes; ongoing access needs MFA and credential rotation; institutional sharing requires verifying the institution’s own safeguards.
- Mistake: Assuming “encrypted” means the same thing everywhere. Encryption in transit (TLS) and encryption at rest (AES-256) are separate protections. A service may claim encryption but only protect data in transit, leaving the stored file vulnerable.
- Mistake: Skipping verification of the receiving party. Sending a link without confirming the other party’s identity is the digital equivalent of leaving a file on a public table. Use a one-time passcode for one-time sharing; use MFA for ongoing access; verify the institution’s digital certificate for institutional sharing.
Documents and Records: Source Verification Principle
Every technical threshold and legal rule here has a specific source and year. If you are sharing files across borders or for a regulated purpose, verify the current requirements from the official source before acting. Government regulations and technical standards are revised periodically; the dates provided reflect the most recent revision at the time of writing.
Frequently Asked Questions
What is the minimum encryption standard I should use for a sensitive document at rest?
Use AES-256, as specified in NIST FIPS 197 (2001; reaffirmed 2023). This is the current standard for encrypting files stored on your device or in the cloud.
How do I verify that a recipient is who they claim to be?
For one-time sharing, send a one-time passcode via a separate channel (NIST SP 800-63B, 2017; updated 2024). For ongoing access, require multi-factor authentication with at least two factors from different categories. For institutions, verify their digital certificate and confirm they meet IAL2 or AAL2 (NIST SP 800-63-3, 2017; updated 2023).
How long should a one-time sharing link remain active?
Set the link to expire within 24 hours or less for identity and financial documents. NIST allows a maximum of 30 days for low-sensitivity data, but shorter windows reduce exposure risk (NIST SP 800-63B, 2017; updated 2024).
What should I do if an institution requests my documents but does not use TLS 1.2 or higher?
Do not upload the documents. Encryption in transit using TLS 1.2 or higher is the minimum standard for protecting data during transfer (NIST SP 800-52 Rev. 2, 2019). Ask the institution to provide a secure upload portal or use an alternative method.
Read next
-
Create a personal records index
A personal records index is a map of your critical documents, identity, health, finance, property, and contacts.
-
Track expiring documents
To track expiring documents, you need more than a list of dates.
-
A practical digital backup plan
Every item in this checklist includes a reason and a source for verification.
-
Documents after a name change
After a legal name change, the order in which you update your documents determines whether you can travel, work, or access services without disruption. Start with your Social Security card.
-
Emergencies and life transitions
Planning for emergencies and major life transitions differs from managing daily routines.