What needs improvement with Check Point Endpoint Remote Access VPN?

Please share with the community what you think needs improvement with Check Point Endpoint Remote Access VPN.

What are its weaknesses? What would you like to see changed in a future version?

33 Answers

author avatar
Top 10Real User

There is always room for innovation and the addition of new features.

author avatar
Top 20Real User

I cannot see the full effect of the antibot solution because it relies on having access to the DNS queries, which might not go through the Check Point firewall when you're using it for perimeter networks. In this case Check Point will not identify the actual source of the DNS queries associated with antibot activity. This may be related to the customer architecture, however, and not due to product limitation. I don't know if it can be improved on the Check Point side or not. The solution should allow for the automatic identification of destinations. We have a URL qualification on the on-premises deployment model; this should also be the case on the cloud. The automatic classification should be done by the cloud team instead of having to specify or subscribe to a RSS for the information, we should be able to have an object that represents such cloud services. It's possible that Check Point already allows for this, but if they don't they should.

author avatar
Top 5LeaderboardReal User

The solution should include the ability to integrate the equipment's functionality with others. For example, we would like Checkpoint to be able to integrate easily to the public key infrastructure. According to Checkpoint, there is no use case for this right now. The interface itself needs improvement. When you need to create something, you have to go through a lot of steps. It needs to be simplified.

Find out what your peers are saying about Check Point, Microsoft, Dell EMC and others in Remote Access. Updated: October 2020.
442,041 professionals have used our research since 2012.