Why this matters
Protecting the laboratory and computing chain: sequencers, LIMS, bioinformatics pipelines, reference datasets, storage, and cloud services. Evaluate the particular asset, access pathway, affected parties, and evidence before assigning a risk classification. These are analytical controls to consider, not a claim that every organization faces the same exposure.
Sequencers and laboratories
Inventory instruments, owners, service accounts, remote maintenance paths, and connections to analysis networks.
LIMS and custody
Link specimen identity to the right subject and record transfers, exceptions, operators, and authorized purposes.
Bioinformatics and reference data
Record tool versions, parameters, container digests, input checksums, and reference versions so results can be reconstructed.
Cloud and storage
Separate permissions for raw data, derived outputs, and exports. Review service identities and test restoration from isolated backups.
The handoff is part of the system
A genomic workflow crosses physical and digital boundaries. Staff label a specimen, an instrument produces files, software transforms those files, and an analyst interprets the output. A failure can begin at one stage and remain invisible until someone relies on the final result.
For a hypothetical sample mix-up, perfectly functioning software may process the wrong person's material. File encryption will not resolve the association error. Conversely, a correctly labeled sample can produce data that is later changed or assigned to the wrong record. Review the links between identifiers, files, and reports rather than assuming each team has covered the gaps.
Make a result reconstructable
Choose one completed analysis and ask a colleague to trace it backward. Can they find the original inputs, the reference version, the workflow parameters, and the identity of the person who approved the interpretation? Could they distinguish a corrected result from an earlier report?
This is a practical review exercise, not a requirement to retain every temporary file forever. Decide what evidence is necessary to reproduce or explain a result, how long it should be kept, and how access will be restricted. Excess retention creates its own exposure, so preservation decisions need a purpose.
Recovery should include a trust check
An available file is not necessarily a trustworthy file. In a recovery exercise, check that restored data matches the intended version and remains linked to the correct specimen and analysis. Record any gaps rather than silently treating an incomplete restoration as normal operation.
Include people in the exercise: who can authorize restarting the workflow, who reviews uncertain outputs, and who informs downstream users if a report must be corrected? The technical recovery and the decision to trust its results are related, but they are separate steps.
Core definitions
- Genetic Exposure Radius — Scope of relational exposure
- Genetic Persistence Risk — Durability after compromise
- Genetic Provenance Integrity — Verifiability of the chain of custody
Reference framework
- PRIMARY SOURCE NIST: Genomic Data Threat Modeling