Checkpoint R80.10 - Smart Update

It's a fine sunny morning and you are in a particularly good mood with the prospect of configuring few dozen rules on your newly upgraded Checkpoint R80.10 Management Server. You bring up your new Smart Console window:

You press the login button and bammm...

You go to the Checkpoint Licensing
center (I will cover Checkpoint licensing in a separate article, later), get
the CPLicenseFile.lic and download it.

Now begins a hunt for our beloved
Smart Update.. You don't find it!! That's where Google comes in "Smart
Update for checkpoint R80.10".. and this is where you land (overly
optimistic, if you know what I mean )

Here is how you fix the Licensing
issue:

1. Locate and double-click the
below file in the below directory:

C:\Program
Files\CheckPoint\SmartConsole\<Version>\PROGRAM\SmartDistributor

C:\Program Files (x86)\CheckPoint\SmartConsole\<Version>\PROGRAM\SmartDistributor For Example

2. You will find the legacy Smart Update (with R77.x changed to R80.10), as below:

3. Now follow the usual Checkpoint
Licensing steps. If you don't know please click here.

Hope your mood continues to stay good!!

Comments

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

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

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

Tejas Jain

Search This Blog