Advanced threat prevention security for AWS and hybrid cloud environments, with Threat Extraction and Threat Emulation, and with GWLB (starting with R81.20)
**Please note: To ensure optimal operations, Check Point recommends a 4 vCores machine size. This provides balanced efficiency and smooth performance, which most customers find ideal for their needs.
Check Point Check Point Cloud Firewall is a cloud-native security gateway that delivers industry-leading threat prevention and multi-layered network security for workloads migrated to or deployed in AWS environments.
Comprehensive Cloud Network Security: Check Point Cloud Firewall for AWS protects cloud assets with a full suite of advanced security capabilities, including: firewall, Data Loss Prevention (DLP), Intrusion Prevention System (IPS), application control, IPsec VPN, URL filtering, antivirus, anti-bot, threat extraction, and threat emulations. These features enable proactive defense against known and unknown threats, ensuring robust protection for cloud workloads.
Industry-Leading Threat Prevention: Check Point Cloud Firewall for AWS provides advanced threat prevention to secure AWS environments from sophisticated threats, unapproved access, and application-layer Denial of Service (DoS) attacks with industry-leading catch rates (Miercom 2025 and Cyberratings 2025).
Full Control of Network Traffic: Check Point Cloud Firewall for AWS ensures secure, encrypted data flows between your on-premises network and your AWS VPCs. It inspects traffic entering and exiting private subnets in the VPC ("North-South") as well as between VPCs ("East-West").
Unified Security Management: Extend on-premises security policies into the AWS cloud with unified, centralized management via Check Point Security Management Server. Manage policies, logs, and reports consistently across AWS, hybrid, and on-premises environments from a single pane of glass. This listing includes the gateway only. For management, use Check Point Smart-1 Cloud: https://www.checkpoint.com/quantum/unified-cyber-security-platform/smart-1-cloud/
Automated, Scalable Cloud Security: Integrates with infrastructure-as-code tools like Terraform and Ansible for policy automation and cloud-native scaling. CloudGuard dynamically adapts security policies based on real-time cloud metadata and changes. Supports AWS Transit Gateway, auto-scaling, high availability, and multi-AZ redundancy.
Seamless AWS Integration: Check Point Cloud Firewall integrates with a broad range of AWS services, including Gateway Load Balancer, AWS Security Hub, VPC Ingress Routing, AWS Traffic Mirroring, AWS Transit Gateway, AWS Outposts, and Amazon Macie.
This Check Point Cloud Firewall gateway will be deployed as a single gateway, as a high availability cluster, or as an Auto Scaling group via Check Point CloudFormation templates (sk111013) or via automation tools such as Ansible, Terraform, etc. This PAYG-distributed security gateway is managed from a central Security Management Server which provides consistent security policy management, enforcement, and reporting within a single pane of glass. The Security Management Server is not included in this offering. To manage Check Point Cloud Firewall Gateway, it is recommended using Check Point Smart-1 Cloud (https://www.checkpoint.com/quantum/unified-cyber-security-platform/smart-1-cloud/ ).
Highlights
Advanced Protection with Security Features: firewall, DLP, IPS, applicationcControl, IPsec VPN, URL Filtering, antivirus, anti-bot, threat extraction, and threat emulation. Includes Security Management Server.
Industry-Leading Threat Prevention: Cutting-edge threat prevention with industry-leading catch rate of malware, ransomware and other types of attacks (per Miercom and Cyberratings, 2025).
Unified Security Management: Provides consistent visibility, policy management, logging, reporting and control across hybrid-clouds and on-premises from a single pane of glass.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Try this product free for 30 days according to the free trial terms set by the vendor. Usage-based pricing is in effect for usage beyond the free trial terms. Your free trial gets automatically converted to a paid subscription when the trial ends, but may be canceled any time before that.
Check Point Cloud Firewall with Threat Prevention and SandBlast
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
You pay by the hour for each running instance, with no upfront commitment. The price you pay depends on the Amazon EC2 instance type you choose to run the virtual security gateway. Options span compute-optimized (c-family), general-purpose (m-family), and memory-optimized (r-family) instances across several hardware generations, including bare-metal sizes. Within each family, larger sizes cost more per hour because they provide more processing and memory capacity. You select the instance type that matches your throughput and traffic needs, and billing scales with the size and number of instances you deploy.
Top-of-mind questions for buyers
What exactly am I paying for with each hourly instance type?
You pay for the software license running on one Amazon EC2 instance of the type you select. The virtual security gateway runs on that instance, and the hourly rate reflects the instance size. More instances or larger sizes raise your total hourly cost.
Am I charged when an instance is stopped or powered off?
Hourly software charges apply only while an instance runs. A stopped or powered-off instance stops accruing software charges. Underlying AWS storage or other resource fees may still apply separately, but the firewall license meters running hours only.
How do I pick the right instance type for my traffic?
Choose the instance type that matches your throughput and traffic needs. Compute-optimized instances suit heavy processing, while memory-optimized instances suit traffic needing more memory. The gateway delivers threat prevention across public, private, and hybrid cloud deployments regardless of the size you select.
www.checkpoint.com
Helpful?
Vendor refund policy
Terminate the instance at any given time to stop incurring charges.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Once the instance is running, connect to it using SSH, set an admin password using: 'set user admin password' followed by 'save config'. Then connect to https://[instance] using Internet Explorer (IE) to finalize the configuration.
Notes:
SSH password authentication is disabled in /etc/ssh/sshd_config
For information regarding Firefox and Chrome refer to sk121373.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Includes firewall, Data Loss Prevention (DLP), Intrusion Prevention System (IPS), application control, IPsec VPN, URL filtering, antivirus, anti-bot, threat extraction, and threat emulation capabilities
Advanced Threat Detection and Analysis
Incorporates Threat Extraction and Threat Emulation technologies for proactive defense against known and unknown threats
Traffic Inspection and Control
Inspects and controls encrypted data flows between on-premises networks and AWS VPCs, supporting both North-South (VPC ingress/egress) and East-West (inter-VPC) traffic
Cloud Infrastructure Integration
Integrates with infrastructure-as-code tools including Terraform and Ansible, AWS Transit Gateway, auto-scaling, Gateway Load Balancer, AWS Security Hub, VPC Ingress Routing, AWS Traffic Mirroring, and AWS Outposts
Centralized Security Policy Management
Provides unified, centralized management and consistent policy enforcement across AWS, hybrid, and on-premises environments through a single management interface
Advanced Threat Prevention
Safeguards network from known and zero-day threats including exploits, malware, spyware, and command and control attacks using researcher-grade signatures and machine learning inspection engine.
Advanced URL Filtering
Defends against phishing, ransomware, and web-based attacks using inline machine learning-based web security engine with real-time detection of previously unseen threats and dynamic policy controls.
File-Based Threat Detection
Identifies file-based threats through inline static and dynamic analysis in the cloud with proprietary hypervisor technology for detection of sandbox-resistant malware.
DNS Security
Detects and prevents sophisticated DNS-layer network attacks and data exfiltration attempts.
Application Layer Visibility and Control
Provides complete application layer-7 visibility and control of traffic with dynamic policy management based on AWS tags, Application IDs, User IDs, geographies, or zones.
Intrusion Detection and Prevention
Intrusion detection and prevention (IPS) capabilities to identify and block malicious network traffic and attacks.
Anti-Virus Protection
Cloud-based anti-virus capabilities that detect and block spyware, adware, viruses, keyloggers, and malware over POP3, HTTP, SMTP, and FTP protocols.
VPN and Encryption
IPsec and full mesh VPN termination services for secure connectivity across on-premises data centers, campuses, branches, and geographically dispersed VPCs.
Application Visibility and Control
AppSecure application visibility and control through L4-L7security services for advanced threat protection and application-level inspection.
Cloud Service Integration
Native integration with AWS services including Elastic Load Balancer, Auto-Scaling Groups, CloudWatch, Security Hub, Key Management Service, Gateway Load Balancer, and Elastic Network Adapter support.
Reliable Cloud Network Security with Strong Threat Protection
Reviewed on Nov 09, 2026
Review provided by G2
What do you like best about the product?
What I like most about Check Point Cloud Firewall is its strong security capabilities and the centralized visibility it gives me across cloud environments. It helps protect workloads with advanced threat prevention, network traffic inspection, and clear security policy management. I also appreciate the added control it provides over cloud network access, and how it helps me spot potential threats early—before they can affect production workloads.
What do you dislike about the product?
The initial setup and configuration can feel a bit complex, especially when you’re managing multiple cloud environments alongside network policies. Troubleshooting and updating policies isn’t always as straightforward as it could be, and the learning curve is fairly steep for new users. I’d also like to see simpler, more intuitive dashboards and pricing that’s more transparent.
What problems is the product solving and how is that benefiting you?
Check Point Cloud Firewall helps us secure our cloud infrastructure by controlling network traffic, monitoring inbound and outbound connections, and protecting workloads from unauthorized access and potential threats. It also provides clearer visibility into network activity, supports consistent enforcement of security policies, and lowers the risk of accidentally exposing critical services. Overall, it makes cloud security management easier and gives our team more confidence when deploying and operating production workloads.
Fernando Ortega
Automated AI defenses have reduced war room time and improve incident response for web attacks
Reviewed on Oct 13, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for Check Point Cloud Firewall (formerly CloudGuard Network Security) is to protect our four sites and our tool that is published to the internet, which is named Pago Facil.
Check Point Cloud Firewall (formerly CloudGuard Network Security) improves most of our incident response because the automated anti-bot and anti-DDoS work very well. In this way, I don't need as many interactions with the tool because using artificial intelligence, it defends a significant portion of the attackers due to the technique switching of the tool and its strong response to attacks.
I integrate Check Point Cloud Firewall (formerly CloudGuard Network Security) only with the logs and I do this integration through the SIEM.
How has it helped my organization?
Check Point Cloud Firewall (formerly CloudGuard Network Security) positively impacts my organization by making our company safer.
I haven't noticed fewer incidents; however, I do have fewer incidents to respond to by my team. The tool itself answers attacks very well, which reduces our time in the war rooms, in the places where direct team interaction would be necessary.
Check Point Cloud Firewall (formerly CloudGuard Network Security) helps me reduce organizational risk significantly because the response time of the tool is very strong and very fast, improving our incident response for the majority of cases.
Check Point Cloud Firewall (formerly CloudGuard Network Security) has positively impacted my confidence in secure cloud deployments and migrations because we utilize artificial intelligence with very fast detection of technique switching from attackers, which strengthens our environment.
What is most valuable?
In my experience, the best features Check Point Cloud Firewall (formerly CloudGuard Network Security) offers are WAF, or Web Application Firewall, which acts as a front end of the tools, as well as anti-distributed denial of service, anti-bot, and the auto features.
The auto features help my team and our workflow significantly because they greatly reduce interactions with incidents by filtering effectively and enhancing our security.
The advanced technique switching detection of the anti-bot and anti-malware works very well, especially when a technique starts with one approach of MITRE and changes mid-process.
Regarding Check Point Cloud Firewall (formerly CloudGuard Network Security)'s AI capabilities, I think its governance is very serious and strong because all the data collected by the WAF is useful for other companies.
I find Check Point Cloud Firewall (formerly CloudGuard Network Security)'s AI capabilities very reliable because all the data used to generate responses is assertive and works very well; it is running very well.
Check Point Cloud Firewall (formerly CloudGuard Network Security) provides unified security management across hybrid clouds as well as on-premises, and this unified security management affects our security operations by ensuring all configurations and management work through the same portal we use for other tools, which is Infinity Portal, and it works very well.
What needs improvement?
I don't see improvements needed for Check Point Cloud Firewall (formerly CloudGuard Network Security), as it helps me greatly and I have a great time using the tool. I don't have anything in my mind right now regarding small improvements or future additions. There are no improvements needed for Check Point Cloud Firewall (formerly CloudGuard Network Security) that I haven't mentioned.
For how long have I used the solution?
I have been using Check Point Cloud Firewall (formerly CloudGuard Network Security) for two years.
What do I think about the stability of the solution?
Check Point Cloud Firewall (formerly CloudGuard Network Security) is very stable.
What do I think about the scalability of the solution?
Check Point Cloud Firewall (formerly CloudGuard Network Security)'s scalability is excellent because the tenants are distributed across many data centers, ensuring great availability of the solution.
How are customer service and support?
Customer support is the best part of the branding; we have access to great engineers who always solve the issues we face. I rate customer support a 10.
Which solution did I use previously and why did I switch?
I didn't have another solution in the past.
What was our ROI?
I have seen a return on investment as I have reduced the number of employees needed.
What's my experience with pricing, setup cost, and licensing?
I purchased Check Point Cloud Firewall (formerly CloudGuard Network Security) through the Azure Marketplace. I have a great experience with pricing, setup costs, and licensing.
Which other solutions did I evaluate?
I have used other solutions that compete with Check Point Cloud Firewall (formerly CloudGuard Network Security), such as Harmony Mail, SASE for remote access, and the CloudGuard WAF tool; these tools synergize with the premises firewall and cloud firewalls we have. Before choosing Check Point Cloud Firewall (formerly CloudGuard Network Security), I evaluated options like Cloudflare and Akamai.
What other advice do I have?
I rate Check Point Cloud Firewall (formerly CloudGuard Network Security) a 10. I choose 10 because the response it delivers is exactly what I need; it's a great tool that reduces war room times and provides self-defense for our environment, preventing the majority of attacks while minimizing my direct interactions with incident response.
We utilize Check Point Cloud Firewall (formerly CloudGuard Network Security) in a private cloud, on-premises, and in a hybrid cloud configuration. For our hybrid or private cloud deployments, we use Azure.
If you want to really prevent AI attacks, I recommend the Check Point Cloud Firewall (formerly CloudGuard Network Security) solution.
reviewer779900
Centralized cloud policies have improved visibility and simplified network troubleshooting
Reviewed on Oct 02, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Check Point Cloud Firewall (formerly CloudGuard Network Security) is securing cloud workloads by controlling and inspecting network traffic between application servers and the internet. Day-to-day, I use it to enforce access rules between production servers and external services while monitoring and blocking suspicious traffic.
The process for enforcing access rules or monitoring traffic with Check Point Cloud Firewall (formerly CloudGuard Network Security) mainly relies on centralized security policy management to define and update access rules, followed by traffic logs and monitoring to verify that traffic is being allowed or blocked. For troubleshooting, I typically review the logs to identify the source, destination, port, and the action before adjusting the policy if required.
Check Point Cloud Firewall (formerly CloudGuard Network Security) gives consistent security controls across our cloud environment rather than managing firewall rules separately on individual workloads. It is also useful during troubleshooting because the centralized logging makes it easier to understand and trace network traffic.
Check Point Cloud Firewall (formerly CloudGuard Network Security) is deployed in our organization primarily in a public cloud environment, protecting workloads and controlling traffic between cloud resources and external networks. It is integrated into our cloud network architecture rather than being deployed as a traditional on-premises firewall.
We primarily use AWS for our public cloud environment and deployment of Check Point Cloud Firewall (formerly CloudGuard Network Security). It secures our cloud workloads and controls traffic between different network segments and external services.
We utilize Check Point Cloud Firewall (formerly CloudGuard Network Security) alongside Check Point Security Management and threat prevention capabilities. The integration gives us a centralized view of policies and security events, while Check Point Cloud Firewall (formerly CloudGuard Network Security) applies those controls to our cloud workloads and network traffic.
How has it helped my organization?
Check Point Cloud Firewall (formerly CloudGuard Network Security) has positively impacted my organization by mainly improving security consistency and visibility across our cloud environments. We have also reduced the time spent troubleshooting network access issues because the centralized policies and logs make it easier to identify and resolve blocked or unexpected traffic.
I estimate we save around 20 to 30 percent of the time on network troubleshooting since we started using Check Point Cloud Firewall (formerly CloudGuard Network Security), mainly because the centralized logs make it quicker to identify blocked traffic and policy issues. We have also seen faster policy changes and less manual effort when managing security rules across environments.
Check Point Cloud Firewall (formerly CloudGuard Network Security) provides us with unified security management across hybrid clouds and on-premises environments where applicable. It helps our security team apply consistent policies and review events from a common management layer, which reduces duplicated administration and makes troubleshooting easier.
Check Point Cloud Firewall (formerly CloudGuard Network Security) has meaningfully reduced our cloud security risk mainly through centralized policies, traffic inspection, and threat prevention controls. I cannot put an exact percentage on risk reduction, but we have improved visibility and reduced the chance of inconsistent or overly permissive network access.
Check Point Cloud Firewall (formerly CloudGuard Network Security) has increased our confidence in secure cloud deployments because we can apply consistent security policies and threat prevention controls as workloads move into the cloud. Having centralized visibility also makes it easier to validate that traffic is properly controlled before and after a migration.
What is most valuable?
The best features Check Point Cloud Firewall (formerly CloudGuard Network Security) offers in my experience are centralized policy management, detailed traffic logging, and built-in threat prevention. I also appreciate having visibility into cloud traffic in one place, which makes troubleshooting access issues and investigating suspicious connections much easier.
Out of the features of Check Point Cloud Firewall (formerly CloudGuard Network Security), I find myself using centralized policy management the most because most of our day-to-day work involves creating, reviewing, and updating access rules. It stands out because changes can be managed consistently across multiple cloud environments instead of handling each firewall separately.
One feature of Check Point Cloud Firewall (formerly CloudGuard Network Security) that I think people may overlook is the quality of the traffic visibility and logging. It is very useful when troubleshooting connectivity issues because I can quickly see which traffic was allowed or blocked and use that information to fine-tune the security policy.
What needs improvement?
The main improvement area for me regarding Check Point Cloud Firewall (formerly CloudGuard Network Security) is ease of configuration and day-to-day administration. Some policies and cloud-specific settings can take time to understand, and troubleshooting occasionally requires going through multiple screens or logs. A more streamlined UI and simpler workflows would help.
I would appreciate simpler policy troubleshooting and better visibility of rule dependencies in Check Point Cloud Firewall (formerly CloudGuard Network Security). It would be helpful to have a clear explanation of why the traffic was blocked and what policy or configuration caused it, especially in larger cloud environments.
I would appreciate better automation around policy recommendations and cleanup of unused rules with clear explanations for each recommendation in Check Point Cloud Firewall (formerly CloudGuard Network Security). It would also be useful to have simpler dashboards for quickly understanding the overall security posture across multiple cloud environments.
For how long have I used the solution?
I have been using Check Point Cloud Firewall (formerly CloudGuard Network Security) for a little over a year, mainly for securing cloud workloads and controlling inbound and outbound traffic. Over that time, I have also worked with its centralized policy management and threat prevention capabilities.
What do I think about the stability of the solution?
Check Point Cloud Firewall (formerly CloudGuard Network Security) has been stable in production. We have been using it for over a year without major stability issues, and the day-to-day policy management and traffic inspection have been reliable.
What do I think about the scalability of the solution?
We have found Check Point Cloud Firewall (formerly CloudGuard Network Security) scales well as the cloud environment grows, especially when adding more workloads and traffic. The centralized management makes it easier to maintain consistent policies, although larger environments require some additional planning around configuration and sizing.
How are customer service and support?
The customer support for Check Point Cloud Firewall (formerly CloudGuard Network Security) has been generally good in my experience. For issues that required deeper troubleshooting, the support team was responsive and helped us work through configuration and policy-related problems.
I would rate the customer support for Check Point Cloud Firewall (formerly CloudGuard Network Security) around eight out of ten. They have generally been responsive and helpful, especially for configuration and troubleshooting issues.
Which solution did I use previously and why did I switch?
Before Check Point Cloud Firewall (formerly CloudGuard Network Security), we mainly relied on the native AWS security controls. We moved to Check Point Cloud Firewall (formerly CloudGuard Network Security) because we wanted more centralized policy management, consistent security controls, and better visibility across our cloud environment.
What was our ROI?
We have seen a return on investment with Check Point Cloud Firewall (formerly CloudGuard Network Security) mainly through time savings and reduced manual troubleshooting effort rather than direct headcount reduction. Based on our experience, we have saved roughly 20 to 30 percent of the time spent on network troubleshooting and policy administration, which adds up significantly over the year.
What's my experience with pricing, setup cost, and licensing?
The pricing for Check Point Cloud Firewall (formerly CloudGuard Network Security) is reasonable for the level of security and centralized management, but licensing can be a bit complex depending on the cloud deployment and required features. Our initial setup required some planning, especially around sizing and licensing, but after that, the ongoing management was fairly straightforward.
Which other solutions did I evaluate?
I have evaluated alternatives such as native AWS security controls. Check Point Cloud Firewall (formerly CloudGuard Network Security) is fairly powerful and flexible, but I found the initial setup and policy configuration somewhat more complex than some alternatives, especially for teams new to Check Point.
Before choosing Check Point Cloud Firewall (formerly CloudGuard Network Security), we evaluated native AWS controls, and we compared them mainly on centralized management, policy control, traffic visibility, threat prevention, and how well they would fit into our existing cloud environment.
What other advice do I have?
Check Point Cloud Firewall (formerly CloudGuard Network Security) provides strong security, centralized policy management, and good visibility while there is still room to improve the overall administration experience and simplify troubleshooting. I would rate Check Point Cloud Firewall (formerly CloudGuard Network Security) eight out of ten because the security capabilities and centralized management work well for our use case. What holds it back is mainly the learning curve and administration complexity. Some configurations and troubleshooting workflows could be more intuitive.
Regarding Check Point Cloud Firewall (formerly CloudGuard Network Security)'s AI capabilities, I would say that its governance and security are reasonably well-governed, with the main strength being existing security controls and centralized visibility. That said, I would still appreciate more transparency around how AI-driven decisions are made and more granular controls for governing those capabilities.
Regarding Check Point Cloud Firewall (formerly CloudGuard Network Security)'s AI capabilities, the accuracy and reliability of output I have used have generally been consistent and useful for security monitoring and analysis, but I do not rely on them blindly for critical policy decisions. I usually validate AI-generated insights against the actual traffic logs and security events before taking action.
We have purchased Check Point Cloud Firewall (formerly CloudGuard Network Security) through AWS Marketplace. It made the procurement process relatively straightforward and fit well with our existing AWS billing and cloud deployment model.
I would recommend Check Point Cloud Firewall (formerly CloudGuard Network Security) for organizations that need centralized security management and strong visibility across cloud environments. I would suggest planning the initial configuration carefully and giving the team some time to learn the platform, especially the policy management side. I have assigned this review a rating of eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Yabaluru Deepthi Naga Ramya Sravani
Cloud security has improved and supports confident migrations with integrated threat prevention
Reviewed on Sep 21, 2026
Review provided by PeerSpot
What is our primary use case?
Check Point Cloud Firewall (formerly CloudGuard Network Security) is used for access control to allow or block traffic based upon the source and destination. Network segmentations and logging and monitoring are implemented to monitor connections, block traffic, and manage security policies through creating and managing firewall rules via Check Point's management platform.
Check Point Cloud Firewall (formerly CloudGuard Network Security) can send events to SIEM platforms such as Splunk for centralized monitoring and incident investigation. Threat intelligence is utilized to identify malicious IPs as a criterion for the platform. Additionally, Check Point Cloud Firewall (formerly CloudGuard Network Security) provides security solutions for cloud environments such as AWS and Azure, which deliver firewalling and threat prevention for cloud workloads.
What is most valuable?
The most valuable aspects of Check Point Cloud Firewall (formerly CloudGuard Network Security) are the VPN secure site-to-site and remote access connections along with threat prevention. Malicious traffic can be detected using security features such as IPS, anti-bot, antivirus, and URL filtering.
Check Point Cloud Firewall (formerly CloudGuard Network Security) has positively impacted confidence in secure cloud deployment and migration. The migration was completed successfully and proved to be very feasible.
What needs improvement?
After working with Check Point Cloud Firewall (formerly CloudGuard Network Security) for three years, most areas including firewall rules, network segmentation, and threat prevention are solid. However, vulnerability and patch management could be improved by providing the best version of vulnerabilities and exact track numbers, which would allow for easier detection of issues with the vulnerability numbers affected in the environment.
For how long have I used the solution?
Check Point Cloud Firewall (formerly CloudGuard Network Security) has been in use for three years.
What do I think about the stability of the solution?
Check Point Cloud Firewall (formerly CloudGuard Network Security) is stable for the most part and is rated as good. The stability is rated around seven to eight on a scale of one to ten.
What do I think about the scalability of the solution?
Scalability is rated as seven on a scale of one to ten.
How are customer service and support?
Technical support for Check Point Cloud Firewall (formerly CloudGuard Network Security) is rated an eight on a scale of one to ten.
How was the initial setup?
The deployment of Check Point Cloud Firewall (formerly CloudGuard Network Security) is straightforward and was easy to implement.
What was our ROI?
The return on investment observed with Check Point Cloud Firewall (formerly CloudGuard Network Security) is approximately fifty percent.
What other advice do I have?
Many companies are opting for Check Point Cloud Firewall (formerly CloudGuard Network Security) as it is cost-effective and integrated with the cloud at affordable prices according to each company's environment. The licenses and overall offerings are favorable, making it a preferable choice.
Check Point Cloud Firewall (formerly CloudGuard Network Security) is definitely recommended because it includes threat detection, the latest technologies integrated with the cloud, and is affordable according to most companies' requirements. The number of users using Check Point Cloud Firewall (formerly CloudGuard Network Security) is approximately ten thousand users. The overall review rating for this product is eight on a scale of one to ten.
Prasanth Penuboina
Centralized cloud security has streamlined multi-account protection but still needs better dashboards
Reviewed on Aug 23, 2026
Review from a verified AWS customer
What is our primary use case?
I have been using Check Point Cloud Firewall (formerly CloudGuard Network Security) for the past one and a half years.
My focus is on cloud-related aspects like AWS cloud and Azure cloud. The primary purpose that we use Check Point Cloud Firewall (formerly CloudGuard Network Security) is for the AWS account environment, securing our AWS accounts and environments.
We manage approximately 500-plus AWS accounts, handling all of our internal customers' AWS accounts. Most of the customers expose their applications using the internet-facing load balancers and expose some APIs to external web vendors or something similar. Our AWS environment is primarily made of EKS clusters, load balancers, transit gateways, and we have direct connect associations with our on-premises infrastructure. We have a lot of ECS and EC2 services. To manage all of them, when you build applications, you primarily expose them to the outside world or internet users across the globe. To protect all of this infrastructure, our applications, and our data running behind a VPC, we deployed Check Point Cloud Firewall (formerly CloudGuard Network Security) to monitor all our inbound traffic, ingress and egress traffic, and to potentially have some kind of threat intelligence in place.
We use it only for cloud, so I can recommend it only for cloud. I am not aware of the on-premises capabilities, but the name says CloudGuard Network Security, so I have focused my discussion on AWS.
What is most valuable?
From our personal usage, the most valuable feature I would say is the centralized policy management. We have organization accounts or root accounts in AWS through Landing Zones. In the case of Check Point Cloud Firewall (formerly CloudGuard Network Security) as well, we have centralized policy management. As I highlighted, we have closely 500 AWS accounts. If we have to configure them independently or individually, that becomes a complex, mammoth, and very tedious task, even to update something. With centralized policy management, we can apply consistent firewall and threat prevention rules across AWS environments without managing security for each VPC. I would say you configure something there, and it is applicable for all our AWS environments. The single view of all policies across all AWS accounts, I would consider it as the most beneficial feature. We have other options as well, such as integration with other AWS network services. Apart from that, the centralized monitoring and logging is very valuable. If we want to see which customers are having some issues or check the DDoS attacks, it will be easy for us to keep an eye on the monitoring and then evaluate the logs. There might be genuine cases of failures as well, which we are supposed to address. We have both the monitoring and logging capabilities.
What needs improvement?
The initial setup was primarily configured by our cybersecurity team, but as we progress using it based on our customer needs or as we progress and mature in terms of exposing our applications, we request ongoing amendments or changes to the security policies, including allowing a certain IP address or configuring the firewall rules that are potentially required for our applications. This is an ongoing process of how it is set up with base policies and how we upgrade it according to our customer needs.
For most of the software available out there, the initial complexity is to configure and use it, particularly in terms of large AWS accounts. We have multiple VPCs, transit gateways, and direct connect associations with on-premises infrastructure. What I would think is that if you have something like a readymade agent or some sort of automation that makes the deployment automation easier, that would be beneficial. We now see each and every single day tens and twenties of new products emerging, but I would still stick to my point that the initial configuration is somewhat difficult. This can be improved. Another point is that the dashboards are pretty much standard. Since I am from an AWS background, I will talk from an AWS perspective. If we have specific AWS-related dashboards or AWS service-related dashboards, for example, if we want to see who is accessing our EKS cluster, I would like to simply see what are all my metrics or dashboards. For example, we have something like Grafana dashboards. If you see, there are some prefabricated dashboards there for node level, EKS level, cluster level, DB level, and network level. If we have certain use-case-specific dashboards, that would really be helpful. From a policy configuration, deployment, and synchronization perspective, that would eventually take time. I would not specifically call it an improvement or to speed it up, but it is okay to manage. Then there are cost factors. Perhaps some sort of discounts for long-running customers, or if a customer is managing some 200 accounts, a discount would help.
Documentation can be considered as an area for improvement. Use case-specific dashboards, if it is possible, would also be beneficial. Providing customer insights onto the ongoing focus areas would be helpful. Dashboards can be improved, and documentation can be made easier, or use case-specific features can be introduced. Cost visibility, showing how much we are spending and how much we saved, and recommendations on new threats to customers to consider in the next iteration, would all be valuable additions. All these things are currently a bit lacking in the tool.
What do I think about the scalability of the solution?
In terms of scalability, it has a capability to handle as many AWS accounts as possible. Since it is a centralized system, it does not have any restrictions on how many consumers would be onboarded onto it. I do not think scalability is a problem or an issue for Check Point Cloud Firewall (formerly CloudGuard Network Security).
How are customer service and support?
I have not been involved directly in the customer support activities, but from my cybersecurity team, that support was top-notch.
Which solution did I use previously and why did I switch?
We previously relied on the standard AWS cloud-native services such as WAF, NACL, and security groups.
The licensing and pricing are beyond my responsibilities, as the cybersecurity team handles configuration at the top layer. They take care of the licensing, and pricing is purely from an organization decision. I do not have a say on that.
How was the initial setup?
The configuration was easy, time-saving, and cost-saving, resulting in customer satisfaction, time to market improvements, and we have confidence in the solution. We pretty much focus on the custom requirements rather than standard requirements of all the accounts.
What was our ROI?
The return on investment is certainly positive. The time to market is very fast compared to the standard process that we used to do. The fewer employees needed category shows that we technically are now focusing only on the customer-specific rules rather than on the standard rules. Whenever you build an account, those configurations come in-built from the Landing Zone configurations. We are pretty much sure that our environment is secured from day one.
I cannot quantify it, but I would say the centralized system has really helped us achieve things a bit faster.
Which other solutions did I evaluate?
There is something like a SmartConsole. We do not have the full permissions on the SmartConsole interface, but we got to know that there is a SmartConsole interface that provides very good visibility and simplifies the ongoing security management. We have two to three people that have access to that SmartConsole, and we can see whatever ongoing security changes are made in terms of good visibility onto where could be our next focus areas.
What other advice do I have?
Since I am not the one who configured it end-to-end, and since my expertise is not in cybersecurity, I would rate the solution a seven.
Check Point Cloud Firewall (formerly CloudGuard Network Security) saves a lot of time, effort, and cost. Rather than managing each individual account, having the centralized deployment across all accounts really makes our life easier. If you are currently handling 500 accounts or something similar, you cannot have a single entity that manages everything, which we did not have initially. But with Check Point Cloud Firewall (formerly CloudGuard Network Security), we have that option in place. It potentially improves visibility, reduces cost, reduces effort, reduces time, and certainly increases the time to market or improves the customer experience.
My deployment is in AWS.
It is not a direct use of the AI features from Check Point Cloud Firewall (formerly CloudGuard Network Security). But from my experience, I would rate it a seven, considering the feedback I have received from my cybersecurity team.
We are using cloud-native products like AWS WAF. We have NACLs, security groups, and AWS WAF is there. All of them are internal services. If you want to rely on that, you end up configuring all such rules or configurations across all the accounts. But when you compare this with Check Point Cloud Firewall (formerly CloudGuard Network Security), it provides a significantly much better centralized policy management, good visibility onto the policies, and advanced threat prevention capabilities. From an administrative perspective, that would be beyond my expertise, but closely working with the cybersecurity architects, we are convinced that Check Point Cloud Firewall has brought in a lot of value-add, rather than purely relying on the cloud-native AWS services for our day-to-day policy management.
My overall rating for this solution is seven out of ten.