Skip to content

Commit

Permalink
Update and rename gcp-dropped-cloudarmor-policy.yaml to gcp-2021-019.…
Browse files Browse the repository at this point in the history
…yaml
  • Loading branch information
korniko98 authored Nov 2, 2023
1 parent cd98929 commit bc2a5d4
Showing 1 changed file with 5 additions and 4 deletions.
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
title: Dropped active Google Cloud Armor security policy
slug: gcp-dropped-cloudarmor-policy
slug: gcp-2021-019
cves: null
affectedPlatforms:
- GCP
Expand All @@ -19,11 +19,12 @@ knownITWExploitation: null
summary: |
There is a known issue where updating a BackendConfig resource
using the v1beta1 API removes an active Google Cloud Armor
security policy from its service.
security policy from its service. If you do not configure Google Cloud Armor
on your Ingress resources via the BackendConfig, then this issue does not affect your clusters.
manualRemediation: |
Dropped Cloud Armor security policies must be manually reattached.
detectionMethods: null
contributor: https://github.com/ramimac
references:
- https://cloud.google.com/support/bulletins#gcp-2022-009
- https://cloud.google.com/anthos/clusters/docs/security-bulletins#gcp-2022-009
- https://cloud.google.com/support/bulletins#gcp-2021-019
- https://cloud.google.com/anthos/clusters/docs/security-bulletins#gcp-2021-019

0 comments on commit bc2a5d4

Please sign in to comment.