Checkpoint Lab -1 (Lab setup details) Tutorial

Setup Check point in distributed environment (2 sites)

Distributed environment is where we make a design decision to install the checkpoint blades separately and connect them like security management server (SMS), security gateway ETC. I would recommend folks to google and gain insight on what is a distributed & Standalone deployments are? What are pros and cons? What checkpoint recommends?

Lab setup VMware workstation 9 – The lab set up would look something like this –
Hardware - 2 client machine, One VM for manager, 2 VM’s for gateway (firewall – 2 sites main office and branch office) , 2 servers/machines capable of supporting  ftp, ssh, web site (very minimal HW requirement, this is just to test )

Network – The client and the manager @ Main Office (Net2), DMZ 1-Main Office (Net2), DMZ 2-Branch Office (Net4), Branch Office (Net3), client @ Branch office(Net5), external routing  ISP we can use our existing internet home connection (Net0).

I used Gaia R76 the iso can be downloaded from checkpoint website. Usually checkpoint provides 15 day evaluation with all features. But if your company has checkpoint firewall you can reach out to your rep and they would help you to get an extended license for 30 days or so.

VM Build – 

• Both the client machine I am using is a win7 machine, 2 GB RAM, 1 Processor, HD-40 GB, Net2

• SMS will be installed via ISO downloaded previously, 2 GB RAM, 1Processor, HD-40GB, Net2

• Main office Security Gateway is installed via ISO as well, 2 GB RAM, 1Processor, HD-40GB, Net2, Net5 & Net0.

• Branch office Security Gateway is installed via ISO as well, 2 GB RAM, 1Processor, HD-40GB, Net3, Net4 & Net0.

• First server I am using is a Win 2012 evaluation machine, 2 GB RAM, 1 Processor, HD-40 GB, Net4 (FTP, SSH and IIS).

• Second server I am using is a Win 2012 evaluation machine, 2 GB RAM, 1 Processor, HD-40 GB, Net5 (FTP, SSH and IIS).

• Net0 – ISP public access – 10.100.100.0/24

• Net2 – 10.1.1.0/24

• Net3 – 172.16.1.0/24

• Net4 – 172.16.2.0/24

• Net5 – 10.2.2.0/24

Snapshot of what my Virtual network editor looks like - 

Note – since these are actually VM’s in virtual environment you can use one server and flip the Net4 and Net5 to test scenarios from the client machine and below is the summery of networks I created for this lab scenario on the VM.

One arm vs. Two arm load balancing.

Two arm - in line mode - Routed mode In this senario the clients and the servers are in 2 different networks (2 arms) and can talk to each other via load balancer which sits between them - inline. Clients are front end, servers are back end with load balancer in between. In most of the cases the backend servers have the load balancer as their gateway and the source or client ip can be preserved.

NOTE - Only the destination IP is changed.

 Single arm - One arm In this mode the load balancer is not in-line, the clients and the servers are in the same network. There is no need for the servers to have load balancer as the gateway. Since we need to load balance the client will talk to the load balancer VIP and the server should be able to send the traffic back to the load balancer...but remember since the servers do not have the load balancers as the gateway we need to use SNAT for the servers to talk back to the LTM or it could cause assymetric routing problem.

NOTE - Both source and destination ip's are changed.

What is SSL handshake and how does it happen?

SSL handshake -

CLIENT - The client initiates the communication to the server over a secure port ex. 443, says Hello, and gives the server its SSL version, cipher settings and other information to the server telling it - "Hey you can talk to me using the information I just provided."

SERVER - Now the server replies to this Hello from client by saying Hello and gives the client its SSL version, cipher settings and other information to the client telling it - "Hey you can talk to me using the information I just provided." It also provides the client with its public key.
It’s like 2 couples sharing each other’s private phones numbers to talk privately.

Note If the client is requesting any server resources that require client authentication the server requests the client digital cert to be sent as well.

CLIENT - The client now uses all the data given by the server (data obtained during this handshake) creates a pre master secret key for the session and encrypts it with the server public key that it was given during step2. It then sends this pre master key to the server. (Only client has the pre master key for now.)

