Define the release decision
The primary laptop fails shortly before an application deadline. A recovery copy exists, but no one has verified its password, file version or readability.
Restore a separately stored copy before a deadline makes an untested backup a single point of failure.
Run the control sequence
- 01Run the drill with a fictional letter or authorized test copy.
- 02Retrieve the recovery copy without relying on the primary device.
- 03Open it using the documented recovery method; do not assume password reset decrypts an existing archive.
- 04Compare file name, date, size and checksum with the safe manifest.
- 05Record the result, gap owner and next test date.
Preserve enough evidence
Record the dataset identifier, application cycle, source device or system, export date, manifest, responsible custodian, authorized recommenders, key location, encryption environment, recovery result, retention rule and next review date. Do not put passwords, recovery secrets or unnecessary applicant values in the decision record.
Keep the manifest, custodian, approved recipient, key-separation decision, restore result and retention owner together without copying applicant values into the record.
Keep surrounding controls visible
A backup icon or cloud status is not evidence that the correct letter is complete, readable, current or recoverable.
Field conditions can create extra copies on tablets, laptops, removable media, synchronization folders and recipient devices. The archive owner must address those copies separately and verify the current software release before relying on product behavior.
Questions to ask
Should the access credential travel with the dataset?
Only when the approved research purpose requires linkage and the responsible owner has authorized the same recipient. Separation is a core risk control.
Does encryption make an export anonymous?
No. Encryption restricts file access; it does not remove identifiers or eliminate reidentification risk after decryption.
Primary references
References support specific controls and do not imply endorsement.