---
title: Default seccomp profile disabled
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > Code Security > Infrastructure as Code (IaC)
  Security > IaC Security Rules > Default seccomp profile disabled
---

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

# Default seccomp profile disabled

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}).
{% /alert %}

{% /callout %}

## Metadata{% #metadata %}

**Id:** `dockercompose-default-seccomp-profile-disabled` 

**Platform:** DockerCompose

**Severity:** Medium

**Category:** Resource Management

#### Learn More{% #learn-more %}

- [Provider Reference](https://docs.docker.com/reference/compose-file/services/#security_opt)

### Description{% #description %}

The default seccomp (secure computing mode) profile restricts the set of Linux system calls available to a container, significantly reducing the attack surface if the container is compromised. Setting `seccomp:unconfined` in `security_opt` disables this protection entirely, allowing container processes to invoke any system call the kernel supports. Services should not include `seccomp:unconfined` in their `security_opt` list unless there is a specific, documented justification.

## Compliant Code Examples{% #compliant-code-examples %}

```yaml
services:
  profile:
    image: alpine
    security_opt: [seccomp:/profiles/unconfined.json]
  lookalike:
    image: alpine
    security_opt: [seccomp:unconfined-extra]
  default:
    image: alpine
```

## Non-Compliant Code Examples{% #non-compliant-code-examples %}

```yaml
services:
  colon:
    image: alpine
    security_opt: [seccomp:unconfined]
  equal:
    image: alpine
    security_opt: [seccomp=unconfined]
```