Refer a site. You both get 10% off for 3 months. Get your referral link

EXAMPLE DATATwo fictional sites: Example University (example.com) and Example Goods (example-store.example), a WordPress and WooCommerce store. Not customers. Not live traffic.

Example Tuning

The WAF that tells you what's safe to block.

These are Tuning views for fictional sites. Pick Promote, Hold, or Needs allowlist. Each card is the real decision, with the why and the evidence. A human clicks Promote. Nothing blocks automatically.

The buttons below do not change a rule. Rules start in count. After 24 hours, your dashboard shows what's safe to block — one click.

Campus site

example.com

EXAMPLE DATA

Example University · Tuning · invented counts. Not a customer. Not live traffic.

A human clicks Promote. Nothing blocks automatically.

  • PromoteQuiet in the observed window — review important workflows before blocking.
  • HoldStill watching or noisy — keep counting.
  • Needs allowlistLooks like real visitors — allow that traffic first.

Promote

Linux server exploits (linux_exploits) counted 12 hit(s) in the 24-hour window, and every sample looks like a probe (GET /.env).

Promoting blocks those attack shapes, not a known-good login or payment path. You still click Promote — the Advisor does not flip the rule.

A human clicks Promote. Nothing blocks automatically. The button on the card does not send that click.

Hold

Common attacks (OWASP) (common_attacks) flagged a large share of requests (620 counted) in the 24-hour window.

That pattern often includes real campus traffic — LMS, registration POSTs, monitoring, CMS, or SSO paths. Keep it in count until you confirm the hits are abuse, not students or editors. The Advisor will not promote this for you.

What would change this. the count has to fall under 50 and the share under 15 percent before an explained attack can say promote; this size stays on hold

Needs allowlist

Known exploits (known_exploits) counted POST /saml/acs.

It looks like SSO in the 24-hour window. Allow that path before you promote. You still click — the Advisor does not block.

What would change this. save the exception on this card when the log names one path and one method

Allow POST /saml/acs. Save that exception on this card when the log names it. You still decide.

Example dataInvented counts for Example University (example.com). Not a customer. Not live traffic.

Advisor

Tuning is count → promote. Rules start in count. After 24 hours, the Advisor names what's safe — you click once. Nothing auto-blocks. It never flips a rule to block on its own. Rule-based checks on this site's logs — the same evidence always gives the same answer.

The 24-hour window is over. Promote quiet rules, or hold / allowlist anything noisy.

Count window

Each managed rule in count is on this track. Counted hits and site requests are the shared 24-hour CloudWatch rollup, so they match Analytics and the Advisor. A missing series says not confirmed, not zero.

  1. StartRules enter count
  2. 12hseries
  3. 24hdecision
  4. 7dyour click
  • Site requests in 24h: 4,000
  • CloudWatch series: 24 hours
  • In count for 30 hours, since this site was protected
  • Linux server exploitsIn count for 30 hours, since this site was protected
    • Counted hits in 24h: 12
    Before Promote

    Nothing else. The Advisor can say Promote.

    What happens next. Click Promote if you want this rule in block. The samples are attacks and the count is within 8× the sample rows. The Advisor does not flip the rule.

  • Common attacks (OWASP)In count for 30 hours, since this site was protected
    • Counted hits in 24h: 620
    Before Promote
    • A count under 50 and a share under 15% of site requests, with every sample an explained attack. An explained attack at 15% or more stays on Hold.

    What would change this. the count has to fall under 50 and the share under 15 percent before an explained attack can say promote; this size stays on hold

    What happens next. Hold this rule. A large share of traffic often includes real visitors. An explained attack at this share stays on Hold too.

  • Known exploitsIn count for 30 hours, since this site was protected
    • Counted hits in 24h: 64
    Before Promote
    • A complete log that names one path and one method, then a save on this card. A partial or empty log cannot supply the exception.

    What would change this. save the exception on this card when the log names one path and one method

    What happens next. Save the exception on this card when the log names one path and one method. A partial or empty log stays in count. Promote stays a separate click.

Virtual patch available

Example dataInvented advisory. Not a customer. Not live traffic.

A managed rule group can watch this class in count. You click Add in count mode. A rule that is already on stays as it is. Nothing here blocks on its own.

