​
Event Information

  1. The v1.compute.subnetworks.patch event in GCP for Compute refers to a modification made to a subnetwork within a project.
  2. This event indicates that changes have been made to the configuration or properties of a specific subnetwork, such as its IP range, secondary IP ranges, or routing settings.
  3. It is important to monitor and track these events to ensure that any modifications to subnetworks are intentional and align with the desired network architecture and security requirements.

​
Examples

  1. Unauthorized access: If security is impacted with v1.compute.subnetworks.patch in GCP for Compute, it could potentially allow unauthorized access to the subnetworks. This could lead to unauthorized users gaining access to sensitive data or resources within the subnetwork, compromising the overall security of the environment.

  2. Network segmentation issues: The v1.compute.subnetworks.patch operation in GCP allows for modifications to the subnetwork configuration. If security is impacted, it could result in network segmentation issues. This means that the subnetworks may not be properly isolated from each other, potentially allowing unauthorized communication between different subnetworks and increasing the attack surface.

  3. Misconfiguration of firewall rules: The v1.compute.subnetworks.patch operation also allows for changes to the firewall rules associated with the subnetworks. If security is impacted, it could result in misconfiguration of these firewall rules. This could lead to unintended access permissions, allowing unauthorized traffic to pass through the firewall and potentially compromising the security of the subnetworks.

​
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. Restricting SSH access:

    • Go to the GCP Console and navigate to the Compute Engine section.
    • Select the instance for which you want to restrict SSH access.
    • Click on the “Edit” button at the top of the page.
    • Scroll down to the “Firewalls” section and click on “Add firewall rule”.
    • Provide a name for the firewall rule and set the “Targets” to “All instances in the network”.
    • In the “Source IP ranges” field, enter the IP range from which you want to allow SSH access (e.g., your organization’s IP range).
    • Set the “Protocols and ports” to allow SSH (port 22) traffic.
    • Click on the “Create” button to save the firewall rule.

  2. Enabling VPC Flow Logs:

    • Go to the GCP Console and navigate to the VPC Network section.
    • Select the VPC network for which you want to enable flow logs.
    • Click on the “Edit” button at the top of the page.
    • Scroll down to the “Flow logs” section and click on “Add flow log”.
    • Provide a name for the flow log and select the desired configuration options (e.g., sampling rate, metadata inclusion).
    • Choose the desired destination for the flow logs (e.g., Stackdriver Logging, Cloud Storage).
    • Click on the “Create” button to enable flow logs for the VPC network.

  3. Implementing IAM best practices:

    • Go to the GCP Console and navigate to the IAM & Admin section.
    • Select the project for which you want to implement IAM best practices.
    • Click on the “IAM” tab to view the IAM roles and permissions.
    • Review the existing IAM roles and identify any unnecessary or overly permissive roles.
    • Remove any unnecessary roles and adjust the permissions of existing roles to follow the principle of least privilege.
    • Consider creating custom IAM roles with specific permissions tailored to the needs of different user groups.
    • Regularly review and audit the IAM roles and permissions to ensure they align with the organization’s security requirements.

​
Using CLI

  1. Enable VPC Flow Logs for GCP Compute instances:

    • Use the gcloud compute instances update command to enable VPC Flow Logs for a specific instance: 
      gcloud compute instances update INSTANCE_NAME --enable-network-endpoint-logging

  2. Restrict SSH access to GCP Compute instances:

    • Use the gcloud compute firewall-rules update command to update the firewall rule for SSH access: 
      gcloud compute firewall-rules update FIREWALL_RULE_NAME --source-ranges=IP_RANGE --allow=tcp:22

  3. Implement disk encryption for GCP Compute instances:

    • Use the gcloud compute disks create command to create an encrypted disk: 
      gcloud compute disks create DISK_NAME --size=SIZE --type=DISK_TYPE --encryption-key=KEY_NAME

​
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)