DNS requests to news organization's subdomain for SecureDrop landing page, freedom.press, torproject.org Tor activity, SD submissions may be correlated inform

THREAT73 · Inform: Handled by telling users how to protect themselves. · Defined in catalog.py:1285

Risk
High impact × High likelihood = 12 high
After mitigations
High impact × Medium likelihood = 9 high

How statuses and scores work

A motivated / resourceful adversary may be able to store, analyse and correlate DNS or HTTPS requests made to these domains and infer that the source may be interested in sharing documents

Threat actors: Nation State / Law Enforcement

Mitigations

Mitigation Status
Source guide contains some OPSEC considerations MITIG86 implemented
Guidelines for OPSEC in the landing page MITIG42 optional

Possible further mitigations

Residual risk

Administrator 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: https://docs.securedrop.org/en/stable/source.html (MITIG86) * Guidelines for OPSEC in the landing page (MITIG42). Further mitigations: Source guide should be updated to use Tor soon as possible in the process. Should also suggest the use of public networks to download Tor. Potential sources may also download Tor from GitHub: https://github.com/TheTorProject/gettorbrowser or via email by sending windows,osx or linux to gettor@torproject.org. In the latter case, users should be mindful of who their mail provider is. (MITIG89) SecureDrop has default (but customizable) text on source interface with post-Tor OPSEC information (MITIG85). * Source Guide should instruct used use Tails or TorBrowser (MITIG155). Automated test for mitigation: No.

How this threat is matched

Listed for these components. A boundary covers every component inside it.