User web traffic to SecureDrop landing page is logged inform
THREAT60
· Inform: Handled by telling users how to protect themselves.
· Defined in catalog.py:1061
- Risk
- Medium impact × High likelihood = 8 high
- After mitigations
- Medium impact × Low likelihood = 4 medium
Web access logs are intentionally or unintentionally stored by an organization or their hosting provider. Logs of SecureDrop landing pages may yield a small pool of potential sources that could be de-anonymized if they use their personal devices and networks.
Threat actors: Any
Mitigations
| Mitigation | Status |
|---|---|
| No logging on landing page MITIG183 | implemented |
Possible further mitigations
- Onion URL on every page of news organization website MITIG184 proposed
- Cover traffic generated to SecureDrop landing pages via embed loaded on every page load MITIG185 proposed
Residual risk
Administrator error or omission
Where it applies
Applies to 1 component in 1 scenario.
Source discovery and OPSEC · Landing page
Notes
Existing mitigations: Landing page deployment requirements: no logging on the landing page (MITIG183). Further mitigations: SecureDrop onion URL could be displayed on the main newspaper landing page (MITIG184). Random traffic to the SecureDrop page could be generated on the homepage (e.g. invisible frame, JS ...) to maximize quantity and diversity (MITIG185). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.