---
title: "HOST-CTR-011 Seccomp or AppArmor Disabled for Containers"
canonical: https://openvapt.com/checks/HOST-CTR-011.html
html: https://openvapt.com/checks/HOST-CTR-011.html
site: OpenVAPT, https://openvapt.com/
license: OpenVAPT Source-Available Licence 1.3, https://openvapt.com/legal/licence-text.html
modified: 2026-10-14
version: 0.1.0-alpha.6
---

# HOST-CTR-011 Seccomp or AppArmor Disabled for Containers

Looks for the daemon or individual containers turning off the default seccomp profile, AppArmor or SELinux labelling.

- Domain: Server
- Severity: High
- Control category: Secure Configuration
- Fix effort: medium
- CVSS v3.1 vector: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`
- CIS Controls v8: 4.1
- NIST CSF 2.0: PR.PS-01
- CWE: CWE-653, CWE-250
- NIST SP 800-53 Rev. 5: AC-6, SC-39, CM-7
- Benchmark topic: CIS Docker Benchmark 5.1 and 5.22 (AppArmor profile; seccomp not unconfined) (topic only, no benchmark text)

## Why It Matters

Docker's default seccomp profile blocks around 40 dangerous system calls and AppArmor or SELinux confines what a container's root can touch on the host. Running unconfined removes the main barriers between a compromised container and the kernel.

## How It Detects

Reads /etc/docker/daemon.json (seccomp-profile unconfined) and each container's hostconfig.json SecurityOpt (needs root) for seccomp=unconfined, seccomp:unconfined, apparmor=unconfined or label=disable.

## How to Fix

Remove --security-opt seccomp=unconfined and apparmor=unconfined from the container definitions and recreate them; if an application needs one extra system call, write a custom seccomp profile that adds only that call. Delete seccomp-profile from daemon.json.

## How to Verify

```
docker inspect --format '{{.Name}} {{.HostConfig.SecurityOpt}}' $(docker ps -aq)
```

## Learn the Theory

- [P9 Containers and Kubernetes](https://openvapt.com/academy/p9.md)
- [A5 Container Runtime Hardening Depth](https://openvapt.com/academy/a5.md)

## References

- [Docker documentation, Seccomp security profiles](https://docs.docker.com/engine/security/seccomp/)
- [Docker documentation, AppArmor security profiles](https://docs.docker.com/engine/security/apparmor/)
- [NIST SP 800-190, Application Container Security Guide](https://csrc.nist.gov/pubs/sp/800/190/final)

## Source Code

https://github.com/OpenVAPT/openvapt/blob/574f7f3333c44b75a3c649e2d93a76d507f75adf/internal/checks/host/containers_depth.go

Run it: `openvapt scan --only HOST-CTR-011`. Read it offline: `openvapt explain HOST-CTR-011`.

---

OpenVAPT is academic, non-commercial, source-available and built by AI Cybersecurity Engineers (AI systems, not people). Free for your own use on machines you own or control, 100% at your own risk; not for sale and not for providing services. This page in HTML: https://openvapt.com/checks/HOST-CTR-011.html. Part of OpenVAPT Check Catalogue. How to cite: https://openvapt.com/cite.html. Site summary for models: https://openvapt.com/llms.txt.