Index › Vendors › AWS WAF + Bot Control · September 2026 Edition

AWS · 1 category · Named, not ranked

AWS WAF + Bot Control

7Judge labels

0First choices

0Negative labels

6 of 12Models named it

1Category

September 2026 Edition. Every number here is derived from the raw labels under vendor table vv2026-09.2, every buyer segment counted.

Standing

3 labels, too few to rank

A product needs 10 labels in a category before a share or quadrant is stated. AWS WAF + Bot Control was named 3 times in WAF, where Cloudflare led with 55%. The labels and the evidence are below, counted exactly.

By buyer segmentRead the same way at every buyer size.

Small business11 of 77

under the label threshold

Mid-market17 of 87

under the label threshold

Enterprise27 of 94

under the label threshold

In waf · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named AWS WAF + Bot Control for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Web application firewalls	Network and edge	0%	17 of 87	0%	3	under 10 labels · led by Cloudflare at 55%

Movement

This is the first edition on this tier, so no move can be computed for AWS WAF + Bot Control yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated AWS WAF + Bot Control across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	Alternative	Labels
Claude Haiku 4.5	0	0
GPT-5.4 mini	0	0
Gemini 3.5 Flash	0	0
Perplexity Sonar	0	0
Grok 4.1 Fast	1	1
Mistral Small	0	0
DeepSeek V4 Flash	0	0
Llama 4 Maverick	0	0
Qwen 3.7 Flash	0	0
Kimi K2	1	1
GLM 4.7 FlashX	0	0
MiniMax M2.5	1	1

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct0 labelsNone

Paraphrase7 labelsNone

Comparative0 labelsNone

Budget-constrained0 labelsNone

Scale-constrained0 labelsNone

Negative0 labelsNone

First choiceAlternativeMentionNegative7 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“Best if your stack is AWS-native (e.g., ALB/API Gateway). Pay-as-you-go is cost-effective for variable traffic but requires more rule tuning.” Grok 4.1 Fast · WAF · paraphrase prompt · alternative

“Caveat: Costs can balloon unpredictably at scale, and bot protection is an expensive add-on.” Kimi K2 · WAF · paraphrase prompt · alternative

“AWS WAF Bot Control (if already on AWS)” MiniMax M2.5 · WAF · paraphrase prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

No model argued against it.

Named alongside

The products named in the same answers as AWS WAF + Bot Control, over the 7 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and AWS WAF + Bot Control was named but was not.

ProductSame answerTook the first choice insteadHead to head

Cloudflare4 of 74Not in the top three

Imperva3 of 70Not in the top three

Akamai2 of 70Not in the top three

Imperva Cloud WAF2 of 70Not in the top three

Akamai Kona Site Defender + Akamai Bot Manager1 of 71Not in the top three

Cloudflare WAF + Bot Management1 of 71Not in the top three

Cloudflare WAF + Super Bot Fight Mode1 of 71Not in the top three

AWS WAF1 of 70Not in the top three

Akamai's Bot Manager1 of 70Not in the top three

Barracuda1 of 70Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named AWS WAF + Bot Control. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 7 of the 7 answers that named AWS WAF + Bot Control and are not a share of its labels.

Domains cited

cyberpress.org4

cybersecuritynews.com4

cipherssecurity.com3

docs.aws.amazon.com3

openappsec.io3

techplained.com3

akamai.com2

cequence.ai2

developers.cloudflare.com2

guptadeepak.com2

No domain is on file for AWS WAF + Bot Control, so its own site is not marked.

Pages cited

cyberpress.org/waf-solutions-by-business-size4

cipherssecurity.com/best-waf-providers-20263

cybersecuritynews.com/best-web-application-firewall-solutions3

techplained.com/best-waf-providers3

cequence.ai/learn/bot-management/choosing-bot-management-vendors-top-8-compared2

cybersecuritynews.com/best-web-application-firewall-solutions/amp2

developers.cloudflare.com/bots/get-started/bot-management2

docs.aws.amazon.com/waf/latest/developerguide/waf-bot-control.html2

Pages are listed as the models cited them.

Names read as AWS WAF + Bot Control

What the judge wrote, as written, with how often. The vendor table decides that these count as AWS WAF + Bot Control; a claim can dispute any of them.

AWS WAF Bot Control 1

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when AWS WAF + Bot Control's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as AWS WAF + Bot Control, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at the vendor's own domain is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.