topic Re: Checkpoint R80 file exports for SmartCenter R80.x or greater - new proc in Expedition Discussions

Checkpoint R80 file exports for SmartCenter R80.x or greater - new procedure

doug-elliott — Thu, 23 Apr 2020 13:44:18 GMT

I have a 2 live articles addressing the file export procedure from around April of 2019.

Expedition version 1.1.66.2 shows a new procedure on the Checkpoint R80+ file import page requiring the download, install, and run of a jar file to compile and export files necessary for import into Expedition. The procedure involves uploading and running a .jar file on the client's Checkpoint mgmt server. I need documentation to understand and further explain any risks to the management server and would like more depth on the procedure if anyone has run though it. I would like to do no harm during the process. Anyone have success stories to share?

Re: Checkpoint R80 file exports for SmartCenter R80.x or greater - new proc

lychiang — Tue, 05 May 2020 21:51:01 GMT

Hi Doug-Elliott,

The jar file is created by checkpoint, maybe you want to ask them in the the checkpoint github.

https://github.com/CheckPointSW/ShowPolicyPackage/

Re: Checkpoint R80 file exports for SmartCenter R80.x or greater - new proc

dgildelaig — Thu, 07 May 2020 08:22:20 GMT

In addition to what Lynn has commented, we are suggesting this approach because we have experienced that this is the only current way to collect Checkpoint configurations that are not missing nested address objects.

We have seen that other methods may result in empty address groups if the members are not directly referenced in the security rules. This is what we call nested objects.

Checkpoint identified their issue as well and released the .jar file to overcome the issue