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

IDPrisma Cloud Remediation - GCP Compute Engine Misconfiguration
From Version5.0.0
Tasks12

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


Prisma Cloud Remediation - GCP Compute Engine Misconfiguration

Inputs

  • AutoRemediateComputeEngine — Execute GCP Compute Engine remediation automatically?
  • policyId — Grab the Prima Cloud policy Id.

Commands used

closeInvestigation redlock-dismiss-alerts

Flowchart

yes yes yes Yes VMs yes Start Start Is Google Cloud Compute integration enabled? Is Google Cloud Compute i... Done Done Is there a policy to remediate? Is there a policy to reme... Update Compute Engine automatically? Update Compute Engine aut... Auto remediate? Auto remediate? Execute playbook Execute playbook Manually update Compute Engine Manually update Compute E... Close investigation - closeInvestigation Close investigation closeInvestigation Prisma Cloud Remediation - GCP Compute Engine Instance Misconfiguration - Prisma Cloud Remediation - GCP Compute Engine Instance Misconfiguration Prisma Cloud Remediation ... Prisma Cloud Remediation - GC... Is Prisma Cloud v2 integration enabled? Is Prisma Cloud v2 integr... Dismiss Prisma Cloud alert - redlock-dismiss-alerts Dismiss Prisma Cloud alert redlock-dismiss-alerts
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

---

![Prisma Cloud Remediation - GCP Compute Engine Misconfiguration v2](../doc_files/Prisma_Cloud_Remediation_-_GCP_Compute_Engine_Misconfiguration_v2.png)