CloudGuard WAF
  • Documentation Overview
  • What is CloudGuard WAF?
  • Getting started
    • Prepare key information
    • Log in to the Infinity Portal
    • Protect a Web Application / API
    • Deploy Enforcement Point
      • Gateway/Virtual Machine
        • AWS
          • Store Certificates in AWS
          • Store certificates on Gateway
        • Azure
          • Store Certificates in Azure
          • Store Certificates on Gateway
        • VMware
          • Store Certificates on Gateway
          • Configure networking in VMware Deployments
      • WAF as a Service
        • Certificates Managed by Check Point
        • Bring Your Own Certificate
      • Kubernetes Ingress
        • Kong Application Security
        • Istio Application Security
      • Docker
        • Single Docker
          • Deployment using 'docker' command
            • Store Certificates Locally on Docker
          • Deployment in Azure App Services
        • Dual Docker: NGINX/Kong/Envoy + Security Agent
      • Linux / NGINX / Kong
    • Monitor Events
  • Concepts
    • Gateways & Agents
    • Management & Automation
    • Security Practices
    • Contextual Machine Learning
  • Additional Security Engines
    • Anti-Bot
    • API Protection
      • API Discovery
      • Track API Discovery Learning
      • Enforce API Schema
    • File Security
    • Intrusion Prevention System (IPS)
    • Rate Limit
    • Snort Rules
  • SETUP INSTRUCTIONS
    • Setup Custom Rules and Exceptions
    • Setup Web User Response Pages
    • Setup Log Triggers
    • Setup Report Triggers
    • Setup Notification Triggers
    • Setup Behavior Upon Failure
    • Setup Agent Upgrade Schedule
  • HOW TO
    • Edit Web Application/API Settings
    • Edit Reverse Proxy Advanced Settings for a Web Asset
    • Protect an existing production site with CloudGuard WAF's Gateway
    • View Policy of all your Web Applications/APIs
    • Add Data Loss Prevention (DLP) rules
    • Configure Contextual Machine Learning for Best Accuracy
    • Track Agent Status
    • Track Learning and Move from Learn/Detect to Prevent
    • Rotate profile authentication token
    • Upgrade your Reverse Proxy when a Linux/NGINX agent is installed
    • Use Terraform to Manage CloudGuard WAF
    • Authorize Temporary Access for Check Point Support
    • Restrict Access to Backend Servers from CloudGuard WAF as a Service IPs Only
  • Troubleshooting
    • WAF Gateway / Virtual Machine
      • Azure
        • "Unable to find a tag containing the vault's name in the VMSS" Error
        • How To: Configure Key Vault for a Single Gateway
      • NGINX Error: Upstream Sent Too Big Header While Reading Response Header from Upstream
      • How To: Compare Between the Gateway's Certificate and the Upstream Certificate
    • Linux
      • SELinux: Checking Status and Disabling
    • WAF as a Service
      • Certificate Validation Failed: Adjusting CAA Record
      • How To: Redirect a Root Domain to a Subdomain Protected by WAF SaaS
      • How To: Extend Connection Timeout to Upstream
      • How To: Update Expired Certificates
  • references
    • Agent CLI
    • Management API
    • Event Query Language
    • Writing Snort Signatures
    • Events/Logs Schema
    • CVE-2022-3786 and CVE-2022-3602: OpenSSL X.509 Email Address Buffer Overflows (HIGH)
    • CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974: Ingress NGINX Controller RCE (Critical)
  • Resources
    • GitHub
    • Docker Hub
Powered by GitBook
On this page
  • Target Environment and Deployment Type
  • Data regions and Points of Presence (PoPs)
  • Application or API Configuration Details

Was this helpful?

  1. Getting started

Prepare key information

PreviousWhat is CloudGuard WAF?NextLog in to the Infinity Portal

Last updated 11 days ago

Was this helpful?

It is recommended to prepare the information below before you start deployment, as it will help you in the configuration process.

Target Environment and Deployment Type

Identify where you are going to install CloudGuard WAF and enforce security. The environment and deployment type will define which applies to your project. You can read more about the different enforcement points in the section.

Options are to deploy as:

  • As a Gateway/Virtual Machine in , or VMware.

  • As in specified regions worldwide. Routing through the service is done by configuring the relevant DNS records for the site's domain.

  • in Kubernetes environments - It integrates with the most popular , , and as well as Istio Ingress Controller.

  • Using Docker in one of two main configurations: - a single Docker image containing a managed reverse proxy server and the CloudGuard WAF Security agent, or as ocker - NGINX Reverse Proxy Docker or Kong API Gateway Docker + CloudGuard WAF Security Agent Docker.

  • As an , thus protects any applications and APIs served by NGINX Reverse Proxy.

Data regions and Points of Presence (PoPs)

Data Residency refers to the physical or geographical location where your data is stored.

In the specific case of , there are also separate supported regions for Points of Presence (PoPs). They refer to the physical locations where our Reverse Proxy and WAF agents are deployed, directly influencing your applications' security efficiency and response time.

According to your environment's location (for latency concerns) and, if applicable, regulation concerns, select the data region (and PoP if applicable) from the supported options.

At this time:

  • CloudGuard WAF supported data regions are: Europe, the United States, India, and Australia.

  • CloudGuard WAF SaaS PoPs are supported in: Ireland, Milan, Montreal, Mumbai, North Virginia, Osaka, Singapore, Stockholm, and Sydney.

Application or API Configuration Details

Collect the following information about the web application(s) or API(s) you are going to protect. You will need this to configure the CloudGuard WAF Assets.

  • What is the internal URL or IP address and port of the web application(s), API(s), or internal load balancer in front of them? These are often URLs that will only be accessible from your reverse proxy/security Gateway and not directly exposed to the Internet.

  • What is the external URL and port that you would like to expose to the users? For example - https://www.acme.com or https://acme.com/api.

  • In the common case, you use HTTPS, then depending on the deployment type, you should have access to the SSL certificate and private key (some deployments, like SaaS, do not require that you provide your certificates)

  • What is the best way to distinguish between users of the application or API? This is useful for the CloudGuard WAF machine learning process:

    • Specific header in the HTTP request

    • Specific key in an HTTP cookie

    • Specific key in HTTP JWT

    • IP address in the X-Forwarded-For header

    • IP address of the request

Enforcement Point
Gateways & Agents
AWS
Azure,
a Service
NGINX Ingress Controller
Kong Ingress Controller
Single Docker
Dual D
add-on for NGINX
WAF SaaS