Catalog 2026.10.1

  • Log4Shell-style JNDI strings

    Relevant

    JNDI lookup strings in a header, query, or path.

    Managed rule group: Known exploits

    Already on in count for this site.

    A sampled request matched a pattern this group watches.

  • Drupalgeddon-style form API probes

    General advisory

    Form API arrays such as a render callback on a user form.

    Managed rule group: PHP application attacks

    Not on for this site.

    General advisory. No signal on this site ties this class to the site.

  • WordPress plugin and xmlrpc probes

    Relevant

    Plugin paths and xmlrpc calls used to look for weak plugins.

    Managed rule group: WordPress protection

    Not on for this site.

    A sampled request matched a pattern this group watches.

  • Shellshock

    General advisory

    A shell function prefix in a header or query, the Shellshock shape.

    Managed rule group: Unix / POSIX exploits

    Not on for this site.

    General advisory. No signal on this site ties this class to the site.

Rule-based notes from this count window. You still click once.

1 ready to promote · 1 needs an allowlist · 1 on hold.

  • PromoteQuiet in the observed window — review important workflows before blocking.
  • HoldStill watching or noisy — keep counting.
  • Needs allowlistLooks like real visitors — allow that traffic first.
  • Linux server exploitsNew protectionPromote

    AWS published Linux server exploits version Version_2.1 (this site was on Version_2.0). The group stays in count.

    Linux server exploits (linux_exploits) counted 12 hit(s) in the 24-hour window, and every sample looks like a probe (GET /.env).

    Promoting blocks those attack shapes, not a known-good login or payment path. You still click Promote — the Advisor does not flip the rule.

    Evidence
    • 24h window
    • Counted 12
    • GET /.env
    Top paths in the sample
    • 3GET /.env
    • 2GET /wp-config.php
    • 1GET /.git/config

    Sample rows only. Counted 12 is the full 24h window.

    Sample requests
    • GET /.env · 203.0.113.xx · attack
    • GET /wp-config.php · 203.0.113.xx · attack
    • GET /.git/config · 198.51.100.xx · attack
    If you promote
    • 12 counted request(s) on Linux server exploits in this 24h window would start being blocked.
    • Includes GET /.env.
    • Only this rule switches to block. Undo puts it back in count — we do not auto-rollback.
  • Common attacks (OWASP)Hold

    Low confidence to promote — review the evidence first. You still click once.

    Common attacks (OWASP) (common_attacks) flagged a large share of requests (620 counted) in the 24-hour window.

    That pattern often includes real campus traffic — LMS, registration POSTs, monitoring, CMS, or SSO paths. Keep it in count until you confirm the hits are abuse, not students or editors. The Advisor will not promote this for you.

    Blocking. This rule is at least 15% of site requests, and the samples are not an explained attack. This rule is about 16% of site requests. This rule counted 620 hits. A large share often includes real visitors.

    What would clear this. A known-good form becomes Needs allowlist. An explained attack at this share stays Hold. Promote would need the count under 50 and under 15%, with every sample an explained attack.

    Next look. The Advisor reads this again when you open Tuning, and on the check that runs about every 15 minutes. That look does not promote the rule.

    Next step. Investigate one matching request. That asks a person to look at that request. It does not promote this rule, and it does not change this Hold.

    Evidence
    • 24h window
    • Counted 620
    • GET /search
    Top paths in the sample
    • 2GET /search
    • 1GET /calendar
    • 1GET /news/story

    Sample rows only. Counted 620 is the full 24h window.

    Sample requests
    • GET /search · 203.0.113.xx
    • GET /calendar · 203.0.113.xx
    • GET /news/story · 198.51.100.xx
  • Known exploitsNeeds allowlist

    Low confidence to promote — review the evidence first. You still click once.

    Known exploits (known_exploits) counted POST /saml/acs.

    It looks like SSO in the 24-hour window. Allow that path before you promote. You still click — the Advisor does not block.

    What would change this. save the exception on this card when the log names one path and one method

    Evidence
    • 24h window
    • Counted 64
    • POST /saml/acs
    Top paths in the sample
    • 4POST /saml/acs

    Sample rows only. Counted 64 is the full 24h window.

    Sample requests
    • POST /saml/acs · 192.0.2.xx · SSO

    False-positive risk: SSO.

    Allow this path

    Save this exception on the card before you promote. The path and method come from this log. The rule stays in count until you click.

    Allow POST /saml/acs

    Flagged: POST /saml/acs · SSO · 192.0.2.xx · this path only

    What this lets through
    • POST /saml/acs · SSO · 192.0.2.xx
    • Allows POST /saml/acs exactly.
    • Only Known exploits skips that traffic. Other protections still inspect it.
    • This does not turn the rule off. Count and block stay as they are until you promote.
    • No attack sample in this evidence. Other paths stay inspected.

    Known exploits counted this traffic. The exception skips only what the preview says.

    1. Review what this lets through and what stays blocked.
    2. Save the exception. Nothing is written before that.
    3. This rule is checked again after the save. Promote is still a separate click.
