Known vulnerabilities in the Linux kernel or packages used by app/mon servers mitigated
THREAT41
· Mitigated: Controls in place bring the risk down to an acceptable level.
· Defined in catalog.py:730
- Risk
- High impact × Low likelihood = 6 medium
- After mitigations
- High impact × Very Low likelihood = 3 low
Known vulnerabilities in the Linux kernel or any package used by app a mon servers may
Threat actors: Any
Mitigations
| Mitigation | Status |
|---|---|
| Automatic updates on servers MITIG43 | implemented |
| Use of grsecurity-hardened kernels on servers MITIG53 | implemented |
| AppArmor on Tor MITIG1 | implemented |
| AppArmor on Apache MITIG2 | implemented |
| Use of OSSEC monitoring software MITIG5 | implemented |
Where it applies
Applies to 2 components in 1 scenario.
Physical and host layer · Application Server (host), Monitoring Server (host)
Notes
Existing mitigations: A cron job ensures that automatic nightly security updates are applied for OS packages (MITIG43). Grsecurity/PaX linux patches prevent the exploitation of certain memory-corruption attacks (MITIG53). AppArmor profiles further reduce process capabilities through Mandatory Access Control (MITIG1, MITIG2). OSSEC is used for intrusion detection/file integrity monitoring (MITIG5). Automated test for mitigation: No.
How this threat is matched
Listed for these components. A boundary covers every component inside it.