Web Application Firewall (WAF) uses specific back-to-origin CIDR blocks to forward normal traffic back to an origin server. After you add your website to WAF, you must add the back-to-origin CIDR blocks to the IP address whitelist of the security software on the origin server. This topic describes how to allow access from the back-to-origin CIDR blocks of WAF.
Procedure
What to do next
For security purposes, we recommend that you configure access control policies for the origin server to allow inbound traffic only from the back-to-origin CIDR blocks of WAF. This way, attackers cannot bypass WAF to attack the origin server. For more information, see Configure protection for an origin server.
FAQ
What is a back-to-origin CIDR block of WAF?

Why must I add the back-to-origin CIDR blocks of WAF to the IP address whitelist of the security software on the origin server?
After a website is added to WAF, the origin server receives most requests from the back-to-origin CIDR blocks of WAF, and requests are sent at a high rate. In this case, the firewall or security software on the origin server may consider these CIDR blocks as attack IP addresses and block them. If these IP addresses are blocked, WAF cannot receive normal responses from the origin server. Make sure that the back-to-origin CIDR blocks of WAF are added to the IP address whitelist of the security software on the origin server after you add a website to WAF. Otherwise, the website may become slow or inaccessible.