It is a stable solution. We implemented the solution in HA. This is because the solution is highly available and can withstand hardware failures and software upgrades.

Once the solution is implemented, there is no need for any further downtime for the Check Point server. Because once we change any policy, we can break the High Availability (HA) session and define the new policy on the Check Point Security Gateway (SGW) in isolation. This allows us to test the new policy without affecting the production traffic. Once the new policy is tested and active, we can then activate it on the HA pair and bring the HA session back up. This process ensures that we can make changes to the policy without any interruption to the user experience.

It is a really stable solution. I would rate the stability a ten out of ten.

It has excellent stability and has not presented errors since it was implemented.

I am impressed by the secure network infrastructure for sharing information.

The solution offers high stability.

It's highly stable and can be effortlessly integrated with all kinds of IT systems and internal servers.

The product is stable.

The solution is stable.

During the two years of implementation in the organization, it has not presented any problem. Its stability is very good.

This solution is stable.

The product is stable.

It's a stable product.

I have not experienced downtime.

The Check Point Anti-Spam and Email Security Software Blade is stable.

This solution has been stable and is working very well in our environment.

The stability is generally good if there are no power-related issues. 

We have had no problems with the performance of the firewalls.

It is a very stable solution.

It is one of the most stable solutions. It is worth emphasizing that one of my common uses is to have it established in one of the solutions that are in a cluster, and this gives double stability. 

For small mail flows, this product is stable.

No.