Since you promoted

Count mode does not block. Each rule says what the firewall read showed. A missing sample is not a result. Put a rule back in count on its card if real visitors are blocked. We do not do that for you.

SQL injectionPromoted

Example only. This is not a firewall read.

  • Invented traffic. This panel does not call the rule blocking.
  • A missing sample is not a result.

WordPress and WooCommerce store

EXAMPLE DATAExample Goods (example-store.example). Fictional store. Not a customer. Not live traffic.

A new site starts four groups in count: common attacks, known exploits, SQL injection, and malicious IPs. In this example a person already promoted malicious IPs. The other three are still in count.

Bot management and account-fraud protection are available after setup. They are not on in this example, and they are not on by default. WordPress and WooCommerce templates are a later step on a real site: they add more groups in count and do not promote. They are not applied here.

Counted samples include login, a public media file, cart, and checkout. Checkout is Needs allowlist, with login and cart on that same card. The media file sat with catalog pages, so that rule stays Hold.

We provision and maintain the shield, help with DNS, and review tuning when you request it. You approve blocking changes. Support is by email; we are not watching every site around the clock. A human clicks Promote. Nothing blocks automatically. A real store records login, media, cart, and checkout on the Launch checklist beside Tuning, then requests a tuning review.

example-store.example

EXAMPLE DATA

Example Goods · Tuning · invented counts. Not a customer. Not live traffic.

A human clicks Promote. Nothing blocks automatically.

  • PromoteQuiet in the observed window — review important workflows before blocking.
  • HoldStill watching or noisy — keep counting.
  • Needs allowlistLooks like real visitors — allow that traffic first.

Promote

SQL injection (sql_injection) counted 12 hit(s) in the 24-hour window, and every sample looks like a probe (GET /.env).

Promoting blocks those attack shapes, not a known-good login or payment path. You still click Promote — the Advisor does not flip the rule.

A human clicks Promote. Nothing blocks automatically. The button on the card does not send that click.

Hold

Common attacks (OWASP) (common_attacks) flagged a large share of requests (620 counted) in the 24-hour window.

That pattern often includes real campus traffic — LMS, registration POSTs, monitoring, CMS, or SSO paths. Keep it in count until you confirm the hits are abuse, not students or editors. The Advisor will not promote this for you.

What would change this. the count has to fall under 50 and the share under 15 percent before an explained attack can say promote; this size stays on hold

Needs allowlist

Known exploits (known_exploits) counted POST /checkout/.

It looks like registration POSTs, payment, CMS paths, login in the 24-hour window. Allow that path before you promote. You still click — the Advisor does not block.

What would change this. save the exception on this card when the log names one path and one method

Allow POST /checkout/. Save that exception on this card when the log names it. You still decide.

Example dataInvented counts for Example Goods (example-store.example), a fictional WordPress and WooCommerce store. Not a customer. Not live traffic.

Advisor

Tuning is count → promote. Rules start in count. After 24 hours, the Advisor names what's safe — you click once. Nothing auto-blocks. It never flips a rule to block on its own. Rule-based checks on this site's logs — the same evidence always gives the same answer.

The 24-hour window is over. Promote quiet rules, or hold / allowlist anything noisy.

Count window

