Skip to main content

Checkpoint Security Gateway Offline CPUSE upgrade - R77.x to R80.x


Call me an old-fashioned Network
Engineer or call it my penchant for rendering my Network skills a geeky
touch, I prefer to perform my device upgrades the old fashioned way - via CLI -
as and when possible. My approach towards Checkpoint upgrade is no different!





Here we will perform the Checkpoint
Security Gateway upgrade from R77.30 to R80.10 via Offline CPUSE (Checkpoint
Upgrade Service Engine). The name should make it evident that we are not
expecting the Gateway to communicate with the Checkpoint Cloud automatically or
provide auto-recommendations for hotfixes or upgrades.





A word of caution before you begin
with the upgrade: Ensure that you have sufficient disk space. One way to ensure
that is:





1. From your expert mode (bash), type
"lvm_manager". Select option 1





2. You will see the disk allocation
to various partitions. Check for "lvm_log". The optimum value
for this should be 10 GB. A 7-8 GB space should suffice, but 5 GB will
definitely prove to be insufficient (I have personally run into disk space
issues at 5 GB)





3. In case you wish to resize the log
partition, select option 2, enter the target value and "Exit". The
device will prompt for a reboot. Proceed with it.





4. Ensure that your CPUSE build
is 802 or above.





5. Make sure to save your
configuration commencing the below steps, as you won't get a confirmation
prompt for reboot. The device simply will!!





My setup:





Security Gateway image: Check_Point_R77.30_Install_and_Upgrade_T5.Gaia.iso





CPUSE build: 14xx (comes
by default with the latest Check_Point_R77.30_Install_and_Upgrade_T5.Gaia.iso)





Target upgrade image: Check_Point_R80.10_T462_Fresh_Install_and_Upgrade_from_R7X.tgz (Please
note that this image is meant to be used only if you are upgrading from R7x..
It won't work in case you are opting for a fresh install)





Step 1:





Copy the Upgrade image: Check_Point_R80.10_T462_Fresh_Install_and_Upgrade_from_R7X.tgz to
/var/tmp (or any other temporary directory of low significance)





Step 2:





Import the image using : installer
import local
/var/tmp/Check_Point_R80.10_T462_Fresh_Install_and_Upgrade_from_R7X.tgz.





Once it has been imported successfully, you should get the "Result:" as below:









Step 3:





Confirm if you see the new image in the installer packages:









Step 4:





Now verify if the feasibility of the upgrade from the current software version to the target version (image)









Step 5:





Proceed with the installation as below:









After the reboot, you will get your magical R80.x login prompt.









Happy Upgrading..! :)


Labels:

Comments

Post a Comment

Popular posts from this blog

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o
Post a Comment
Read more

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account.  That password hash is s
3 comments
Read more

Tejas Jain - GCP Constraints & Random Facts

1.  Google Cloud Interconnect Security Cloud Interconnect does not encrypt the connection between your on-premises network and Google's network. Cloud VPN cannot be used with Dedicated Interconnect For additional security, use application-level encryption or your own VPN 2. While using Cloud CDN, the default time-to-live (TTL) for content caching is 3600 seconds = 60 mins 3. Cloud NAT sends only the translation logs and error logs to Cloud Logging service. 4. GCP Dedicated Interconnect - On Premises network device requirements:     10-Gbps circuits, single mode fiber or 100-Gbps circuits, single mode fiber     IPv4 link local addressing     LACP, even if you are using single circuit     EBGP-4 with multi-hop     802.1Q VLANs 5. While using Cloud VPN, the recommended MTU to be configured on the peer VPN  gateway = 1460 bytes 6. Each instance must have at least one network interface. The maximum number of network instances per instance is 8, depending on the instance's machine
1 comment
Read more