Wednesday, 11 September 2013

Pyrit -WPA/WPA2-PSK Epic Fail-

Pyrit allows to create massive databases, pre-computing part of the IEEE 802.11 WPA/WPA2-PSK authentication phase in a space-time-tradeoff. Exploiting the computational power of Many-Core- and other platforms through ATI-StreamNvidia CUDA and OpenCL, it is currently by far the most powerful attack against one of the world's most used security-protocols.

WPA/WPA2-PSK is a subset of IEEE 802.11 WPA/WPA2 that skips the complex task of key distribution and client authentication by assigning every participating party the same pre shared key. This master key is derived from a password which the administrating user has to pre-configure e.g. on his laptop and the Access Point. When the laptop creates a connection to the Access Point, a new session key is derived from themaster key to encrypt and authenticate following traffic. The "shortcut" of using a single master key instead of per-user keys eases deployment of WPA/WPA2-protected networks for home- and small-office-use at the cost of making the protocol vulnerable to brute-force-attacks against it's key negotiation phase; it allows to ultimately reveal the password that protects the network. This vulnerability has to be considered exceptionally disastrous as the protocol allows much of the key derivation to be pre-computed, making simple brute-force-attacks even more alluring to the attacker. For more background see this article on the project's blog.

Monday, 2 September 2013

R77 is now available!

It seems to be the best one ever.

What's New in R77

New Threat Emulation Software Blade

The new Threat Emulation Software Blade blocks attacks which cannot be detected by signatures. It opens inspected files inside secure emulation environments to detect malicious behavior. It can be deployed as a cloud service or as a private (local) cloud.

New Check Point Compliance Blade

This new Software Blade analyzes your environment for compliance with major regulations and international standards. Check Point Compliance Blade generates detailed reports, with best practice recommendations taken from the large Check Point library. Check Point Compliance Blade sends alerts for policy changes that can affect compliance.

HyperSPECT Technology

Improvements to deep packet inspection engines boost performance for IPS and for Application and URL Filtering Software Blades Software Blades.
  • Supports SMT (Hyper-Threading)
  • Optimizations to DPI engines including streamers, parsers and pattern matching engines

Gaia Operating System Enhancements

  • Centrally manage basic network configuration
  • Back up and restore, run scripts, remote shell, and more, from a central console
  • Synchronize cluster members with Gaia OS configuration cloning

Enhanced Gaia Software Updates

Update the Gaia operating system with the enhanced Automated Software Updates tool:
  • Clean install of full image and upgrade of optimally sized package from the Check Point Cloud
  • Up to 90% less downtime for Security Gateway upgrade
  • Export and import of Gaia software update packages
  • New WebUI features with enhanced usability

Enhanced Identity Awareness

  • New identity acquisition method: RADIUS Accounting
  • Automatic update of LDAP group membership changes
  • Improved Identity Agent installation, with support for repair tools
  • New MSI configuration tool for Agent distribution


a lot more at;

Thursday, 29 August 2013

Sending Syslog flow to an External Log Server

Dear Checkpoint Fellows and Followers,

Syslog data is possible to be sent as shown in sk33423, however only from physical boxes.

If you have VSX infrastructure, it is not possible to send syslogs of each vsx customer to another syslog server. All and all..


Checkpoint R77

Very excited to test the new blades! :)

Friday, 2 August 2013

Check Point R75.47 Released!

The release notes and the resolved issues, it’s mainly a maintenance or bug fix version.

There are a lot of fixed bugs.

It would be good to install the version firstly within the test environment, and then get it into production a.s.a.p.

Wednesday, 31 July 2013

License Info Tool / Checkpoint

License Tool for Checkpoint. I found it pretty useful actually as the license issues seem complicated most often. My Products > License Info Tool.

Sunday, 21 July 2013

Fortinet Upgrade Procedures

The upgrade processes have usually been a issue with Check Point. However, it is unbelievably easy for security vendor Fortinet (even in the cluster env.)

- .out file is downloaded from the support site.
- it is uploaded through GUI.

then, all process goes on automatically; firstly the active member is upgraded with losing 4 - 6 ping packets, and then 2-3 ping lost while  upgrading the second member.

I suppose the reason is truly the architecture difference behind these boxes.

Friday, 22 February 2013

Network Troubleshooting - Cisco Packet Flow

To be or not to be.
Incoming or Outgoing Packets, sometimes understanding these two subjects are very vital in troubleshooting process.

ip access-list  extended gre-debug-out
permit gre any any log // optional 
permit ip any any log

ip access-list  extended gre-debug-in
permit gre any any log // optional
permit ip any any log

interface GigabitEthernet0/1
ip access-group gre-debug-in in
ip access-group gre-debug-out out

Here it is; 

show ip access-list gre-debug-in

show ip access-list gre-debug-out out

believe me you will like the result..

Identity Awareness - User & Machine Identification

Even though you see users and/or machines as acquired in Smart Dashboard, pdp monitor is the place where AD query comes in. If you do not see users/machines in pdp monitor, It means that Check Point did not actually acquire the users/machines.

pdp monitor all |more

pdp monitor all |grep machine/username

