USB transfer device malware compromises SVS mitigated Legacy (Tails/SVS)
THREAT129
· Mitigated: Controls in place bring the risk down to an acceptable level.
· Defined in catalog.py:2221
- Risk
- High impact × Low likelihood = 6 medium
- After mitigations
- High impact × Low likelihood = 6 medium (unchanged)
Potentially comprimising SVS airgap
Threat actors: Nation State / Law Enforcement
Mitigations
| Mitigation | Status |
|---|---|
| Use of airgapped SVS key MITIG10 | implemented |
| SecureDrop install guide explains that physical hardware like speakers, microphones, network devices should be removed from airgap MITIG152 Legacy (Tails/SVS) | implemented |
Possible further mitigations
- Transfer devices should be regularly sanitized - e.g. after each use. MITIG154 Legacy (Tails/SVS) proposed
Where it applies
Applies to 1 component in 1 scenario.
- Transfer Device Legacy (Tails/SVS)
Transfer & decrypt Legacy (Tails/SVS) · Transfer Device
Notes
Existing mitigations: SVS is airgapped (MITIG10). Admin guide states that radios and unecessary hardware be removed/disabled from the SVS (MITIG152). Further mitigations: Transfer devices should be regularly sanitized. Admin should be be instructed to schedule regular Transfer Device maintenance (wiping, passphrase change on personnel changes) (MITIG154). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.