Each managed rule in count is on this track. Counted hits and site requests are the shared 24-hour CloudWatch rollup, so they match Analytics and the Advisor. A missing series says not confirmed, not zero.

  1. StartRules enter count
  2. 12hseries
  3. 24hdecision
  4. 7dyour click
  • Site requests in 24h: 4,000
  • CloudWatch series: 24 hours
  • In count for 30 hours, since this site was protected
  • SQL injectionIn count for 30 hours, since this site was protected
    • Counted hits in 24h: 12
    Before Promote

    Nothing else. The Advisor can say Promote.

    What happens next. Click Promote if you want this rule in block. The samples are attacks and the count is within 8× the sample rows. The Advisor does not flip the rule.

  • Common attacks (OWASP)In count for 30 hours, since this site was protected
    • Counted hits in 24h: 620
    Before Promote
    • A count under 50 and a share under 15% of site requests, with every sample an explained attack. An explained attack at 15% or more stays on Hold.

    What would change this. the count has to fall under 50 and the share under 15 percent before an explained attack can say promote; this size stays on hold

    What happens next. Hold this rule. A large share of traffic often includes real visitors. An explained attack at this share stays on Hold too.

  • Known exploitsIn count for 30 hours, since this site was protected
    • Counted hits in 24h: 64
    Before Promote
    • A complete log that names one path and one method, then a save on this card. A partial or empty log cannot supply the exception.

    What would change this. save the exception on this card when the log names one path and one method

    What happens next. Save the exception on this card when the log names one path and one method. A partial or empty log stays in count. Promote stays a separate click.

Virtual patch available

Example dataInvented advisory. Not a customer. Not live traffic.

A managed rule group can watch this class in count. You click Add in count mode. A rule that is already on stays as it is. Nothing here blocks on its own.

Catalog 2026.10.1

  • Drupalgeddon-style form API probes

    General advisory

    Form API arrays such as a render callback on a user form.

    Managed rule group: PHP application attacks

    Not on for this site.

    General advisory. No signal on this site ties this class to the site.

  • WordPress plugin and xmlrpc probes

    Relevant

    Plugin paths and xmlrpc calls used to look for weak plugins.

    Managed rule group: WordPress protection

    Not on for this site.

    A sampled request matched a pattern this group watches.

  • Shellshock

    General advisory

    A shell function prefix in a header or query, the Shellshock shape.

    Managed rule group: Unix / POSIX exploits

    Not on for this site.

    General advisory. No signal on this site ties this class to the site.

Rule-based notes from this count window. You still click once.

