What is our primary use case?
The primary use is to protect the organization from any kind of attack. It is able to isolate, secure, and control every device on the network at all times. Solutions should have the ability to block infected devices from accessing corporate data and assets.
It provides access to the Internet for corporate resources in a secure manner. Our resources are used to host applications and services that are accessible to end-users over the Internet.
It is used to provide required/limited access for third parties who want to connect to our corporate network. Access is granted based on application type and should be independent of port or protocol.
It provides next-generation protection including IPS/Web Filtering/SSL decryption and more.
It offers centralized policy management capabilities for all firewalls.
How has it helped my organization?
This solution was able to provide access to our internet-based resources using our application/FQDN.
The license offers different modules for NGTP and SNBT. It provides multiple functionality or blades, which can be enabled on the firewall depending upon organizational requirements.
Other than stateful packet filtering with the NGTP license, it provides blades such as IPS/URL/VPN/Application Control/content awareness/Anti-Bot/Anti-Virus/Anti-Spam. With SNBT, it provides additional security using the SandBlast Threat Emulation and SandBlast Threat Extraction for Zero-day attacks in real-time.
Any file, before it reaches an endpoint, is executed in a virtual environment for analysis. Based on the verdict and configured policy, a decision will be made as to whether it should be delivered to the endpoint or not.
What is most valuable?
It provides the flexibility to use any module with the NGTP and SNBT license. Depending upon the requirements, the blades/module can be enabled on the firewall security gateway and it can be deployed easily.
In case SSL decryption or IPS need to be enabled on any security gateway, it is simple to do. We can go ahead and enable the module/blade and then create a policy, deploy it, and it will start to work.
It has a default five-user license for Mobile/SSL VPN, so the organization can check the solution any time or can even provide access to critical users on an as-needed basis, without getting the OEM involved, all on the same box.
For smaller organizations with the correct sizing of the appliance, they can use the full security solution on a single box. It will provide financial benefits along with reducing the cost of purchasing additional solutions or appliances.
For example:
- URL Filtering Module: It can replace the proxy solution for on-premises users with integration of application control and the Identity module. Active Directory access can be provided based on the User ID and the website or application.
- SSL VPN or SSL decryptor, and more.
- Core assignment for each interface, which can be done using the CLI. If the administrator determines that a particular interface requires more compute, he can manually assign additional cores accordingly. This is done by enabling hyperthreading on the firewall.
- The policy can be copied from any security gateway and pasted onto another one.
What needs improvement?
This is a zone-based firewall, which differs from other firewall solutions available on the market. It changes the way the admin manages firewall policy. The administrator has to be careful while defining policy because it can lead to configuration errors, allowing unwanted access.
For example, if a user needs to access the internet on the HTTPS port, then the administrator has to create a policy as below, rather than using NAT for assigning the user's machine to a public IP.
Source: User machine
Destination: any
Port: HTTPS
Action: allow (for allowing the user's machine access)
This has to be done along with the below policy:
Source: User machine
Destination: Other Zone created on Firewall
Port: HTTPS
Action: block
The two policies, together, mean that the user's machine will not be able to communicate with any other L3 Network created on the firewall.
The firewall throughput or performance reduces drastically after enabling each module/blade.
It does not provide for standalone configuration on the security gateway. Instead, you need to have a management server/smart console for managing it. This can be deployed on a dedicated server or can be deployed on the security gateway itself.
For how long have I used the solution?
I have been using the Check Point NGFW for more than eight years.
What do I think about the stability of the solution?
This solution is very much stable and does not require frequent changes in architecture. The patch frequency is limited and it does not require frequent maintenance windows in terms of downtime.
What do I think about the scalability of the solution?
This firewall is very much scalable. The introduction of Maestro has changed the concept of hyperscaling.
How are customer service and technical support?
The technical support is excellent. The center is located in major cities in India along with the Check Point presales team.
Which solution did I use previously and why did I switch?
We did not use another solution prior to this one. We have been using Check Point for a long time.
How was the initial setup?
During the initial setup, support is excellent. It is a well-known OEM and they have people ready to resolve any issue that should arise.
What about the implementation team?
Our in-house team deployed it with support from the OEM.
What's my experience with pricing, setup cost, and licensing?
Cost-wise, it cheaper than industry leaders such as Palo Alto. The licensing is straightforward; there are only three types of licenses that include NGFW, NGTP, and SNBT, so the organization can choose its license according to their requirements.
Which other solutions did I evaluate?
We have evaluated solutions by Juniper, Cisco, and Palo Alto.
What other advice do I have?
Before implementing the security gateway, you need to be sure about the license and modules that you are going to enable. This includes determining the proper size, as it can affect throughput drastically after enabling each module. This is especially true for SSL decryption.
The architecture needs to be studied before finalizing, as the configuration is done remotely using the centralized smart console. All of the security gateways need to be connected to the management server for any policy configuration, and they should be available at all times.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.