Configure your server to allow XBOW requests
Configure firewall access and infrastructure settings to enable XBOW testing.
Before you start: Review Protecting targets during XBOW testing to understand the trade-offs between different access methods and rate limiting approaches.
Configure firewall access
Choose the access method that best fits your security requirements and configure your WAF accordingly. See Allowing access through your firewall for guidance on choosing the right method.
Option 1: Configure a custom bypass header (recommended)
A bypass header is a custom header that XBOW includes in all test requests. Configure your WAF to allow requests with this header.
- On the “Target configuration” page, expand the “Custom headers” section.
- Click “Add header” to display a pair of “Name” and “Value” fields with an associated
icon. - In the “Name” field, enter your header name (for example,
X-XBOW-Test). - In the “Value” field, enter a secure, unique value (for example, a UUID or random string).
- Configure your WAF to allow requests containing this header.
Tip: Using a bypass header makes it easy for your security team to detect and distinguish XBOW’s traffic from other traffic in logs and monitoring tools.
Option 2: Add XBOW IP addresses to your WAF allowlist
- Review the XBOW IP address ranges in Access requirements.
- Configure your WAF to allow traffic from these IP addresses to your test target.
- Verify that the allowlist rules are active before starting your assessment.
Option 3: Temporarily disable your WAF (test environments)
Important: Only use this option for isolated test environments with no exposure to production or untrusted networks.
- Disable your WAF for the target under test.
- Schedule re-enabling the WAF immediately after testing completes.
- Ensure your security team is aware of the temporary change.
Configure CAPTCHA handling
- Disable CAPTCHA for the test account you provide to XBOW.
- Document this change for your security team and plan to re-enable CAPTCHA after testing completes.
Next steps
- Lightspeed users: Fix configuration check problems
- Enterprise users: Set test execution options