Source reveals that they are using securedrop/leaking documents partially mitigated
THREAT76
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:1339
- Risk
- High impact × Medium likelihood = 9 high
- After mitigations
- High impact × Low likelihood = 6 medium
A source may inadvertently discuss leaking in a way that may compromise a source's operational security.
Threat actors: Nation State / Law Enforcement Large Corporation Troll
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
Source error or omission
Where it applies
Applies to 1 component in 1 scenario.
Source discovery and OPSEC · Source environment
Notes
Existing mitigations: Securedrop source guide states that users should not discuss whistleblowing activities as do many landing pages (MITIG42, MITIG86). Further mitigations: Source interface should be updated with operational security guidelines to strongly discourage discussing about leaking either publicly or privately (MITIG85). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.