R80.10 is now GA (General Availability). There is a long list of enhancements, but the largest one is probably the fact that for the first time R80 is now available for the gateway with significant performance enhancements. The overall list of features is pretty long so I am not going to post those here, but it is well worth a look.

There is also an extensive list of “known issues”¬†which you should always check before moving to a major version. One limitation that I noticed in EA for R80 and R80.10 is the removal of the “follow-up” category for IPS signatures. This one boggles my mind especially since “follow-up” is part of the Check Point IPS “best practices” procedure. Another one that I will be looking for is the “where used” search not being as precise as it should. (fixed in R80.10).

Overall, it will be interesting to see how this release is embraced by customers. Every vendor’s product has issues, but I would argue that Check Point sets the bar pretty high when it comes to quality. On paper, this looks to be a very compelling release.

 

R80.10 is GA

2 thoughts on “R80.10 is GA

  • May 24, 2017 at 1:28 pm
    Permalink

    It looks like they’ve replaced “follow-up” with “staging mode” now. You can configure default actions for newly downloaded signatures based on performance impact, severity, etc. For example, you can say all newly downloaded signatures go into “Detect (Staging)”, but if the signature is severity high or above put it right into Prevent mode.

    This will take some getting used to.

  • June 4, 2017 at 1:02 pm
    Permalink

    Hi Pat,

    We would love to hear your feedback on the release!

    Check Point has a rapid transparency policy regarding limitation lists, no matter if the limitation is big or small, new or 3 years old. We hope that by doing this we can convince our customers on the amount of quality and documentation that we put into newly released versions, as well as an 8-month old early availability program with customers running the release in production and reporting issues.

    Specifically – Follow-Up has simply been renamed to “Staging” – see https://community.checkpoint.com/thread/1243 . The one feature that is missing is the option to manually flag a non-staging protection back to “staging”. I apologize for the miss-phrasing in the known-limitations list.

Leave a Reply

Your email address will not be published. Required fields are marked *