Application-server DDoS accepted
THREAT148
· Accepted: The team has decided to live with this risk.
· Defined in catalog.py:2546
- Risk
- Medium impact × High likelihood = 8 high
- After mitigations
- Medium impact × High likelihood = 8 high (unchanged)
An attacker may leverage application functionality to disrupt/degrade application/server performance.
Threat actors: Troll
Mitigations
No mitigations in place.
Possible further mitigations
- Benchmark / load test SecureDrop application - through Tor and without MITIG192 proposed
- CAPTCHA for SecureDrop submissions MITIG137 proposed
Residual risk
No mitigations implemented.
Where it applies
Applies to 1 component in 2 scenarios.
Source submission · Source Interface
Supply chain and dependencies · Source Interface
Notes
Existing mitigations: The only functionality that may be resource intensive is the GPG encryption for submissions but throughput offered by Tor is likely not sufficient to significantly degrade server performance. Further mitigations: Benchmark/load test application (e.g.: https://github.com/locustio/locust) server to measure involvment necessary for DDoS (MITIG192). Implement CAPTCHA for submissions (MITIG137). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.