Allow Through WAF
If your application is behind a Web Application Firewall (WAF) or CDN with security features, you may need to allowlist Detectify’s scanner IP addresses to ensure scans can reach your application. Without allowlisting, the WAF may block scanner traffic, resulting in incomplete scan results or false negatives.
Why Allowlisting Is Needed
WAFs are designed to block malicious-looking traffic. Since Detectify’s scanner sends security testing payloads (such as SQL injection and XSS test strings), WAFs will often detect and block this traffic. While this means your WAF is working correctly, it prevents Detectify from testing your actual application for vulnerabilities.
Allowlisting Detectify’s scanner IPs lets traffic pass through the WAF so the scanner can test your application directly.
General Approach
For any WAF or CDN provider:
- Get the current list of Detectify scanner IP addresses from the Scanner IP Addresses page
- Create an allowlist rule in your WAF that permits traffic from these IPs
- Scope the allowlist to only the assets you want to scan, if possible
- Run a test scan to verify traffic is reaching your application
Provider-Specific Instructions
Cloudflare
- Log in to the Cloudflare dashboard
- Navigate to Security > WAF > Tools
- Create a new IP Access Rule
- Enter each Detectify scanner IP address
- Set the action to Allow
- Apply the rule to the zones you want to scan
Alternatively, create a WAF custom rule that skips all WAF rules when the source IP matches Detectify’s scanner IPs.
AWS CloudFront with AWS WAF
- In the AWS WAF console, navigate to your Web ACL
- Create a new IP set containing Detectify’s scanner IP addresses
- Add a rule to your Web ACL that allows traffic from this IP set
- Position the rule before any blocking rules so it takes precedence
Akamai
- In the Akamai control panel, navigate to your security configuration
- Add Detectify’s scanner IPs to the IP allowlist
- Ensure the allowlist applies to the properties you want to scan
Other WAF Providers
For other WAF providers (Imperva, Fastly, Sucuri, Azure WAF, F5, and others), the process is similar:
- Locate the IP allowlist or bypass rule configuration
- Add Detectify’s scanner IP addresses
- Apply the rule to the relevant domains or applications
- Test with a scan to confirm
Security Considerations
- Scope the allowlist narrowly. Only allowlist Detectify IPs for the specific domains or paths you want to scan, not your entire infrastructure.
- Use the correct IP set. Detectify uses different IPs for Surface Monitoring and Application Scanning. See Scanner IP Addresses for the complete list.
- Remove the allowlist when not needed. If you only scan periodically, consider removing the allowlist between scans.
- Monitor for changes. Detectify may add new scanner IPs. Check the Scanner IP Addresses page periodically or subscribe to updates.