Firewall rule misconfiguration on application server partially mitigated
THREAT31
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:541
- Risk
- High impact × Medium likelihood = 9 high
- After mitigations
- Low impact × Medium likelihood = 3 low
Intentional or accidental configuration of the application server firewall rules may introduce vulnerabilities in the Application Server.
Threat actors: Administrator error
Mitigations
| Mitigation | Status |
|---|---|
| Use of Ansible for configuration management for servers MITIG61 | implemented |
| Use of external dedicated hardware firewall MITIG21 | implemented |
Possible further mitigations
- Instruct admins not to modify config by hand MITIG62 proposed
- securedrop-admin script to audit config of running servers MITIG65 proposed
Residual risk
Administrator error or omission
Where it applies
Applies to 1 component in 1 scenario.
Physical and host layer · Application Server (host)
Notes
Existing mitigations: All SecureDrop infrastructure is provisioned via infrastructure-as-code (Ansible scripts). (MITIG61), presence of hardware firewall provides defense-in-depth (MITIG21). Further mitigations: Instruct Administrators to not modify by hand the configuration of the SecureDrop Application server (MITIG62). Develop a Securedrop-admin audit script which audits the current running configuration of Application server security-critical services (MITIG65). Automated test for mitigation: Yes.
How this threat is matched
Listed for these components. A boundary covers every component inside it.