Ensure the logging level is set to 'info'

LowLevel 1Automateddocker

Description

The info log level captures all logs except debug; lower levels lose security events and debug floods logs. Compliant when log-level is unset (default info) or set to info. The audit reads the running dockerd command line (ps) together with /etc/docker/daemon.json.

How it is checked

Audit method: Shell command

shell

args=$(ps -eo args 2>/dev/null) || exit 1; s=$(printf '%s\n' "$args" | grep '[d]ockerd'; cat /etc/docker/daemon.json 2>/dev/null); printf '%s\n' "$s" | grep -Eq -e '(--log-level[= ]+|"log-level"[[:space:]]*:[[:space:]]*")(debug|warn|error|fatal)' && echo noncompliant || echo compliant

Expected output: compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Remove the log-level option or set "log-level": "info" in /etc/docker/daemon.json (remove --log-level from the dockerd start-up flags) and restart the Docker daemon.

Properties

Operating systems: Any
Tags: dockerdaemon
Reference: CIS Docker Benchmark v1.9.0 - 2.3 Ensure the logging level is set to 'info'

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

shell

tmaegis scan --target docker