Skip to content

Commit 1661b16

Browse files
committed
add WAF geomatch to security hub
1 parent 4e851e8 commit 1661b16

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

articles/networking/security/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,8 @@ additionalContent:
6969
url: ../../firewall/detect-malware-with-sentinel.md
7070
- text: Detect new threats
7171
url: ../../web-application-firewall/waf-new-threat-detection.md
72+
- text: Enhance network security using custom WAF geomatch rules
73+
url: ../../web-application-firewall/geomatch-custom-rules-examples.md
7274
- title: Training
7375
links:
7476
- text: Introduction to Azure Firewall

articles/web-application-firewall/geomatch-custom-rules-examples.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ This article introduces Azure WAF geomatch custom rules and shows you how to cre
2727

2828
Geomatch custom rules enable you to meet diverse security goals, such as blocking requests from high-risk areas and permitting requests from trusted locations. They're particularly effective in mitigating distributed denial-of-service (DDoS) attacks, which seek to inundate your web application with a multitude of requests from various sources. With geomatch custom rules, you can promptly pinpoint and block regions generating the most DDoS traffic, while still granting access to legitimate users. In this article, you learn about various custom rule patterns that you can employ to optimize your Azure WAF using geomatch custom rules.
2929

30-
## Scenario 1: Block traffic from all countries except "x"
30+
## Scenario 1 - Block traffic from all countries except "x"
3131

3232
Geomatch custom rules prove useful when you aim to block traffic from all countries, barring one. For instance, if your web application caters exclusively to users in the United States, you can formulate a geomatch custom rule that obstructs all requests not originating from the US. This strategy effectively minimizes your web application’s attack surface and deters unauthorized access from other regions. This specific technique employs a negating condition to facilitate this traffic pattern. For creating a geomatch custom rule that obstructs traffic from all countries except the US, refer to the following portal, Bicep, and PowerShell examples:
3333

0 commit comments

Comments
 (0)