Benchmark: PR.PS-04
Description
Log records are generated and made available for continuous monitoring.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-gcp-compliance
Start the Powerpipe server:
steampipe service startpowerpipe server
Open http://localhost:9033 in your browser and select PR.PS-04.
Run this benchmark in your terminal:
powerpipe benchmark run gcp_compliance.benchmark.nist_csf_v2_pr_ps_04
Snapshot and share results via Turbot Pipes:
powerpipe benchmark run gcp_compliance.benchmark.nist_csf_v2_pr_ps_04 --share
Controls
- Ensure compute firewall rule have logging enabled
- Ensure Logging is enabled for HTTP(S) Load Balancer
- Ensure that Cloud DNS logging is enabled for all VPC networks
- Ensure VPC Flow logs is enabled for every subnet in VPC Network
- GKE clusters logging should be enabled
- GKE clusters monitoring should be enabled
- Ensure that retention policies on log buckets are configured using Bucket Lock
- Ensure that the log metric filter and alerts exist for Audit Configuration changes
- Ensure that the log metric filter and alerts exist for Custom Role changes including undelete operations
- Ensure that the log metric filter and alerts exist for Custom Role changes
- Ensure that the log metric filter and alerts exist for VPC Network Firewall rule changes
- Ensure that the log metric filter and alerts exist for VPC network changes
- Ensure that the log metric filter and alerts exist for VPC network route changes
- Ensure log metric filter and alerts exist for project ownership assignments/changes
- Ensure that the log metric filter and alerts exist for SQL instance configuration changes
- Ensure that the log metric filter and alerts exist for Cloud Storage IAM permission changes
- Ensure that sinks are configured for all log entries
- Ensure that Cloud Storage buckets used for exporting logs have object versioning enabled
- Ensure that Cloud Storage buckets used for exporting logs have retention policy enabled
- Ensure that Cloud Storage buckets used for exporting logs are configured using bucket lock