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

修正方法

修正方法: ガイダンスまたは IaC パッチ

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