SERVER - The server decrypts this pre master key using its private key.

Note at this point after step 4 both the client and server has the pre master key.

CLIENT & SERVER - From this point on both the parties perform series of steps, starting from the same pre master key - generate a master secret password. Both client and server use this master key and generate symmetric keys which are used to encrypt and decrypt information during SSL session.

CLIENT - Client informs the server from this point on all future messages from it are going to be encrypted using the session key and then sends a separate encrypted message telling the server that client portion on SSL handshake has been completed.

SERVER - Pretty much does the same as above. Informs the client that from this point on all future messages from it are going to be encrypted using the session key and then sends a separate encrypted message telling the client that server portion on SSL handshake is now complete.

SSL handshake is now done and SSL session has begun. Whatever happens between the client and server is now encrypted and either parties use the symmetric keys to encrypt and decrypt.

Note - Symmetric encryption has begun after the last step. In this kind of encryption both the parties use the shared password (symmetric key) to encrypt and decrypt messages. But notice that to get to this point PKI (public and private key) infrastructure was in play. This is faster than situations where both the parties use public and private key all the time and would be taxing on the client and server.

Also keep in mind that if A encrypts a piece of information using B's Public key the only B who has the private key can decrypt it.
If A encrypts a piece of information using A's Private key then anyone who trusts A's public key can decrypt it. Successfully decrypting the information proves that it was send by A and no one else.

Head spinner but this is one of the most important topic and I tend to fall back on this explanation time to time.

F5 LTM SSL Configurations - Concept

The F5 LTM device is built to handle SSL traffic in load balancing scenario and meet most of the security requirements effectively. The 3 common SSL configurations that can be set up on LTM device are

• SSL Offloading
• SSL Re-Encryption
• SSL Passthrough

Typical load balancing infrastructure setup would be Client--->F5 LTM---->Servers hosting applications i.e. client traffic will be directed to a load balancer like F5 which in return (using complex algorithm) send the traffic to an appropriate server.

SSL Offloading - In this method the client traffic to F5 is sent as encrypted. Instead of the server decrypting and re-encrypting the traffic LTM would handle that part. So the client traffic is decrypted by the LTM and the decrypted traffic is sent to the server. The return communication from the server to client is encrypted by the LTM and sent back to the client. Thus sparing the server additional load of encryption and decryption. All the server resources can now be fully utilized to serve the application content or any other purpose they are built to do.

 SSL Offloading

Note - 

1. The communication between the server LTM and server is in clear txt.
2. Servers are setup to listen on unsecure ports ex Port 80.
3. Since the LTM decrypts the HTTP traffic it has now the ability to read the content (header, txt, cookies etc.) and all the persistence options can be applied. (Source address, Destination address, Cookies, SSL, SIP, Universal, MSRDP)

SSL Re-Encryption - In this method the LTM will re-encrypt the traffic before sending it to the servers. Client sends encrypted traffic to LTM, LTM then decrypts it and before send it to the servers or pool members re-encrypts it again. This method is generally used to satisfy the requirement of traffic to be encrypted between the LTM and Servers as well. This requirement might be put in place for additional security or prevent intrusion from within the network. When this method is used the servers will also have to decrypt and encrypt the traffic.

SSL Re-Encryption

Note –

1. The communication between the server LTM and server is secure.
2.  Servers are setup to listen on secure ports ex Port 443.
3.  Since the LTM initially decrypts the HTTP traffic it still has the ability to read the content (header, txt, cookies etc.) and all the persistence options can be applied same as SSL Offloading. (Source address, Destination address, Cookies, SSL, SIP, Universal, MSRDP)

SSL Pass through - As the name suggests the LTM's will just pass the traffic from client to servers absolving itself from any SSL related workload. Instead of forwarding SSL handshakes and connections to the servers directly it will just pass the client traffic to the servers. Usually this setup is used if the applications being served are anti SSL proxy or cannot consume decrypted traffic.

SSL Pass Through

Note - 

