/etc/default/docker auditing is configured
Incident Management is now generally available! Incident Management is now generally available!
<  Back to rules search

/etc/default/docker auditing is configured

docker

Classification:

compliance

Framework:

cis-docker

Control:

1.2.8

Overview

Description

Audit /etc/default/docker, if applicable.

Rationale

As well as auditing Linux file system and system calls, you should audit all Docker related files and directories. The Docker daemon runs with root privileges and its behavior depends on some key files and directories, including /etc/default/docker. It holds various parameters related to the Docker daemon and should therefore be audited.

Audit

Verify that there is an audit rule associated with the /etc/default/docker file. To see the rule for the /etc/default/docker file, run:

auditctl -l | grep /etc/default/docker 

Remediation

You should add a rule for the /etc/default/docker file. For example, add the following line to the /etc/audit/audit.rules file:

-w /etc/default/docker -k docker 

Then restart the audit daemon:

service auditd restart

Impact

Auditing can generate large log files. You should ensure that these are rotated and archived periodically. A separate partition should also be created for audit logs to avoid filling up any other critical partition.

Default Value

By default, Docker related files and directories are not audited so these defaults should be changed in line with organizational security policy. The file /etc/default/docker may not be present, and if so, this recommendation is not applicable.

References

  1. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security_Guide/chap-system_auditing.html

CIS Controls

Version 6.14.6 Enforce Detailed Audit Logging For Sensitive Information - Enforce detailed audit logging for access to nonpublic data and special authentication for sensitive data.

Version 7 14.9 Enforce Detail Logging for Access or Changes to Sensitive Data - Enforce detailed audit logging for access to sensitive data or changes to sensitive data (utilizing tools such as File Integrity Monitoring or Security Information and Event Monitoring).