Restrict Access to Backend Servers from CloudGuard WAF as a Service IPs Only

Risks of Not Restricting Backend Servers to Receive Traffic Only from WAF

Leaving backend servers open to traffic from sources other than Web Application Firewalls (WAF) exposes them to cyber threats. Without WAF protection, attackers can directly target these servers, leading to risks such as denial-of-service (DoS) attacks, ransomware infections, and full application compromises.

Steps to Restrict Backend Servers to Receive Traffic Only from CloudGuard WAF SaaS IPs

To ensure backend servers only receive traffic from CloudGuard WAF as a Service IPs, follow these steps:

1. Identify CloudGuard WAF SaaS IPs: Log in to your Infinity Portal account and navigate to the Profile page to find the list of authorized IP addresses.

2. Update Firewall Rules: Configure your network firewall to allow incoming traffic only from the identified CloudGuard WAF SaaS IPs. This can typically be done through your firewall’s management console.

3. Modify Server Access Control Lists (ACLs): Update the ACLs on your backend servers to permit traffic exclusively from the CloudGuard WAF IP addresses. This ensures that any traffic not routed through the WAF is blocked.

4. Test Configuration: After updating the firewall rules and ACLs, conduct thorough testing to verify that only traffic from the CloudGuard WAF is reaching your backend servers.

5. Monitor and Audit: Continuously monitor network traffic and audit logs to ensure compliance with the new configuration and to detect any unauthorized access attempts.

By implementing these steps, you can significantly enhance the security of your backend servers and protect them from potential cyber threats.