1 ready to promote · 1 needs an allowlist · 1 on hold.

  • PromoteQuiet in the observed window — review important workflows before blocking.
  • HoldStill watching or noisy — keep counting.
  • Needs allowlistLooks like real visitors — allow that traffic first.
  • SQL injectionPromote

    SQL injection (sql_injection) counted 12 hit(s) in the 24-hour window, and every sample looks like a probe (GET /.env).

    Promoting blocks those attack shapes, not a known-good login or payment path. You still click Promote — the Advisor does not flip the rule.

    Evidence
    • 24h window
    • Counted 12
    • GET /wp-config.php
    Top paths in the sample
    • 2GET /.env
    • 2GET /.git/config
    • 2GET /wp-config.php

    Sample rows only. Counted 12 is the full 24h window.

    Sample requests
    • GET /wp-config.php · 203.0.113.xx · attack
    • GET /.env · 198.51.100.xx · attack
    • GET /.git/config · 198.51.100.xx · attack
    If you promote
    • 12 counted request(s) on SQL injection in this 24h window would start being blocked.
    • Includes GET /wp-config.php.
    • Only this rule switches to block. Undo puts it back in count — we do not auto-rollback.
  • Common attacks (OWASP)Hold

    Low confidence to promote — review the evidence first. You still click once.

    Common attacks (OWASP) (common_attacks) flagged a large share of requests (620 counted) in the 24-hour window.

    That pattern often includes real campus traffic — LMS, registration POSTs, monitoring, CMS, or SSO paths. Keep it in count until you confirm the hits are abuse, not students or editors. The Advisor will not promote this for you.

    Blocking. This rule is at least 15% of site requests, and the samples are not an explained attack. This rule is about 16% of site requests. This rule counted 620 hits. A large share often includes real visitors.

    What would clear this. A known-good form becomes Needs allowlist. An explained attack at this share stays Hold. Promote would need the count under 50 and under 15%, with every sample an explained attack.

    Next look. The Advisor reads this again when you open Tuning, and on the check that runs about every 15 minutes. That look does not promote the rule.

    Next step. Investigate one matching request. That asks a person to look at that request. It does not promote this rule, and it does not change this Hold.

    Evidence
    • 24h window
    • Counted 620
    • GET /wp-content/uploads/2026/10/wool-hat.jpg
    Top paths in the sample
    • 2GET /product/wool-hat
    • 2GET /shop/
    • 2GET /wp-content/uploads/2026/10/wool-hat.jpg

    Sample rows only. Counted 620 is the full 24h window.

    Sample requests
    • GET /wp-content/uploads/2026/10/wool-hat.jpg · 203.0.113.xx · media upload
    • GET /product/wool-hat · 203.0.113.xx
    • GET /shop/ · 203.0.113.xx
  • Known exploitsNeeds allowlist

    Low confidence to promote — review the evidence first. You still click once.

    Known exploits (known_exploits) counted POST /checkout/.

    It looks like registration POSTs, payment, CMS paths, login in the 24-hour window. Allow that path before you promote. You still click — the Advisor does not block.

    What would change this. save the exception on this card when the log names one path and one method

    Evidence
    • 24h window
    • Counted 64
    • POST /checkout/
    Top paths in the sample
    • 4POST /checkout/
    • 2POST /cart/
    • 2POST /wp-login.php

    Sample rows only. Counted 64 is the full 24h window.

    Sample requests
    • POST /checkout/ · 192.0.2.xx · registration POSTs
    • POST /cart/ · 192.0.2.xx · registration POSTs
    • POST /wp-login.php · 192.0.2.xx · CMS paths

    False-positive risk: registration POSTs, payment, CMS paths, login.

    Allow this path

    Save this exception on the card before you promote. The path and method come from this log. The rule stays in count until you click.

    Allow POST /checkout/

    Flagged: POST /checkout/ · registration POSTs · 192.0.2.xx · this path only

    What this lets through
    • POST /checkout/ · registration POSTs · 192.0.2.xx
    • Allows POST /checkout/ exactly.
    • Only Known exploits skips that traffic. Other protections still inspect it.
    • This does not turn the rule off. Count and block stay as they are until you promote.
    • No attack sample in this evidence. Other paths stay inspected.

    Known exploits counted this traffic. The exception skips only what the preview says.

    1. Review what this lets through and what stays blocked.
    2. Save the exception. Nothing is written before that.
    3. This rule is checked again after the save. Promote is still a separate click.
Since you promoted

Count mode does not block. Each rule says what the firewall read showed. A missing sample is not a result. Put a rule back in count on its card if real visitors are blocked. We do not do that for you.

Malicious IP blockingPromoted

Example only. This is not a firewall read.

  • Invented traffic. This panel does not call the rule blocking.
  • A missing sample is not a result.

Questions

Is Example University a real customer?

No. Example University and example.com on this page are example data: an invented site and invented counts. Not a customer. Not live traffic.

Does a Promote click on this page block anything?

No. The Promote button is inert. A human clicks Promote on a real site. Nothing blocks automatically, and this page does not change a rule.

What does Hold’s “what would change this” line mean?

It names the gap that would have to close before that rule could say Promote. The line is display only. It does not block, and it does not change the decision.

Is the WordPress store a real shop?

No. Example Goods and example-store.example are example data: an invented WooCommerce store and invented counts. Not a customer. Not live traffic. Login, a media file, cart, and checkout are in those counts. A real store records the same paths on the Launch checklist beside Tuning.

Are bots and fraud protection on in the store example?

No. The store example uses the four groups a new site starts with. Bot management and account-fraud protection are available after setup. They are not on by default, and they are not on in this example. A person still clicks Promote.

See it on your site

Rules start in count. After 24 hours, your dashboard shows what's safe to block — one click.

Start a 14-day trial

Card at Stripe checkout. Cancel before the 14-day trial ends and you won't be charged.

$150/site/mo after the trial

Full example panel · WAF Cybersecurity Advisor docs · What is the WAF Cybersecurity Advisor? · Pricing