WAF as a Service
Last updated
Last updated
CloudGuard WAF SaaS provides all of CloudGuard WAF's security capabilities, with the ease of avoiding the need for a complex deployment. In addition, it provides another layer of security with advanced DDoS protection for your protected assets.
DNS configuration of your domain is changed to route your site's traffic through WAF SaaS. WAF SaaS protects the site by inspecting the traffic, and routes it to the internal server. The SaaS service has a Reverse proxy function with CloudGuard WAF's security.
WAF SaaS does not support accepting traffic to a root domain.
i.e. the asset's URL can be defined to be "www.myapp.com" or "api.myapp.com", but it cannot be just "myapp.com"
For specific cases we can provide a manual solution - Contact your local Check Point team.
In today's digital landscape, data security and privacy are paramount. We understand the critical importance of protecting sensitive information as it traverses the internet. That's why we are proud to offer comprehensive end-to-end (E2E) encryption across our services.
Our robust encryption ensures that your data remains secure and private, from the moment it leaves the application client to the point it reaches you, our valued customer. The journey of your data begins when it is transmitted from the application client. When the client's encrypted data reaches our WAF SaaS exposed entry point, it is decrypted to allow WAF Security. After the WAF had performed its security inspection it sends the data to the application, again in encrypted communication.
When creating an account to manage your security, a data region was selected. Data Residency refers to the physical or geographical location where your data is stored and it also determines the region of Infinity Portal where your configuration and logs can be viewed and edited.
In WAF SaaS there are also Points of Presence (PoPs). PoPs are crucial for the performance and security of your web applications. They refer to the physical locations where our WAF agents are deployed, directly influencing your applications' security efficiency and response time.
CloudGuard WAF PoPs can be deployed in any AWS location worldwide, offering unparalleled flexibility. For optimal performance, it is recommended to deploy PoPs as close to your application server as possible. This proximity reduces latency, ensuring faster and more reliable protection against threats. Please note that we are using network assertion therefore the application users will have an accelerated connection to the PoP.
With CloudGuard WAF, you have the flexibility to create or delete PoPs as your needs evolve. Assets can be seamlessly moved from one PoP to another, allowing for a dynamic and adaptable security posture.
Ownership of the DNS configuration for the protected domain.
Accessibility - You must be able to configure your internal web server to be accessible from the IP addresses of WAF SaaS (whitelist WAF IPs). If you just added a new internal address it can be exposed publicly for the deployment stage purposes, but you must reduce its accessibility in the appropriate installation step after WAF SaaS has been configured. Following that step it should not be accessible publicly.
It is important to note the following:
Existing CloudFront Configuration for your site - If you are already using AWS with an existing CloudFront configuration for your site, you will need to delete CloudFront configuration before connecting to WAF SaaS as AWS does not allow defining the same URL in separate CloudFront configurations.
Requiring a dedicated private IP address for your web site - In some cases, usually due to regulation purposes, it is required for the website's domain to be translated to a dedicated private IP address that follows some conditions/regulations.
WAF SaaS currently does not support private IP address usage.
For specific cases we can provide a manual solution - Contact your local Check Point team.
It is possible to define a second WAF SaaS profile in a different region by browsing to Policy->Profiles and creating a new WAF SaaS profile, then connecting an existing Web asset to this profile in addition to an existing WAF SaaS profile.
After creating the second profile, browse to Policy->Assets and edit your web asset. Under General->Basic->Profiles you can add additional profiles that will protect this asset. Select your secondary WAF SaaS profile.
At this point only 2 WAF SaaS profiles from different PoPs are supported per Web asset. Usage of each PoP is done in an active-passive mode where only one is used in any given moment.
