Last Modified: Jul 24, 2020
See more info
Known Affected Versions:
14.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.2, 22.214.171.124, 126.96.36.199, 15.0.0, 15.0.1, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168
Opened: Sep 08, 2019
When defining whitelists in bot defense profiles, when the IP is set to 'Any' and route domains are in use, whitelists are not applied.
Request will be mitigated.
-- Bot Defense profile is enabled. -- Whitelist is configured for IP 'Any' (for URL or GEO), -- Sending a request that matches the whitelist using route domains.
For url whitelist only: Add micro service to the bot defense profile, configure: 1. Add required URL. 2. Specify service type 'Custom Microservice Protection'. 3. Set the 'Mitigation and Verification' setting as required (relevant for logging only). 4. In 'Automated Threat Detection', set 'Mitigation Action' to 'None'. 5. Set the microservice 'Enforcement Mode' to 'Transparent'. This causes the associated URL to never be blocked (but no 'whitelist' will be seen in reporting).
Enabling IP 'Any' on route domains now works as expected.