[Network] Expose WAF rule paranoiaLevel and rule set displayName

Abierto
  • ¿Algo no está bien?
#33,879 2 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@necusjz ya está trabajando en esto.

Desde el 12/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

act-quality-productivity-squad Auto-Assign Azure CLI Team feature-request Network
Preconditions
  • No need to upgrade Python SDK or the Python SDK is ready.
Related command

az network application-gateway waf-config list-rule-sets

az network application-gateway waf-config list-dynamic-rule-sets

Resource Provider

Microsoft.Network/applicationGateways

Description of Feature or Work Requested

Two new read-only fields in api-version 2026-01-01:

  1. paranoiaLevel on each managed rule (ApplicationGatewayFirewallRule). Values PL1 to PL4. It is the OWASP CRS paranoia level of the rule, where PL1 is baseline detection and PL4 is strictest. Set only for DRS and OWASP rule sets. Customers need it to understand why a rule fires and whether to disable it.

  2. displayName on the rule set (ApplicationGatewayFirewallRuleSetPropertiesFormat). For example "Default Ruleset 2.2 (Latest, Recommended)" or "Core Ruleset 3.0 (Deprecated)". Today the CLI only shows ruleSetType and ruleSetVersion, for example OWASP 3.0, so customers cannot tell which version is current and which is deprecated.

Both are output only. No new parameters and no behavior change.

Minimum API Version Required

2026-01-01

Swagger PR link / SDK link

https://github.com/Azure/azure-rest-api-specs-pr/pull/29807

Request Example

{
"listRuleSets": {
"command": "az network application-gateway waf-config list-rule-sets",
"operation": "ApplicationGatewayAvailableWafRuleSets",
"response": {
"value": [
{
"name": "Microsoft_DefaultRuleSet_2.1",
"properties": {
"ruleSetType": "Microsoft_DefaultRuleSet",
"ruleSetVersion": "2.1",
"displayName": "Default Ruleset 2.1",
"ruleGroups": [
{
"ruleGroupName": "RFI",
"description": "Remote file inclusion",
"rules": [
{
"ruleId": 931100,
"ruleIdString": "931100",
"description": "Possible Remote File Inclusion (RFI) Attack: URL Parameter using IP Address",
"action": "AnomalyScoring",
"state": "Enabled",
"paranoiaLevel": "PL1"
}
]
}
]
}
}
]
}
},
"listDynamicRuleSets": {
"command": "az network application-gateway waf-config list-dynamic-rule-sets -l westus",
"operation": "ApplicationGatewayWafDynamicManifests_Get",
"response": {
"properties": {
"availableRuleSets": [
{
"ruleSetType": "Microsoft_DefaultRuleSet",
"ruleSetVersion": "2.2",
"displayName": "Default Ruleset 2.2 (Latest, Recommended)",
"status": "GA",
"tiers": [
"WAF_v2"
],
"ruleGroups": [
{
"ruleGroupName": "RFI",
"description": "Remote file inclusion",
"rules": [
{
"ruleId": 931100,
"ruleIdString": "931100",
"description": "Possible Remote File Inclusion (RFI) Attack: URL Parameter using IP Address",
"action": "AnomalyScoring",
"state": "Disabled",
"paranoiaLevel": "PL1"
}
]
}
]
}
],
"defaultRuleSet": {
"ruleSetType": "Microsoft_DefaultRuleSet",
"ruleSetVersion": "2.2",
"_note": "displayName is defined in the spec here but the service does not return it yet"
}
}
}
}
}

Target Date

01.01.2027

PM Contact

yuvalpery

Engineer Contact

shgoldbourt

Additional context

No response

Lenguaje dominante
Python
Estrellas
4.7k
Forks
3.5k
Merge medio
4 d 14 h
PR fusionados (30 d)
92

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/azure-cli

Todos los issues de Azure/azure-cli

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.