You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After applying audit rules using docker_enable_audit everything seems fine is check with Docker Bench for Security.
[INFO] 1 - Host Configuration
[PASS] 1.1 - Ensure a separate partition for containers has been created
[NOTE] 1.2 - Ensure the container host has been Hardened
[PASS] 1.3 - Ensure Docker is up to date
[INFO] * Using 17.09.0 which is current
[INFO] * Check with your operating system vendor for support and security maintenance for Docker
[INFO] 1.4 - Ensure only trusted users are allowed to control Docker daemon
[INFO] * docker:x:993:
[PASS] 1.5 - Ensure auditing is configured for the Docker daemon
[PASS] 1.6 - Ensure auditing is configured for Docker files and directories - /var/lib/docker
[PASS] 1.7 - Ensure auditing is configured for Docker files and directories - /etc/docker
[PASS] 1.8 - Ensure auditing is configured for Docker files and directories - docker.service
[INFO] 1.9 - Ensure auditing is configured for Docker files and directories - docker.socket
[INFO] * File not found
[INFO] 1.10 - Ensure auditing is configured for Docker files and directories - /etc/default/docker
[INFO] * File not found
[PASS] 1.11 - Ensure auditing is configured for Docker files and directories - /etc/docker/daemon.json
[PASS] 1.12 - Ensure auditing is configured for Docker files and directories - /usr/bin/docker-containerd
[PASS] 1.13 - Ensure auditing is configured for Docker files and directories - /usr/bin/docker-run
However after reboot (using Vagrantfile under tests) errors is seen during auditd startup so some rules are not applied.
Oct 22 14:49:56 localhost.localdomain augenrules[651]: Error sending add rule data request (No such file or directory)
Oct 22 14:49:56 localhost.localdomain augenrules[651]: There was an error in line 12 of /etc/audit/audit.rules
Oct 22 14:49:56 localhost.localdomain systemd[1]: Started Security Auditing Service.
[INFO] 1 - Host Configuration
[PASS] 1.1 - Ensure a separate partition for containers has been created
[NOTE] 1.2 - Ensure the container host has been Hardened
[PASS] 1.3 - Ensure Docker is up to date
[INFO] * Using 17.09.0 which is current
[INFO] * Check with your operating system vendor for support and security maintenance for Docker
[INFO] 1.4 - Ensure only trusted users are allowed to control Docker daemon
[INFO] * docker:x:993:
[PASS] 1.5 - Ensure auditing is configured for the Docker daemon
[PASS] 1.6 - Ensure auditing is configured for Docker files and directories - /var/lib/docker
[PASS] 1.7 - Ensure auditing is configured for Docker files and directories - /etc/docker
[PASS] 1.8 - Ensure auditing is configured for Docker files and directories - docker.service
[INFO] 1.9 - Ensure auditing is configured for Docker files and directories - docker.socket
[INFO] * File not found
[INFO] 1.10 - Ensure auditing is configured for Docker files and directories - /etc/default/docker
[INFO] * File not found
[WARN] 1.11 - Ensure auditing is configured for Docker files and directories - /etc/docker/daemon.json
[WARN] 1.12 - Ensure auditing is configured for Docker files and directories - /usr/bin/docker-containerd
[WARN] 1.13 - Ensure auditing is configured for Docker files and directories - /usr/bin/docker-runc
One way to fix this might be to add a new lines in the rules saying -c which let auditd continue processing rules even if errors are seen.
Need understand reason why everything works before reboot directly after applying the rules etc.
The text was updated successfully, but these errors were encountered:
After applying audit rules using
docker_enable_audit
everything seems fine is check with Docker Bench for Security.However after reboot (using Vagrantfile under tests) errors is seen during auditd startup so some rules are not applied.
One way to fix this might be to add a new lines in the rules saying
-c
which let auditd continue processing rules even if errors are seen.Need understand reason why everything works before reboot directly after applying the rules etc.
The text was updated successfully, but these errors were encountered: