---
title: Incoming system calls should be filtered using enabled Seccomp profiles
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > Incoming system calls should be
  filtered using enabled Seccomp profiles
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Incoming system calls should be filtered using enabled Seccomp profiles
Classification:complianceFramework:cis-dockerControl:5.22 
## Description{% #description %}

Containers should run under a seccomp profile.

## Rationale{% #rationale %}

The default seccomp profile of Docker blocks about 50 system calls that containers rarely need and that often serve kernel exploits.

## Audit{% #audit %}

Inspect the containers, then show the default profile of the daemon:

```bash
docker ps --quiet --all | xargs docker inspect --format '{{ .Name }}: SecurityOpt={{ .HostConfig.SecurityOpt }}'
docker info --format '{{ .SecurityOptions }}'
```

Datadog fails the rule when a container sets `seccomp=unconfined`, in either spelling, or names no profile while the default profile of the daemon is `unconfined`, and passes it otherwise.

## Remediation{% #remediation %}

Run the container without `--security-opt seccomp=unconfined`, under the default profile or a profile of your own, and leave the default profile of the daemon set.

## Impact{% #impact %}

A workload that needs a blocked system call fails until a profile of its own allows it.

## Default value{% #default-value %}

Docker applies its default seccomp profile.

## References{% #references %}

1. [https://docs.docker.com/engine/containers/run/#security-configuration](https://docs.docker.com/engine/containers/run/#security-configuration)
1. [https://docs.docker.com/engine/security/seccomp/](https://docs.docker.com/engine/security/seccomp/)
1. [https://www.kernel.org/doc/Documentation/prctl/seccomp_filter.txt](https://www.kernel.org/doc/Documentation/prctl/seccomp_filter.txt)
