Prisma Cloud Remediation - GCP Compute Engine Misconfiguration Deprecated Hidden
Deprecated. Use Prisma Cloud Remediation - GCP Compute Engine Misconfiguration v2 instead. This playbook remediates Prisma Cloud GCP Compute Engine alerts. It calls sub-playbooks that perform the actual remediation steps. Remediation: - GCP VM instances have serial port access enabled - GCP VM instances have block project-wide SSH keys feature disabled - GCP VM instances without any custom metadata information
Prisma Cloud by Palo Alto Networks · 12 tasks · 2 inputs · 0 outputs
Details
| ID | Prisma Cloud Remediation - GCP Compute Engine Misconfiguration |
|---|---|
| From Version | 5.0.0 |
| Tasks | 12 |
README
This playbook remediates Prisma Cloud GCP Compute Engine alerts. It calls sub-playbooks that perform the actual remediation steps.
Remediation:
- GCP VM instances have serial port access enabled
- GCP VM instances have block project-wide SSH keys feature disabled
- GCP VM instances without any custom metadata information
Dependencies
This playbook uses the following sub-playbooks, integrations, and scripts.
Sub-playbooks
- Prisma Cloud Remediation - GCP Compute Engine Instance Misconfiguration
Integrations
- PrismaCloud v2
Scripts
This playbook does not use any scripts.
Commands
- redlock-dismiss-alerts
- closeInvestigation
Playbook Inputs
| Name | Description | Default Value | Required |
|---|---|---|---|
| AutoRemediateComputeEngine | Execute GCP Compute Engine remediation automatically? | no | Optional |
| policyId | Grab the Prima Cloud policy Id. | incident.labels.policy | Optional |
Playbook Outputs
There are no outputs for this playbook.
Playbook Image

Inputs
AutoRemediateComputeEngine— Execute GCP Compute Engine remediation automatically?policyId— Grab the Prima Cloud policy Id.
Commands used
closeInvestigation
redlock-dismiss-alerts
Flowchart
This playbook remediates Prisma Cloud GCP Compute Engine alerts. It calls sub-playbooks that perform the actual remediation steps. Remediation: - GCP VM instances have serial port access enabled - GCP VM instances have block project-wide SSH keys feature disabled - GCP VM instances without any custom metadata information ## Dependencies This playbook uses the following sub-playbooks, integrations, and scripts. ### Sub-playbooks Prisma Cloud Remediation - GCP Compute Engine Instance Misconfiguration ### Integrations PrismaCloud v2 ### Scripts This playbook does not use any scripts. ### Commands * closeInvestigation * prisma-cloud-alert-dismiss ## Playbook Inputs --- | **Name** | **Description** | **Default Value** | **Required** | | --- | --- | --- | --- | | AutoRemediateComputeEngine | Execute GCP Compute Engine remediation automatically? | no | Optional | | policyId | Grab the Prima Cloud policy ID. | incident.labels.policy | Optional | ## Playbook Outputs --- There are no outputs for this playbook. ## Playbook Image --- 