v1.compute.healthChecks.delete

​

Event Information

1. The v1.compute.healthChecks.delete event in GCP for Compute indicates that a health check has been deleted in the Compute Engine service.
2. This event signifies that any associated resources or configurations related to the deleted health check will no longer be active or available.
3. It is important to monitor and track these events to ensure that the health check deletion does not impact the overall health and availability of your Compute Engine instances.

​

Examples

1. Unauthorized deletion: If security is impacted with v1.compute.healthChecks.delete in GCP for Compute, it could potentially allow unauthorized users or malicious actors to delete health checks. This could lead to disruption of service availability and potential denial of service attacks.

2. Misconfiguration: If security is impacted with v1.compute.healthChecks.delete in GCP for Compute, misconfiguration of access controls or permissions could result in unintended deletion of health checks. This could lead to false positives or negatives in monitoring and impact the overall reliability and performance of the application or infrastructure.

3. Lack of audit trail: If security is impacted with v1.compute.healthChecks.delete in GCP for Compute, the lack of proper logging and audit trail for health check deletions could make it difficult to track and investigate any unauthorized or accidental deletions. This could hinder incident response and forensic analysis, making it challenging to identify the root cause and take appropriate actions to prevent future incidents.

​

Remediation

​

Using Console

To remediate the issues mentioned in the previous response for GCP Compute using the GCP console, you can follow these step-by-step instructions:

1. Enable VPC Flow Logs:

   • Go to the GCP Console and navigate to the VPC network page.
   • Select the VPC network where you want to enable flow logs.
   • Click on “Edit” at the top of the page.
   • Scroll down to the “Flow logs” section and click on “Enable flow logs”.
   • Configure the desired flow log settings, such as the filter, flow sampling, and destination.
   • Click on “Save” to enable VPC flow logs for the selected VPC network.

2. Enable CloudTrail for GCP:

   • Go to the GCP Console and navigate to the CloudTrail page.
   • Click on “Create a new trail” to create a new CloudTrail configuration.
   • Provide a name for the trail and select the GCP project where you want to enable CloudTrail.
   • Configure the desired settings, such as the storage location, log file validation, and event selectors.
   • Click on “Create” to enable CloudTrail for the selected GCP project.

3. Enable Security Center for GCP:

   • Go to the GCP Console and navigate to the Security Command Center page.
   • Click on “Enable Security Command Center” to enable Security Center for your GCP project.
   • Configure the desired settings, such as the organization, billing account, and location.
   • Click on “Enable” to enable Security Center for the selected GCP project.

These steps will help you remediate the mentioned issues by enabling VPC flow logs, CloudTrail for GCP, and Security Center for GCP using the GCP console.

​

Using CLI

To remediate the issues mentioned in the previous response for GCP Compute using GCP CLI, you can follow these steps:

1. Disable SSH access for the default service account:

   • Use the following command to get the email address of the default service account:

     gcloud iam service-accounts list --filter="displayName:Compute Engine default service account"
     

   • Once you have the email address, use the following command to remove the roles associated with SSH access:

     gcloud projects remove-iam-policy-binding PROJECT_ID --member=serviceAccount:EMAIL_ADDRESS --role=roles/compute.osLogin
     

2. Enable VPC Flow Logs for network monitoring:

   • Use the following command to enable VPC Flow Logs for a specific subnet:

     gcloud compute networks subnets update SUBNET_NAME --region=REGION --enable-flow-logs
     

3. Restrict public access to Cloud Storage buckets:

   • Use the following command to update the bucket ACL and remove all public access:

     gsutil iam ch allUsers:legacyObjectReader gs://BUCKET_NAME
     

Please note that you need to replace the placeholders (PROJECT_ID, EMAIL_ADDRESS, SUBNET_NAME, REGION, and BUCKET_NAME) with the actual values specific to your GCP environment.

​

Using Python

To remediate the issues mentioned in the previous response for GCP Compute using Python, you can use the following approaches:

1. Enforce secure OS configurations:

   • Use the google-cloud-sdk library to retrieve the list of GCP Compute instances.
   • Iterate through each instance and check the OS configuration settings.
   • Use the googleapiclient library to update the instance settings and enforce secure configurations.
   • Example Python script:

     from google.cloud import compute_v1
     
     def enforce_secure_os_config(project_id):
         compute_client = compute_v1.InstancesClient()
         instances = compute_client.list(project=project_id)
         
         for instance in instances:
             # Check OS configuration settings
             if instance.os_config.secure_boot == False:
                 # Update instance settings to enforce secure boot
                 instance.os_config.secure_boot = True
                 compute_client.update(project=project_id, instance=instance)
     

2. Implement network security controls:

   • Use the google-cloud-sdk library to retrieve the list of GCP Compute instances.
   • Iterate through each instance and check the network security controls.
   • Use the googleapiclient library to update the instance settings and implement necessary network security controls.
   • Example Python script:

     from google.cloud import compute_v1
     
     def implement_network_security_controls(project_id):
         compute_client = compute_v1.InstancesClient()
         instances = compute_client.list(project=project_id)
         
         for instance in instances:
             # Check network security controls
             if instance.network_config.firewall_rules == []:
                 # Add necessary firewall rules
                 firewall_rule = compute_v1.FirewallRule(...)
                 compute_client.insert(project=project_id, firewall_rule=firewall_rule)
     

3. Enable logging and monitoring:

   • Use the google-cloud-sdk library to retrieve the list of GCP Compute instances.

   • Iterate through each instance and enable logging and monitoring.

   • Use the googleapiclient library to update the instance settings and enable necessary logging and monitoring.

   • Example Python script:

     from google.cloud import compute_v1
     
     def enable_logging_and_monitoring(project_id):
         compute_client = compute_v1.InstancesClient()
         instances = compute_client.list(project=project_id)
         
         for instance in instances:
             # Enable logging and monitoring
             instance.logging_config.enable = True
             instance.monitoring_config.enable = True
             compute_client.update(project=project_id, instance=instance)