|
| 1 | +{ |
| 2 | + "Provider": "gcp", |
| 3 | + "CheckID": "compute_instance_suspended_without_persistent_disks", |
| 4 | + "CheckTitle": "Suspended VM instance does not have persistent disks attached", |
| 5 | + "CheckType": [], |
| 6 | + "ServiceName": "compute", |
| 7 | + "SubServiceName": "", |
| 8 | + "ResourceIdTemplate": "", |
| 9 | + "Severity": "medium", |
| 10 | + "ResourceType": "compute.googleapis.com/Instance", |
| 11 | + "ResourceGroup": "compute", |
| 12 | + "Description": "This check identifies VM instances in a **SUSPENDED** or **SUSPENDING** state with persistent disks still attached.\n\nPersistent disks on suspended VMs remain accessible through the GCP API and could contain **sensitive data** while the instance is inactive, potentially creating security blind spots in long-forgotten infrastructure.", |
| 13 | + "Risk": "Persistent disks on suspended VM instances remain accessible through the GCP API and may contain **sensitive data**, creating potential security risks:\n\n- **Unauthorized data access** if credentials are compromised or permissions are misconfigured\n- **Data exposure** from forgotten infrastructure that is no longer actively monitored\n- **Security blind spots** where suspended resources are overlooked during security reviews and audits", |
| 14 | + "RelatedUrl": "", |
| 15 | + "AdditionalURLs": [ |
| 16 | + "https://cloud.google.com/icompute/docs/instances/suspend-resume-instance", |
| 17 | + "https://www.trendmicro.com/cloudoneconformity/knowledge-base/gcp/ComputeEngine/persistent-disks-attached-to-suspended-vms.html" |
| 18 | + ], |
| 19 | + "Remediation": { |
| 20 | + "Code": { |
| 21 | + "CLI": "gcloud compute instances delete INSTANCE_NAME --zone=ZONE", |
| 22 | + "NativeIaC": "", |
| 23 | + "Other": "1. Open the Google Cloud Console\n2. Navigate to Compute Engine > VM instances\n3. Identify suspended instances with attached disks\n4. If the instance is no longer needed, select it and click DELETE\n5. If the instance will be resumed, take no action or resume it with: gcloud compute instances resume INSTANCE_NAME --zone=ZONE", |
| 24 | + "Terraform": "```hcl\n# To remediate, either delete the suspended instance or resume it\n# Delete by removing the resource from your Terraform configuration\n# Or resume by changing the desired_status\nresource \"google_compute_instance\" \"example_resource\" {\n name = \"example-instance\"\n machine_type = \"e2-medium\"\n zone = \"us-central1-a\"\n\n # Set desired_status to RUNNING to resume the instance\n desired_status = \"RUNNING\"\n\n boot_disk {\n initialize_params {\n image = \"debian-cloud/debian-11\"\n }\n }\n\n network_interface {\n network = \"default\"\n }\n}\n```" |
| 25 | + }, |
| 26 | + "Recommendation": { |
| 27 | + "Text": "Regularly review suspended VM instances to reduce your attack surface. Either **resume** instances if still needed, or **delete** them along with their attached disks to eliminate potential data exposure. Implement automated policies to detect and alert on long-suspended instances as part of your security monitoring.", |
| 28 | + "Url": "https://hub.prowler.com/check/compute_instance_suspended_without_persistent_disks" |
| 29 | + } |
| 30 | + }, |
| 31 | + "Categories": [], |
| 32 | + "DependsOn": [], |
| 33 | + "RelatedTo": [ |
| 34 | + "compute_instance_disk_auto_delete_disabled" |
| 35 | + ], |
| 36 | + "Notes": "This check is focused on security risks rather than cost optimization. Persistent disks on suspended VMs remain accessible and may contain sensitive data, creating potential unauthorized access risks." |
| 37 | +} |
0 commit comments