Skip to content

Commit 4d81652

Browse files
committed
lc filename extension
1 parent ca06fc9 commit 4d81652

File tree

7 files changed

+7
-7
lines changed

7 files changed

+7
-7
lines changed

articles/frontdoor/waf-front-door-create-portal.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,13 +62,13 @@ To see WAF in action, you can change the mode settings from **Detection** to **P
6262

6363
You can create a custom rule by selecting **Add custom rule** under the **Custom rules** section. This launches the custom rule configuration page. Below is an example of configuring a custom rule to block a request if the query string contains **blockme**.
6464

65-
![Change WAF policy mode](./media/waf-front-door-create-portal/customquerystring.png)
65+
![Change WAF policy mode](./media/waf-front-door-create-portal/customquerystring2.png)
6666

6767
### Default Rule Set (DRS)
6868

6969
Azure-managed Default Rule Set is enabled by default. To disable an individual rule within a rule group, expand the rules within that rule group, select the **check box** in front of the rule number, and select **Disable** on the tab above. To change actions types for individual rules within the rule set, select the check box in front of the rule number, and then select the **Change action** tab above.
7070

71-
![Change WAF Rule Set](./media/waf-front-door-create-portal/managed.png)
71+
![Change WAF Rule Set](./media/waf-front-door-create-portal/managed2.png)
7272

7373
## Next steps
7474

articles/frontdoor/waf-front-door-policy-configure-bot-protection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Create a basic WAF policy for Front Door by following the instructions described
3030
1. In the basic policy page that you created in the preceding section, under **Settings**, click **Rules**.
3131
2. In the details page, under the **Manage rules** section, from the drop-down menu, select the check box in front of the rule **BotProtection-preview-0.1**, and then select **Save** above.
3232

33-
![Bot protection rule](./media/waf-front-door-configure-bot-protection/botprotect.png)
33+
![Bot protection rule](./media/waf-front-door-configure-bot-protection/botprotect2.png)
3434

3535
## Next steps
3636

articles/frontdoor/waf-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.devlang: na
99
ms.topic: article
1010
ms.tgt_pltfrm: na
1111
ms.workload: infrastructure-services
12-
ms.date: 05/30/2019
12+
ms.date: 05/31/2019
1313
ms.author: kumud;tyao
1414
---
1515

@@ -24,7 +24,7 @@ Preventing such attacks in application code can be challenging and may require r
2424

2525
WAF for Front Door is a global and centralized solution. It is deployed on Azure network edge locations around the globe and every incoming request for a WAF enabled web application delivered by Front Door is inspected at the network edge. This allows WAF to prevent malicious attacks close to the attack sources, before they enter your virtual network and offers global protection at scale without sacrificing performance. A WAF policy can be easily linked to any Front Door profile in your subscription and new rules can be deployed within minutes, allowing you to respond quickly to changing threat patterns.
2626

27-
![Azure web application firewall](./media/waf-overview/web-application-firewall-overview.png)
27+
![Azure web application firewall](./media/waf-overview/web-application-firewall-overview2.png)
2828

2929
Azure WAF can also be enabled with Application Gateway. For more information, see [Web application firewall](../application-gateway/waf-overview.md).
3030

@@ -87,7 +87,7 @@ Azure-managed rule sets provide an easy way to deploy protection against a commo
8787
- Java attacks
8888
- Local file inclusion
8989
- PHP injection attacks
90-
- Remote command processing
90+
- Remote command executing
9191
- Remote file inclusion
9292
- Session fixation
9393
- SQL injection protection
@@ -103,7 +103,7 @@ Custom rules are always applied before rules in the Default Rule Set are evaluat
103103

104104
A managed Bot protection rule set can be enabled for your WAF to take custom actions on requests from known malicious IP addresses. The IP addresses are sourced from the Microsoft Threat Intelligence feed. [Intelligent Security Graph](https://www.microsoft.com/security/operations/intelligence) powers Microsoft threat intelligence and is used by multiple services including Azure Security Center.
105105

106-
![Bot Protection Rule Set](./media/waf-front-door-configure-bot-protection/BotProtect.png)
106+
![Bot Protection Rule Set](./media/waf-front-door-configure-bot-protection/BotProtect2.png)
107107

108108
> [!IMPORTANT]
109109
> Bot protection rule set is currently in public preview and is provided with a preview service level agreement. Certain features may not be supported or may have constrained capabilities. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for details.

0 commit comments

Comments
 (0)