Network - 26882 - Bot protection ruleset is enabled and assigned in Application Gateway WAF#1112
Merged
Network - 26882 - Bot protection ruleset is enabled and assigned in Application Gateway WAF#1112
Conversation
alexandair
requested changes
Apr 1, 2026
Collaborator
alexandair
left a comment
alexandair
left a comment
There was a problem hiding this comment.
@sandeepjha000 Please, address my feedback.
| @@ -0,0 +1,12 @@ | |||
| Azure Application Gateway Web Application Firewall (WAF) provides bot protection through the Microsoft Bot Manager ruleset, which identifies and categorizes automated traffic based on behavioral patterns, known bot signatures, and IP reputation. Without bot protection enabled, threat actors leverage automated tools to perform large-scale attacks that would be impractical manually: credential stuffing attacks that test stolen username and password combinations across login endpoints at thousands of attempts per minute, content scraping that extracts proprietary data and pricing information for competitive exploitation, inventory hoarding bots that deplete product availability for legitimate customers, and application-layer denial of service attacks that overwhelm backend resources. | |||
|
|
|||
| These automated attacks often originate from distributed botnets that rotate IP addresses to evade simple rate limiting, making signature-based bot detection essential. The Bot Manager ruleset classifies bots into categories including known good bots (search engines), known bad bots (scrapers, spammers), and unknown bots, allowing granular policy enforcement. Without this classification, malicious bot traffic blends with legitimate requests, consuming application resources and enabling fraud that damages revenue and customer trust. By enabling the Bot Manager ruleset on Application Gateway WAF, organizations ensure automated attacks are identified and blocked before they can exploit application vulnerabilities or exhaust backend capacity. | |||
Collaborator
There was a problem hiding this comment.
"By enabling the Bot Manager ruleset on Application Gateway WAF, organizations ensure automated attacks are identified and blocked before they can exploit application vulnerabilities or exhaust backend capacity."
Where is this sentence coming from? It's not in the spec.
| function Test-Assessment-26882 { | ||
| [ZtTest( | ||
| Category = 'Azure Network Security', | ||
| ImplementationCost = 'Low', |
Collaborator
There was a problem hiding this comment.
Service = ('Azure') is missing.
| return | ||
| } | ||
|
|
||
| # Fail if any attached policy is not enabled, not in Prevention mode, or missing the Microsoft_BotManagerRuleSet |
Collaborator
There was a problem hiding this comment.
Duplicated pass/fail logic between assessment and report
The three-condition check (Enabled + Prevention + BotManager ruleset) appears in both the $failingPolicies filter and the $statusDisplay computation. Consider precomputing a $isPassing property on each policy to avoid logic drift:
foreach ($policy in $policies) {
$policy | Add-Member -NotePropertyName IsPassing -NotePropertyValue (
$policy.EnabledState -eq 'Enabled' -and
$policy.Mode -eq 'Prevention' -and
($policy.ManagedRuleSets | Where-Object { $_.ruleSetType -eq 'Microsoft_BotManagerRuleSet' }).Count -gt 0
)
}
$passed = ($policies | Where-Object { -not $_.IsPassing }).Count -eq 0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SPEC-26882