Source googles for SecureDrop, clicks on link on Twitter, or other metadata trail accepted
THREAT163
· Accepted: The team has decided to live with this risk.
· Defined in catalog.py:2803
- Risk
- High impact × High likelihood = 12 high
- After mitigations
- High impact × High likelihood = 12 high (unchanged)
Even if a source does not discuss SecureDrop/leaking documents, a source may accidentally generate a metadata trail via their web browsing activity, e.g. via a Google search (search results were used in the Reality Winner trial)
Threat actors: Nation State / Law Enforcement Large Corporation
Mitigations
No mitigations in place.
Residual risk
By the time we can inform these users about these risks, the damage is likely already done.
Where it applies
Applies to 1 component in 1 scenario.
Source discovery and OPSEC · Source environment
Notes
Existing mitigations: None. Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.