App server (physical) tampering partially mitigated
THREAT107
· Partially mitigated: Some controls are in place, but the risk is still too high.
· Defined in catalog.py:1862
- Risk
- High impact × Low likelihood = 6 medium
- After mitigations
- High impact × Low likelihood = 6 medium (unchanged)
SecureDrop application server physical security is compromised
Threat actors: Nation State / Law Enforcement
Mitigations
| Mitigation | Status |
|---|---|
| Swap disabled on servers MITIG52 | implemented |
| AppArmor on Tor MITIG1 | implemented |
| AppArmor on Apache MITIG2 | implemented |
| Use of OSSEC monitoring software MITIG5 | implemented |
| Nighly reboot occurs to clear secrets stored in memory MITIG136 | implemented |
Possible further mitigations
- Physical monitoring, e.g. Haven MITIG135 proposed
- FDE on app/mon servers MITIG134 proposed
- Admin guide should speak clearly to physical security considerations MITIG115 proposed
Residual risk
Candidate for further mitigation efforts.
Where it applies
Applies to 1 component in 1 scenario.
Physical and host layer · Application Server (host)
Notes
Existing mitigations: Swap is disabled (MITIG52). AppArmor for mandatory access control (MITIG1, MITIG2), and ossec for file integrity monitoring (MITIG5). Memory is cleared on daily reboot (MITIG136). Further mitigations: Physical security/surveillance (e.g. Haven) (MITIG135), ping checks, full-disk-encryption (MITIG134), explain physical security in admin guide (MITIG115). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.