DKER-EE-002070 - The Docker Enterprise default seccomp profile must not be disabled.


Seccomp filtering provides a means for a process to specify a filter for incoming system calls. The default Docker seccomp profile works on whitelist basis and allows 311 system calls blocking all others. It should not be disabled unless it hinders the container application usage.

A large number of system calls are exposed to every userland process with many of them going unused for the entire lifetime of the process. Most of the applications do not need all the system calls and thus benefit by having a reduced set of available system calls. The reduced set of system calls reduces the total kernel surface exposed to the application and thus improvises application security.

The default seccomp profile blocks syscalls, regardless of --cap-add passed to the container. Create a custom seccomp profile in such cases. Disable the default seccomp profile by passing --security-opt=seccomp:unconfined on docker run.

When running a container, it uses the default profile unless it is overridden with the --security-opt option.


This fix only applies to the use of Docker Engine - Enterprise on a Linux host operating system.

By default, seccomp profiles are enabled. It is not necessary to do anything unless the user wants to modify the seccomp profile. Do not pass unconfined flags to run a container without the default seccomp profile. Refer to seccomp documentation for details.

See Also

Item Details


References: 800-53|CM-7a., CAT|I, CCI|CCI-000381, Rule-ID|SV-235812r627563_rule, STIG-ID|DKER-EE-002070, STIG-Legacy|SV-104797, STIG-Legacy|V-95659, Vuln-ID|V-235812

Plugin: Unix

Control ID: b6da9670594770c36b5d7ec9dade5d5cfc72d16ed34b9ff87085bda6b32257be