Monitor server configuration error partially mitigated
THREAT65
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:1140
- Risk
- High impact × Medium likelihood = 9 high
- After mitigations
- Medium impact × Medium likelihood = 6 medium
Intentional or accidental configuration of the monitoring server (firewall rules, ossec rules, ssh config, postfix config) may introduce vulnerabilities in the Monitoring Server. Administrators may not notice that the monitor server is down.
Threat actors: Administrator error
Mitigations
| Mitigation | Status |
|---|---|
| Use of Ansible for configuration management for servers MITIG61 | 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 · Monitoring Server (host)
Notes
Existing mitigations: All SecureDrop infrastructure is provisioned via infrastructure-as-code (Ansible scripts). (MITIG61). Further mitigations: Instruct Administrators to not modify by hand the configuration of the SecureDrop monitor server (MITIG62). Develop a Securedrop-admin audit script which audits the current running configuration of monitor 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.