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

Was this helpful?

  1. Getting started
  2. Deploy Enforcement Point
  3. Docker

Dual Docker: NGINX/Kong/Envoy + Security Agent

PreviousDeployment in Azure App ServicesNextLinux / NGINX / Kong

Last updated 2 months ago

Was this helpful?

In this option you will deploy two docker images:

  • NGINX/Kong/Envoy - managed locally by you

  • CloudGuard WAF Agent - centrally managed via WebUI or API

The benefit of this mode is that you can upgrade each docker separately.

Step 1: Pull agent container image

As part of your CI, use the registry to pull the Nano-Agent image.

Step 2: Obtain the registration token

Make sure you obtain the <token> from the page, Authentication section. you will need it during agent deployment.

Step 3: Run the agent

Run the agent with this command:

docker run -d --name=agent-container --ipc=host -v=<path to persistent location for agent config>:/etc/cp/conf -v=<path to persistent location for agent data files>:/etc/cp/data -v=<path to persistent location for agent debugs and logs>:/var/log/nano_agent –e https_proxy=<user:password@Proxy address:port> -it <agent-image> /cp-nano-agent --token <token>

–e https_proxy parameter is optional and used only in case the outbound traffic reaches the internet through a proxy server.

Step 4: Replace the NGINX container with the Check Point NGINX container

Replace the NGINX container using the following registry to pull the image for this deployment:

As part of creating your reverse proxy for this environment, make sure that the reverse proxy is deployed with the correct downstream and upstream routing.

Step 5: Modify the run command

Change your existing NGINX/Kong docker run command and add the --ipc=host parameter.

If you are installing a reverse proxy for the first time and have no prior knowledge of deployment methods, an example of simple deployment instructions using NGINX can be found in .

Step 6: Deploy the two containers

Deploy the two containers.

To make sure that it is running, run: docker ps.

Step 7: Configure SSL certificates (optional if the servers do not use HTTPS)

To configure SSL certificates in NGINX follow these guides:

Step 8: Verify installation

Following the steps above, the agent will install and connect automatically. CloudGuard WAF web portal should display a successful connection message:

Step 1: Pull agent container image

Step 2: Obtain the registration token

Step 3: Run the agent

Run the agent with this command:

docker run -d --name=agent-container --ipc=host -v=<path to persistent location for agent config>:/etc/cp/conf -v=<path to persistent location for agent data files>:/etc/cp/data -v=<path to persistent location for agent debugs and logs>:/var/log/nano_agent –e https_proxy=<user:password@Proxy address:port> -it <agent-image> /cp-nano-agent --token <token>

–e https_proxy parameter is optional and used only in case the outbound traffic reaches the internet through a proxy server.

Step 4: Replace the Kong container with the Check Point Kong container

As part of creating your reverse proxy for this environment, make sure that the reverse proxy is deployed with the correct downstream and upstream routing.

Step 5: Modify the run command

Change your existing NGINX/Kong docker run command and add the --ipc=host parameter.

Step 6: Deploy the two containers

Deploy the two containers.

To make sure that it is running, run: docker ps.

Step 7: Configure SSL certificates (optional if the servers do not use HTTPS)

Step 8: Verify installation

Following the steps above, the agent will install and connect automatically. CloudGuard WAF web portal should display a successful connection message:

Step 1: Pull agent container image

Step 2: Obtain the registration token

Step 3: Run the agent

Run the agent with this command:

docker run -d --name=agent-container --ipc=host -v=<path to persistent location for agent config>:/etc/cp/conf -v=<path to persistent location for agent data files>:/etc/cp/data -v=<path to persistent location for agent debugs and logs>:/var/log/nano_agent –e https_proxy=<user:password@Proxy address:port> -it <agent-image> /cp-nano-agent --token <token>

–e https_proxy parameter is optional and used only in case the outbound traffic reaches the internet through a proxy server.

Step 4: Replace the Envoy container with the Check Point Envoy container

As part of creating your reverse proxy for this environment, make sure that the reverse proxy is deployed with the correct downstream and upstream routing.

Step 5: Load the CloudGuard WAF attachment in the proxy configuration

When installing Envoy on Docker: As an envoy.yaml configuration file is not included in the Envoy container make sure to have the above configuration added yourself to that file!

In the Envoy configuration file, which is typically called envoy.yaml make sure to have the CloudGuard WAF attachment loaded as a filter for HTTP traffic.

The CloudGuard WAF attachment is usually located here: /usr/lib/libenvoy_attachment.so

Step 6: Deploy the two containers

Deploy the two containers.

To make sure that it is running, run: docker ps.

Step 7: Configure SSL certificates (optional if the servers do not use HTTPS)

Step 8: Verify installation

Following the steps above, the agent will install and connect automatically. CloudGuard WAF web portal should display a successful connection message:

As part of your CI, use the registry to pull the Nano-Agent image.

Make sure you obtain the <token> from the page, Authentication section. you will need it during agent deployment.

Replace the NGINX container using the following registry to pull the image for this deployment:

If you are installing a reverse proxy for the first time and have no prior knowledge of deployment methods, an example of simple deployment instructions using NGINX can be found in .

To configure SSL certificates in Kong follow the guide in the following .

As part of your CI, use the registry to pull the Nano-Agent image.

Make sure you obtain the <token> from the page, Authentication section. you will need it during agent deployment.

Replace the NGINX container using the following registry to pull the image for this deployment:

To configure SSL certificates in Envoy follow the guide in the following .

NGINX
NGINX PLUS
checkpoint/infinity-next-nano-agent
Enforcement Profile
checkpoint/infinity-next-kong
the official NGINX docker hub repository
link
checkpoint/infinity-next-nano-agent
Enforcement Profile
 checkpoint/cloudguard-waf-envoy
link
checkpoint/infinity-next-nano-agent
Enforcement Profile
checkpoint/infinity-next-nginx
the official NGINX docker hub repository