Other Articles
- Cloud SQL – Configure Private IP
- Cloud SQL – Monitor CPU Utilization
- Cloud SQL – Enable Deletion Protection
- Cloud SQL – Enable Disk Encryption
- Cloud SQL – Enable Automated Backups
- Cloud SQL – Enable Log Export
- Cloud SQL – Enforce Password Validation
- Cloud SQL – Protect From Internet Access
- Cloud SQL – Enforce Secure Transport
- Compute Engine – Block Project-Wide SSH Keys
- Compute Engine – Disable IP Forwarding
- Compute Engine – Disable Public IP Addresses
- Compute Engine – Disable Serial Port Access
- Compute Engine – Enable Confidential Computing
- Compute Engine – Enable OS Login
- Compute Engine – Enable Shielded VM
- Compute Engine – Restrict Default Service Account
- General – Deny Public Access to KMS Keys
- General – Enforce Duties Separation
- General – Enforce KMS Key Rotation
- General – Restrict Admin Roles on Service Accounts
- Cloud Run – Configure Timeout Settings
- Cloud Storage – Enable Bucket Encryption
- Cloud Storage – Enable Bucket Logging
- Cloud Storage – Enable Bucket Versioning
- Cloud Storage – Enforce Uniform Bucket-Level Access
- Cloud Storage – Restrict Public Access
- IAM Users – Enforce GCP-Managed Keys
- IAM Users – Rotate External User-Managed Service Account Keys
- GKE – Enable Private Nodes
- GKE – Restrict Control Plane Access
- GKE – Enable Workload Identity
- GKE – Disable Legacy ABAC
- GKE – Enable Network Policy
- GKE – Enable Shielded Nodes
- GKE – Enable Node Auto-Upgrade and Auto-Repair
- GKE Cluster – Enable Cluster Logging
- General – Enable Cloud Audit Logs
- General – Configure a Log Sink
- General – Configure Log Bucket Retention
- Cloud SQL – Enable High Availability
- Cloud SQL – Configure Maintenance Window
- Cloud Storage – Configure Bucket Retention or Lifecycle
- Compute Engine – Enable Instance Deletion Protection
- VPC Firewall – Restrict Public SSH and RDP Access
- VPC Firewall – Restrict Public Database Access
- VPC Network – Avoid the Default Network
- VPC Network – Enable Subnet Flow Logs
General – Enable Security Command Center
Secure Configuration Checks > GCP
This check ensures that Security Command Center is enabled for the project. At least one built-in service, such as Security Health Analytics, must be active. The service reports vulnerabilities and threats in one place.
Check Details
- Resource: Google Cloud Project
- Check: Enable Security Command Center
- Risk: Without it, vulnerabilities, misconfigurations and threats are not reported in one place. They can go unnoticed.
Remediation via Google Cloud Console
-
Log in to the Google Cloud Console and navigate to
Security > Security Command Center.
- Click Get started.
-
Select a service tier, such as Standard or Premium.
Click Next.
- Review the built-in services. Make sure that at least one is enabled, such as Security Health Analytics. Click Next.
- If asked, click Grant roles to give the service the access that it needs.
- Click Finish setup to apply the changes.
Remediation via Google Cloud CLI
-
Open the Google Cloud Console and launch
Cloud Shell.
-
Enable the Security Command Center API:
gcloud services enable securitycenter.googleapis.com --project=<PROJECT_ID>
-
Enable a built-in service, such as Security Health Analytics:
gcloud scc settings services enable \ --project=<PROJECT_ID> \ --service=SECURITY_HEALTH_ANALYTICS
Replace
<PROJECT_ID>with your project ID. Choose the service tier first in the Google Cloud Console, as described above. You need permission to manage Security Command Center settings. -
Verify the service state:
gcloud scc settings services describe \ --project=<PROJECT_ID> \ --service=SECURITY_HEALTH_ANALYTICS
The service state must show as enabled.
Default Value
By default, Security Command Center is not enabled. The tiers differ in features and cost.
Updated on 09 November, 2026