Friday, 15 February 2013

IPS Update: ips scheduled update ended with errors

Check the internet connection on SMC and Check dns config to see resolves to an IP.

To manually update the IPS database;

1- Close all GUI applications,
2- Open a GUIDBEdit to the SMC (Application:GuiDBedit.exe)
3- Search (Search->Find) for: autoupdate_and_install_status_obj

Once found you will see a field named status under that object.
4- Change the value of status 0
5- Save changes,close GUIDBEDIT
6- Open Dashboard and verify if the issue resolved.

Note : There is a fix for this issue, Request it from Support.

Wednesday, 13 February 2013

ClusterXL - Do not Consume Public IPs for ClusterXL

Configuring Cluster Addresses on Different Subnets
Only one routable IP address is required in a ClusterXL cluster, for the virtual cluster interface that faces the Internet. All cluster member physical IP addresses can be non-routable.Configuring different subnets for the cluster IP addresses and the member addresses is useful in order to:

- Enable a multi-machine cluster to replace a single-machine gateway in a pre-configured network, without the need to allocate new addresses to the cluster members.
- Allow organizations to use only one routable address for the ClusterXL Gateway Cluster. This saves routable addresses.
ClusterXL virtual IPs and your members physical (or VLAN) interfaces do not need to be on the same subnet. So you can simply use whichever addresses you like for each of the cluster interfaces (apart from internal/management and external/VPN-routable interfaces obviously). And of course this applies to physical untagged interfaces unlike our case too.
I settled for using  tiny Class B private space /30 subnets for each VLAN, enough for just our 2 cluster members like this. The topology would then look like this.

Monday, 11 February 2013

Smart Event & Reporter (CPU Peaks)

# evstop
# rm –r * $RTDIR/distrib/*
# evstart
SmartEvent konsolu içersinden policy install yapalım.

If not resolved,

# fw debug cpsemd on TDERROR_ALL_ALL=5
# fw debug cpsead on TDERROR_ALL_ALL=5

to end debug;

# fw debug cpsemd off TDERROR_ALL_ALL=0
# fw debug cpsead off TDERROR_ALL_ALL=0

Then check these files $RTDIR/log/cpsemd.elg* and $RTDIR/log/cpsead.elg*

Wednesday, 6 February 2013

Check Point - Identity Awareness (Security Event Logs)

Check Point Identity Awareness (had to supply all PDC in order to capture all IA.)

AD Query reads these events from the Security Event log:
 On Windows Server 2003 domain controllers - 672, 673, 674
 On Windows Server 2008 domain controllers - 4624, 4769, 4768, 4770

If the domain controller does not generate these events (by default they are generated), refer to Microsoft Active Directory documentation for instructions on how to configure these events.

Monday, 4 February 2013

VPN Debugging – Check Point

Vpn debug on – vpn debug off

Vpn debug ikeon // vpn debug ikeoff

vpn tu // remove all Sas for either the peer which are about the create the tunnel or all tunnels.
fw monitor –e ‘accept src=IP or dst=IP;’

SmartDashboard Connectivity Issues

Cpwd_admin list // check for the fwm whether it is up

fw debug fwm 0 TDERROR_ALL_ALL=5

tail –f $FWDIR/log/fwm.elg

Network Troubleshooting – Check Point

Route –n > routes.txt

ifconfig  -a > interfaces.txt

SecureXL is enabled or disabled <check on cpconfig>

fw monitor -e "accept src=IP_Number or dst=IP_Number;" -o monitor.out
fw ctl zdebug + drop > ctlzdebug.txt
fw ctl zdebug + dtop > ctlzdebug2.txt

[to stop the logging  “Ctrl + C”]

Monday, 21 January 2013

Removing old Check Point packages and files after an upgrade

Check Point releases a great script which erases old CP packages and files causing disc issues later on. Here it is;
Solution ID:sk91060
Product:Security Gateway, Security Management, 2012 Models Security Appliances, UTM-1, Power-1, Smart-1
Version:R70, R71, R75, R75.10, R75.20, R75.30, R75.40, R75.40VS
OS:SecurePlatform 2.6, Gaia
Platform / Model:All
Date Created:08-Jan-2013
Last Modified:20-Jan-2013
Rate this document
[Click on the stars to rate]
  • After an upgrade, the packages of the old version are not deleted automatically.

    For example, when upgrading from R71 to R75, the old R71 packages and files remain on the system. This could lead to a disk space issue, especially after several upgrades.

Tuesday, 8 January 2013

Checkpoint IPSec VPN with Non-Checkpoint Products (Such as, PFsense, DrayTek etc.)

Non-Check Point products does not have "ike_use_largest_possible_subnets (supernetting)" feature, this is the reason why we need to disable that feature on Check Point.
(Exchanging keys with another vendor gateway uses largest possible subnet –Check Point uses the best possible subnet to increase the performance while doing IKE key exchanges by default)

DNS packets should not be allowed firstly, otherwise that results DNS resolution problems for VPN domains.

# dbedit

Enter Server name (ENTER for 'localhost'): 

Enter User Name: fwadmin

Enter User Password: abc123