- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`Classification:
compliance
Framework:
cis-docker
Control:
1.2.9
Set up the docker integration.
Audit /etc/sysconfig/docker
, if applicable.
As well as auditing the Linux file system and system calls, you should also audit the Docker daemon. Because this daemon runs with root privileges, it is very important to audit its activities and usage. Its behavior depends on some key files and directories, including /etc/sysconfig/docker
. It contains various parameters related to the Docker daemon when run on CentOS and RHEL based distributions. If present, it is important that it is audited.
Verify that there is an audit rule associated with the /etc/sysconfig/docker
file. To see the rule for the /etc/sysconfig/docker
file, run:
auditctl -l | grep /etc/sysconfig/docker
You should add a rule for the /etc/sysconfig/docker
file. For example, add the following line to a new file in /etc/audit/rules.d/
. For instance, create a file named docker.rules
:
echo "-w /etc/sysconfig/docker -k docker" > /etc/audit/rules.d/docker.rules
Then, reload the audit rules:
augenrules --load
Next, restart the audit daemon using the following command:
service auditd restart
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.
By default, Docker-related files and directories are not audited. The file /etc/sysconfig/docker
may not be present on the system and in that case, this recommendation is not applicable.
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).