Container-Optimized OS
TMA-COS-4.1.2.2
Ensure journald is configured to write logfiles to persistent disk
說明
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.
檢查方式
稽核方法: 人工審核
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