Agent skill · google
cloud-armor-crs-rule-upgrader
Upgrades Google Cloud Armor security policies from OWASP CRS 3.0 and 3.3 to OWASP CRS 4.22. Preserves signature opt-in and opt-out lists, translates evaluatePreconfiguredExpr to native evaluatePreconfiguredWaf dictionary parameters, remaps signature IDs to v042200, drops retired signature IDs, and updates structured preconfiguredWafConfig fine-tuning exclusions. Evaluates operational risk (High Breaking Change, Medium Attention Required, Low Clean Upgrade) including Method Enforcement breaking changes (PUT/PATCH/DELETE blocking) and sensitivity coverage expansions. Supports both in-place rule upgrades and smooth preview mode deployments with priority spacing and a 200-rule quota guardrail. Use when a user or agent needs to audit, upgrade, or transition Cloud Armor WAF rules to CRS 4.22. Don't use for non-WAF Cloud Armor rules (IP rate-limiting, geo-blocking, reCAPTCHA) or AWS/Azure WAF migrations.
What it needs
About 9k tokens when loaded.
What this skill does
Cloud Armor OWASP Rule Upgrader (CRS 3.0/3.3 -> 4.22) <!-- disableFinding(LINEOVER80) --> This skill guides Network Security Agents and Google Cloud practitioners through auditing, assessing, and upgrading Google Cloud Armor security policies from legacy OWASP Core Rule Set (CRS) 3.0 or 3.3 to OWASP CRS 4.22. Usage Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. -------------------------------------------------------------------------------- Prerequisites and Environment Setup Before auditing or modifying Google Cloud Armor security policies, ensure the following prerequisites are met: 1. Google Cloud SDK: Install or update the Google Cloud CLI (gcloud). 2. Project Selection and Active Billing: Select your target Google Cloud project and verify that an active billing account is attached: 3. API Enablement: Enable the Compute Engine API (for Cloud Armor security policies) and Cloud Logging API (for preview mode telemetry): 4. Authentication: Interactive CLI: gcloud auth login Application Default Credentials (ADC): gcloud auth application-default login Service Accounts: Set GOOGLEAPPLICATIONCREDENTIALS="/path/to/service-account-key.json". 5. Required IAM Roles: roles/compute.securityAdmin: Required to create, update, delete, or import Cloud Armor security policies and rules (use roles/compute.securityViewer for read-only policy audits). roles/logging.viewer: Required to inspect HTTP load balancer preview telemetry in Cloud Logging. 6. Scope and Regional Availability: Cloud Armor security policies can be Global (default for global external Application Load Balancers) or Regional (for regional external Application Load Balancers, for example, --region=us-central1; set a default region via gcloud config set compute/region us-central1). See Google Cloud Locations for regional availability. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/cloud-armor-crs-rule-upgrader