Monitor server is seized partially mitigated
THREAT152
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:2615
- Risk
- Medium impact × Low likelihood = 4 medium
- After mitigations
- Medium impact × Low likelihood = 4 medium (unchanged)
SecureDrop monitor server is seized by and adversary. A compromised monitor server could silence alerts in the case of a real attack against the Application server.
Threat actors: Nation State / Law Enforcement
Mitigations
| Mitigation | Status |
|---|---|
| OSSEC logs do not contain sensitive information. MITIG148 | implemented |
Possible further mitigations
- FDE on app/mon servers MITIG134 proposed
- Support SecureDrop raid kill switch: Turn off / disable servers MITIG191 proposed
Residual risk
Candidate for further mitigation efforts.
Where it applies
Applies to 1 component in 1 scenario.
Physical and host layer · Monitoring Server (host)
Notes
Existing mitigations: OSSEC information (logs, alerts and integrity monitoring) does not contain sensitive information (MITIG148). Further mitigations: FDE on the server (MITIG134). Support SecureDrop kill switch: for example, have both servers plugged into managed power device to turn off power to server in case of raid. Admins use Haven or similar to monitor the servers and if LE activity is detected, they kill the servers remotely. (MITIG191). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.