Source searches for SecureDrop on search engines accepted
THREAT156
· Accepted: The team has decided to live with this risk.
· Defined in catalog.py:2686
- Risk
- Medium impact × Low likelihood = 4 medium
- After mitigations
- Medium impact × Low likelihood = 4 medium (unchanged)
Source browser searches, history or traffic contains mentions of SecureDrop or other SecureDrop related queries (e.g.: How to leak documents to $NEWS_ORG)
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
Risk currently unmanaged
Where it applies
Applies to 1 component in 1 scenario.
Source discovery and OPSEC · Source environment
Notes
Existing mitigations: OPSEC guidelines on landing page (MITIG42), source guide (MITIG86). Further mitigations: Explain OPSEC more in source interface itself (MITIG85). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.