A WAF Policy that Blocks rather than Narrates
Detection mode evaluates every rule, logs every match and forwards every request - the dashboard fills with blocked-looking entries while the backend receives them all. Prevention by default, Detection only by name. A policy attached to no listener protects nothing, so the attached listeners are an output; every exclusion is a hole and has to carry a reason.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live test pending (no cloud run yet)
Last verified 2026-09-14 · how we verify
Use it from the registry
terraform · opentofumodule "waf_policy" {
source = "www.iac-bazaar.com/iac-bazaar/azure-waf-policy/azure"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
azure-waf-policy
A shared Web Application Firewall policy for Azure Application Gateway that
blocks rather than narrates. Works with Terraform and OpenTofu (>= 1.6),
azurerm provider >= 4.0, < 5.0.
Detection mode is a smoke alarm with the siren cut. Every rule evaluates,
every match is written to the log, the dashboard fills with blocked-looking
entries - and the request is forwarded to the backend. Microsoft's guidance is
to run Detection while tuning and switch to Prevention afterwards, which is
reasonable, and which is also how policies stay in Detection for years: the
switch is a one-word change nobody owns. This module defaults to Prevention
and refuses Detection without accept_detection_mode = true.
A policy attached to nothing protects nothing. The policy is standalone; it
takes effect only where an Application Gateway, listener or path rule
references it, and it renders in the portal as a fully configured WAF either
way. attached_listener_ids is an output so a test can check the policy is in
front of something.
Every exclusion is a hole, so each one needs a reason. Azure gives exclusions no description field. This module requires one anyway and refuses an exclusion that is not explained - they are added under time pressure by whoever is on call, and the next person needs to know whether the false positive still exists.
A custom rule with action = "Log" is Detection mode for one rule. Allowed,
and counted in log_only_rule_count.
Verification
Static validation runs tofu fmt, init, validate, tflint and checkov.
This module has not yet had a live test, so it is published as statically
validated with its live test pending and does not carry the live-tested mark.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
Related modules
azure-firewall
Every security feature on this service defaults to telling you, not to stopping it: threat_intelligence_mode defaults to Alert, which logs traffic to known-malicious destinations and forwards it, and intrusion detection does the same. Deny for both here, with the DNS proxy on so FQDN rules and the client agree on an answer.
azure-bastion-jumpbox
Bastion (Developer/Basic/Standard SKU) with optional hardened Linux VM, JIT-style NSG rules and boot diagnostics for secure VM access without public IPs.
azure-defender-for-cloud
A subscription with no Defender plan still has a full Defender for Cloud page: a Secure Score, hundreds of recommendations, a compliance dashboard - and not one threat detection, because those come from the paid plans, each Off until somebody turns it on. Sets Standard per resource type, always creates the security contact, and defaults alert notifications on.
azure-entra-id-baseline
App registrations, service principals, groups and federated credentials (OIDC for GitHub/Terraform) - the identity plumbing every Azure org rebuilds by hand.
azure-pim
Azure defaults for an activation policy require MFA and a justification and no approval, so an eligible Owner activates alone at 3am with the reason fix; and eligibility itself is permanent unless somebody sets an end date. Manages the role policy per scope with approval required for Owner-class roles, gives every eligible assignment an expiry, and time-boxes the active ones kept for break-glass.
azure-managed-identity
A map-driven module creating one or many user-assigned managed identities, each with optional workload identity federation (OIDC) and least-privilege RBAC role assignments - no secrets to rotate.