User Profile
davidfrazee
Joined 4 years ago
User Widgets
Recent Discussions
Re: Azure Firewall Manager
Brant_Boyd Hello Brant, that is an excellent question and I'd be happy to clarify this for you. Azure Firewall Manager itself is not a deployable resource and does not have a location that it references, it is purely a centralized security management service for your Azure Firewall Policies, Web Application Firewall Policies, DDoS Protection Plans, and Security Partner Providers. The resource that gets deployed to a specific region is the Azure Firewall Policy, but this is still considered to be a global resource. You can think of the Azure Firewall Policy as a construct, or image, that will be replicated and available throughout all of the Azure datacenters. To clarify your scenario, if the Azure Firewall Policy is deployed to West US, and you use this to manage Azure Firewalls in East US, Central US, etc., and there happens to be an outage at the West US datacenter, the Azure Firewall Policy will continue to service the Azure Firewall's globally with no impact.2.2KViews2likes0CommentsRe: Azure WAF - Resources for understanding policies
chilberto Hello Jeffrey, here are some resources that provide excellent guidance on how to understand WAF actions and logs for both Azure Application Gateway and Azure Front Door. The OWASP signature IDs use a set of regex pattern matching. For a particular rule ID, you can look through the glossary and see what the parameter combination the regex is looking for. For example, SQLi rule 942120 looks for a combination of is+not in a string. This regex looks for it as you can see in line 538 here SecRule ARGS_NAMES|ARGS|XML:/* "@rx (?i:(?:(?:^|\W)in[+\s]*\([\s\d\"]+[^()]*\)|\b(?:r(?:egexp|like)|isnull|xor)\b|<(?:>(?:\s+binary)?|=>?|<)|r(?:egexp|like)\s+binary|not\s+between\s+0\s+and|(?:like|is)\s+null|>[=>]|\|\||!=|&&))" \ By enabling Diagnostic settings on the Application Gateway and Front Door resources, we're able to send WAF specific logs to a log analytics workspace that allows you to consume and identify why certain requests have been blocked due to specific regex patterns identified. OWASP: owasp-modsecurity-crs/rules at v3.1/dev · SpiderLabs/owasp-modsecurity-crs (github.com) Application Gateway: CRS rule groups and rules - Azure Web Application Firewall | Microsoft Docs Monitoring metrics for Azure Application Gateway Web Application Firewall metrics | Microsoft Docs Troubleshoot - Azure Web Application Firewall | Microsoft Docs Front Door: Azure Web Application Firewall on Azure Front Door DRS rule groups and rules | Microsoft Docs Azure Web Application Firewall monitoring and logging | Microsoft Docs1.9KViews0likes0Comments
Recent Blog Articles
Getting Started with Azure WAF REST API for Azure Front Door: A Step-by-Step Guide
Learn how to create, update, and delete Azure WAF Policies for Azure Front Door using REST API. We'll cover how to build and apply different configurations to customize an Azure WAF Policy to ...2.6KViews0likes0CommentsGetting Started with Azure WAF REST API for Application Gateway: A Step-by-Step Guide
Learn how to create, update, and delete Azure WAF Policies for Application Gateway using REST API. We'll cover how to build and apply different configurations to customize an Azure WAF Policy ...4KViews2likes0CommentsAzure Firewall's Auto Learn SNAT Routes: A Guide to Dynamic Routing and SNAT Configuration
Do you want to learn how to use Azure Firewall's Auto-learn SNAT routes feature? This feature can help you optimize your network configuration in Azure by automatically learning the out-of-network ad...8.8KViews3likes0Comments