liveBook · Manning

Security policy

As explained in Azure Security

A security policy is an Azure Front Door configuration that associates a web application firewall policy with a Front Door profile.

A security policy connects a web application firewall policy to an Azure Front Door profile. The association applies WAF protection to selected Front Door domains and path patterns. section 3.3.2

WAF association

A policy named contososecurity associates the AzFrontDoorWafPolicy WAF policy with the contosofrontend endpoint in the myWAFAzD profile. The WAF can operate in detection or prevention mode; prevention blocks matching requests, so tuning helps avoid blocking legitimate traffic. section 3.3.2

How Azure Security covers it

How deep it goes
Shows Azure CLI creation, resource identifiers, path matching, returned status, and detection-versus-prevention implications.
Examples
Uses the contososecurity policy, contosofrontend endpoint, /* path pattern, and AzFrontDoorWafPolicy resource.
What it assumes
Assumes an Azure Front Door profile, endpoint, and WAF policy already exist before creating the security policy.
What you can do after
Configure it via Azure CLI and verify that the WAF policy is associated with the intended Front Door endpoint.
How it connects
Connects Azure Front Door with WAF policies, managed rule sets, bot protection, detection mode, and prevention mode.
Cover of Azure Security
liveBookmanning.com
Read Azure Security on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.