TMA-COS-4.1.2.2

Ensure journald is configured to write logfiles to persistent disk

보통레벨 1수동 검토cos

설명

Data from journald may be stored in volatile memory or persisted locally on the server. Logs in memory will be lost upon a system reboot. By persisting logs to local disk on the server they are protected from loss. Writing log data to disk will provide the ability to forensically reconstruct events which may have impacted the operations or security of a system even after a system crash or reboot.

점검 방법

감사 방식: 수동 검토

이 권장 사항은 자동으로 점검할 수 없습니다. --include-manual 옵션을 전달하면 스캔 결과에 이 지침과 함께 표시됩니다.

Review /etc/systemd/journald.conf and verify that logs are persisted to disk: # grep -e Storage /etc/systemd/journald.conf # Storage=persistent

조치 방법

조치 방식: 가이드 또는 인프라 패치

Edit the /etc/systemd/journald.conf file and add the following line: Storage=persistent /etc is stateless on Container-Optimized OS. Therefore, /etc cannot be used to make these changes persistent across reboots. The steps mentioned above needs to be performed after every boot.

속성

운영 체제: 모두
태그: container-optimized-oscoslogging
참고 자료: CIS Google Container-Optimized OS Benchmark v1.2.0 - 4.1.2.2 Ensure journald is configured to write logfiles to persistent disk