1. Since it’s just pass through LTM cannot read the headers which introduces limitations on persistence. Only non SSL information in the packet can be used to maintain persistence like source ip address, destination ip address.

I will try to post few more concept articles when time permits. Enjoy.

Tutorial - Raid setup on Dell - R710 using PERC H700 card

I embarked on a building a test Hyper-V machine and debated a lot on what an optimal Raid configuration should be. After much thought I decided to go with  RAID 1 for the OS and RAID 10 for the data store drive on which I will be running my VM's.

The RAID card I have is PERC H700 card but the same can be applied to  PERC 6/i Integrated card as well.

H/W info - 6 bays

0 and 1 - 180 GB disks, OS, RAID 1
2,3,4,5 - 500 GB disks, DataStore, RAID 10

Launch the config utility - by pressing Ctrl+R

This utility will have three TABs on the top.

• VD Mgmt – Virtual Disk Management, which will be selected by default.
• PD Mgmt – Physical Disk Management
• Ctrl Mgmt – Controller Management

If this is brand new setup you will see "No configuration present" if you are re-purposing an inherited H/W you might see the older setup. Please backup the data before you wipe out the existing configuration. Also the physical disks are displayed in the raw format.

When the new virtual disk VD creation is initiated you can see the below screen with the following options for Virtual Disk Management - 

• RAID Level
• PD Per Scan
• Secure VD
• Physical Disks Section

Basic Settings

• VD Size
• VD Name

Advanced Settings

• Stripe Element Size
• Read Policy
• Write Policy
• Force WB with no battery
• Initialize
• Configure Hot Spare

Chose RAID option - 

• RAID-0
• RAID-1
• RAID-5
• RAID-6
• RAID-10
• RAID-50

Press TAB to select the next option, Disk selection

Name the VD group  in my case its HyperV_OS and VM_DataStore.

I would recommend leaving all the advanced settings to the default values. if you want to config a spare go ahead and select that option.

• Stripe Element Size – Default value is 64KB
• Read Policy – Default value is Adaptive R
• Write Policy – Default Value is “Write Back”

By default, following values are not checked. i.e check-box not selected

• Force WB with no battery
• Initialize
• Configure HotSpare

Press TAB to jump to OK and press enter.  You’ll get the following warning message. Click OK to continue. This will successfully create the new Virtual Disk with RAID-1 configuration.

To view the configuration select the VD label as below and hit enter. Also once the VD group is setup the initialization of the disks will begin as well.

Once the VD is created, you’ll see a new ‘Disk Group 0′ under ‘PERC H700′. There will be a progress bar next to the ‘Virtual Disk 0′ showing the progress of the initialization.

Continue to create a second VD group for VM_DataStore. Pay attention to the VD group properties (Right hand side - yellow) how they are populated which will help you down the lane to setup additional disks or RAID controllers.

Hopefully someone would find this useful.

Unable to RDP to windows 7 (Lenovo) machine

My company recently purchased few Lenovo laptops and desktops. They came in with Windows 7 OEM install image. I was not able to RDP into few of those machines and further research led me to the below missing registry key.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

and the value for Security Packages should be


kerberos
msv1_0
schannel
wdigest
tspkg
pku2u

if you have similar issue just copy the above and update the field.

Windows 7 black screen after logging in via RDP.

I had this issue couple of day ago...there are many blogs out there how to deal with this black screen issue but the scenario I had was different. Based on going through multiple blogs users having ATI or GForce graphic cards were primarily affected, users having dual screens are also in soup. In my case I had a Intel card and my issue was black screen does not appear for all the users. For example user1 has no problem what so ever he was able to login and work but then user2 logs in all he sees in a black screen when he remotes in. I tried to disable bitmap caching, disable turn off monitor in power settings, disable power management to NIC as suggested by some folks. Nothing worked.

So I ended by deleting that particular user's profile (folder and registry) as per my previous blog and he was able to log in and issue did not happen. Also what I observed was user2 did not log in for quite some time and the issue came up again. Maybe the amount to time between the remote log in has some connection to getting black screen.

If you guys have any input I welcome it.