Skip to main content

Can Umbraco Cloud allowlist IP addresses for a penetration test or vulnerability scan?

Why Umbraco Cloud's WAF blocks authorised penetration tests and vulnerability scans, why tester IPs can't be allowlisted, how to temporarily turn off WAF for the test window, and where to report findings.

Written by Joana Knobbe

Type: FAQ
​Category: Umbraco Cloud > Security
​Tags: penetration test, pen test, pentest, vulnerability scan, security scan, security audit, PSN, CREST, allowlist, whitelist, IP allowlist, IP whitelist, WAF, web application firewall, scanner blocked, Transport Security, Cloudflare

Product: Umbraco Cloud
​Version: All versions


Can Umbraco Cloud allowlist IP addresses for a penetration test or vulnerability scan?

No. Umbraco Cloud does not have an inbound IP allowlist that lets a penetration tester or security scanner bypass the Web Application Firewall (WAF). If the WAF is blocking an authorised test, you can turn WAF off on the hostname being tested for the duration of the test, then turn it back on.

Why your test is being blocked

WAF is enabled by default on every custom hostname on Umbraco Cloud. It applies Cloudflare's managed rulesets, which look for common attack patterns. Penetration tests and vulnerability scans deliberately send those patterns, so the WAF blocks them the same way it would block a real attack.

There is currently no setting to exempt specific IP addresses from the WAF.

How to let an authorised test through

  1. In the Cloud Portal, open your project and go to Security > Transport Security.

  2. Find the custom hostname the testers will target and turn off WAF for that hostname.

  3. Run the test.

  4. Turn WAF back on as soon as the test is finished. While WAF is off, that hostname has no WAF protection against real attacks either, so keep the window as short as you can.

Agree the test window with your testers in advance so WAF is only off while the test is actually running.

What doesn't work

  • The Public Access IP allowlist. Under Project settings > Public Access you can enable Basic Authentication and add allowed IPs. This controls who can view the site. It is not a way past the WAF, and enabling Basic Authentication on a Live site would block your real visitors.

  • Asking Umbraco Support to allowlist the testers' IPs. We can't add IP exceptions to the WAF for individual projects.

If your site sits behind your own proxy or CDN

If your hostname is routed through your own proxy, such as Azure Front Door or your own Cloudflare account, the Umbraco Cloud WAF cannot be enabled on that hostname. In that setup the firewall in front of your site is yours, and you allowlist the testers' IPs there.

Reporting findings

If the test finds a possible vulnerability in Umbraco CMS or Umbraco Cloud, report it privately to security@umbraco.com. Include a proof of concept rather than raw scan output, and don't post it publicly or as a GitHub issue.

Want self-service IP allowlisting?

There is a feature request for a self-service inbound IP allowlist on Umbraco Cloud. Upvote it here: Self-Service IP Allowlist for Inbound Traffic (WAF Bypass).

Still having issues?

  • If you are chatting with Umboto right now, type "talk to human" and we will connect you with someone who can help.

  • If you are reading this article in the Help Center, contact us by clicking the messenger icon at the bottom right.

Related articles

Recommended documentation


Last updated on November 03, 2026

Did this answer your question?