Source activity is compromised via physical surveillance (e.g.: camera) partially mitigated
THREAT131
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:2254
- Risk
- Medium impact × Medium likelihood = 6 medium
- After mitigations
- Medium impact × Medium likelihood = 6 medium (unchanged)
An adversary may be able to leverage physical surveillance such as cameras to capture source keystrokes or observe source's computer screen.
Threat actors: Nation State / Law Enforcement Large Corporation
Mitigations
| Mitigation | Status |
|---|---|
| Guidelines for OPSEC in the landing page MITIG42 | optional |
| Source guide contains some OPSEC considerations MITIG86 | implemented |
Possible further mitigations
- SecureDrop has default (but potentially customizable) text on source interface with post-Tor OPSEC information MITIG85 proposed
Residual risk
Landing pages don't all have this OPSEC information. Source guide is not particularly discoverable by sources.
Where it applies
Applies to 1 component in 1 scenario.
Source discovery and OPSEC · Source environment
Notes
Existing mitigations: Source guide and landing pages contain some information about OPSEC (MITIG42, MITIG86). Further mitigations: Source interface should provide further guidance on operational security (avoid cameras, physical surveillance for passwords and screen), talking about leaks or activity in public spaces (MITIG85). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.