How to identify WAF Mode which is getting used

@Priyanka Mahadik

Welcome to Microsoft Q&A and thank you for posting your questions here!

To understand your question, you were asking reason Azure WAF showing detection mode instead of prevention mode and to identify the mode of Azure WAF which is been used.

Firstly, I have seen from your screenshot your good job, let us break it down little should there be any steps overlooked.

To identify prevention mode on Azure web application firewall, you should follow these steps:

• Sign-in to the Azure portal.
• In the left-hand menu, click on Application Gateway.
• Select your application gateway from the list.
• In the left-hand menu, click on Web application firewall.
• Click on Policy.
• Under Managed rules, click on Prevention mode.

I wanted to believe you have done it right, but note:

If prevention mode is enabled, the WAF will block intrusions and attacks that the rules detect and return a “403 unauthorized access” exception.

Read Overview and read more about Policy Setting

Now, the logs captured on the Application Gateway of Azure Web Application Firewall shows Detection mode only because the firewall log is generated only if you have enabled it for each application gateway. The web application firewall must also be configured on an application gateway.

Read more on web application firewall logs.

Also, you can enable logs to inspect what is happening with each request. Firewall logs give insight into what the WAF is evaluating, matching, and blocking. With Log Analytics, you can examine the data inside the firewall logs to give even more insights.

Read more here: https://zcusa.951200.xyz/en-us/azure/application-gateway/log-analytics

In summary, to identify Prevention and Detection Mode on Azure web application firewall.

Detection mode: Monitors and logs all threat alerts. You turn on logging diagnostics for Application Gateway in the Diagnostics section. You must also make sure that the WAF log is selected and turned on. Web application firewall doesn’t block incoming requests when it’s operating in Detection mode.

Read more here: https://zcusa.951200.xyz/en-us/azure/web-application-firewall/ag/ag-overview

Prevention mode: After you’ve tuned your WAF, you should configure it to run in prevention mode. By running in prevention mode, you ensure the WAF actually blocks requests that it detects are malicious. Running in detection mode is useful while you tune and configure your WAF but provides no protection.

Read more here for best practice: https://zcusa.951200.xyz/en-us/azure/web-application-firewall/ag/best-practices

I hope this helps you resolve your issue with Azure Logic Apps! If this answer solves your issue, please vote for it so other community members know that it is a useful answer. PS: Do not hesitate to let me know if you have any other questions.

Best Regards,

Sina

Hello @Priyanka Mahadik ,

Apologies for the delay in response.

Looking at your screenshots, the configuration seem fine. The WAF policy mode is set to Prevention and the listener is associated to the WAF policy but the logs seem weird. Are the logs for the same Application gateway named "AGW-Sandbox-CI"?

Also, are there any other WAF policies in the same resource group "RG-SANDBOX-CI"?

Regards,

Gita

Yes, the logs are of the same application gateway and there is one more WAF that is in detection mode in the same resource group.