Landing page DNS leaks from Securedrop/leaks-related subdomain inform
THREAT59
· Inform: Handled by telling users how to protect themselves.
· Defined in catalog.py:1043
- Risk
- Medium impact × High likelihood = 8 high
- After mitigations
- Medium impact × Medium likelihood = 6 medium
Should the SecureDrop landing page be hosted on a dedicated subdomain, it would be visible by observing DNS requests coming from the potential source
Threat actors: Nation State / Law Enforcement Large Corporation ISP
Mitigations
| Mitigation | Status |
|---|---|
| Landing page subdomains discouraged MITIG160 | implemented |
Possible further mitigations
- Landing page scanner detects subdomains, warnings shown on directory MITIG161 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 guide recommends against the use subdomains for landing pages (MITIG160). Further mitigations: Landing page scanner can detect subdomains. Reinforce the suggestion and make landing page scan information public (MITIG161). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.