Checkpoint Objects

Objects are the central piece of most of the firewalls that currently
exist – be it the traditional stateful firewalls or the over-used term
“Next-Generation” firewall. Objects are the containers for IP addresses,
subnets, services i.e. ports. The rationale being:

Create an object
Use that object in the Firewall rules, NAT policies, VPN communities
etc.
In case the IP address / port needs to be changed, simple make that
change in the object , so that the changes get automatically reflected in all
the firewall rules, NAT policies, VPN communities that use the object. This is
the sole purpose of the objects’ existence (besides making the IP addresses or
ports, more admin friendly)
Multiple network or service objects are grouped together in a Network or
Service group

Depending on the type of the value
that goes into the object, Checkpoint has multiple types of objects.

Network Object
Host Object
Network Group
Service Object

The Checkpoint objects in R80.x can be created from the main work pane, via “Object Categories” (located in a pane, towards the right of the dashboard), as below. The steps to create the objects remains the same as its predecessors.

1. Network Object

2. Host Object

Optional: In case of automatic NAT configuration for the object, behind a particular gateway. In the below example host object with the original IP of 1.1.1.1 (created above) will be NATted to the IP address of 2.2.2.2 and apply for the Gateway “BranchOffice”

3. Network Group

4. Service Objects – The ports can be single (just mention the number) or a range of ports (hyphen separated lower and upper port numbers)

Comments

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. ...

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 - Understanding Kerberos (for Golden Ticket Attack)

Kerberos = Network Authentication Protocol used by AD environments Provides authentication by issuing tickets to authenticate users and allow them access to the services Tickets are distibuted by KDC (Key Distribution Center), which is typically a Domain Controller (DC) During initial authentication, a TGT (Ticket Granting Ticket) is a ticket asigned to a user by KDC. TGT is later used to authenticate the user to the KDC in order to request a service ticket from TGS (Ticket Granting Service). Service tickets are granted for authentication against services. List of steps / negotiations for Kerberos authentication (of the user with the service): The user requests (AS-REQ) a TGT from the KDC and the KDC verifies and validates the credentials and user information. This request if often done automatically at login. After authenticating the user, the KDC sends an encrypted TGT back to the requester (AS-REP) . The user presents the TGT to the DC and requests a TGS (TGS-...

Tejas Jain

Search This Blog