Cis GCP Cos 4.1.1.2

4.1.1.2 Ensure Logging Service is Running (Manual)

Description

Some form of logging for the OS should be used. On COS Stackdriver-logging agent or fluent-bit logging agent are provided and can be activated simply by following the guides. It is not require to use these for logging but they are simple to set up and will work well.

Rationale

If no logging is running, their will be less of a trail for audit if things go wrong. It is a good practice to have logging enabled for better visibility.

Audit Procedure

This audit procedure is only if you are using one of the supporting logging services described.

Stackdriver-Logging Agent

Run the following command to verify stackdriver-logging is running:

# systemctl status stackdriver-logging | grep Active
Active: active (running) since <Day date time>

Fluent-bit Logging

Or if your system has fluent-bit, run the following command to verify fluent-bit is running:

# systemctl status fluent-bit | grep Active
Active: active (running) since <Day date time>

Expected Result

The output should show Active: active (running) for either stackdriver-logging or fluent-bit.

Remediation

This remediation is only if you want to use one of the supported logging services described.

Stackdriver-logging Agent

Run the following command to enable stackdriver-logging:

# systemctl start stackdriver-logging

Fluent-bit Logging

Run the following command to enable fluent-bit:

# systemctl start fluent-bit

Works for Both

Simply update the instance metadata to enable logging as follows:

# gcloud compute instances add-metadata <instance-name> \
    --zone <compute-zone> \
    --metadata google-logging-enabled=true

CIS Controls

Profile

• Level 2 - Server