Source network being monitored partially mitigated
THREAT136
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:2339
- Risk
- Medium impact × Medium likelihood = 6 medium
- After mitigations
- Medium impact × Medium likelihood = 6 medium (unchanged)
An attacker seeks if a user on their network is a potential SecureDrop source. Source may access securedrop.org or news organization's SecureDrop landing page (particularly if it's hosted on a separate subdomain), which may raise suspicion. Furthermore, the use of Tor can be detected, and in some locations may raise suspicion.
Threat actors: Nation State / Law Enforcement Large Corporation Source error
Mitigations
| Mitigation | Status |
|---|---|
| Source interface only available as a Tor onion service MITIG54 | implemented |
Possible further mitigations
- Sources instructed to use a non-monitored network (e.g. coffee shop) for Tor activity MITIG156 proposed
Residual risk
Tor does not hide the fact one is using Tor.
Where it applies
Applies to 1 component in 1 scenario.
Source discovery and OPSEC · Source environment
Notes
Existing mitigations: The Tor network should provide secrecy of links visited through the Tor browser (MITIG54). Further mitigations: Source guide should include recommendation to use a public network (e.g. coffee shop), use Tails whenever possible (MITIG156). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.