Skip to main content

IPSEC

                                                 IPSEC

IPSEC consist of multiple protocols:
Internet Security Association and Key Management Protocol (ISAKMP) A framework for the negotiation and management of security associations between peers (traverses UDP/500)
Internet Key Exchange (IKE) Responsible for key agreement using asymmetric cryptography
Encapsulating Security Payload (ESP) Provides data encryption, data integrity, and peer authentication; IP protocol 50
Authentication Header (AH) Provides data integrity and peer authentication, but not data encryption; IP protocol 51

Encryption algorithm:
  Type Key Length (Bits) Strength
DES Symmetric 56 Weak
3DES Symmetric 168 Medium
AES Symmetric 128/192/256 Strong
RSA Asymmetric 1024+ Strong

HASH Algorithm:
Length (Bits) Strength
  MD5 128   Medium
  SHA-1 160   Strong

IPSEC Phase:
Phase 1 A bidirectional ISAKMP SA is established between peers to provide a secure management channel (IKE in main or aggressive mode)
Phase 1.5 (optional) Xauth can optionally be implemented to enforce user authentication
Phase 2 Two unidirectional IPsec SAs are established for data transfer using separate keys (IKE quick mode)

IPSEC modes:
Transport Mode The ESP or AH header is inserted behind the IP header the IP header can be authenticated but not encrypted
Tunnel Mode A new IP header is created in place of the original this allows for encryption of the entire original packet

IPSEC configuration template:

ISAKMP Policy crypto isakmp policy 10
encryption aes 256
hash sha
authentication pre-share
group 2
lifetime 3600

  ISAKMP Pre-Shared Key crypto isakmp key 1 SECRET_KEY address 10.1.1.1

  IPsec Transform Set crypto ipsec transform-set MyTS esp-aes 256 esp-sha-hmac mode tunnel

  IPsec Profile crypto ipsec profile MyProfile
set transform-set MyTS

Virtual Tunnel Interface interface Tunnel0                           
ip address 172.16.0.1 255.255.255.252
tunnel source 10.0.0.1
tunnel destination 10.0.0.2
tunnel mode ipsec ipv4
tunnel protection ipsec profile MyProfile 

Troubleshooting 
show crypto isakmp sa
show crypto isakmp policy
show crypto ipsec sa
show crypto ipsec transform-set
debug crypto {isakmp | ipsec}
Terminology:
Data Integrity Secure hashing (HMAC) is used to ensure data has not been altered in transit
Data Confidentiality Encryption is used to ensure data cannot be intercepted by a third party
Data Origin Authentication Authentication of the SA peer
Anti-replay Sequence numbers are used to detect and discard duplicate packets
Hash Message Authentication Code (HMAC) A hash of the data and secret key used to provide message authenticity
Diffie-Hellman Exchange A shared secret key is established over an insecure path using public and private keys

Comments

Popular posts from this blog

Checkpoint firewall common commands part 2

Checkpoint firewall common commands part 2 For basic firewall informaton gathering: fgate stat -Status and statistics of Flood-Gate-1. fwaccel <stat|stats|conns>  – View status, statistics or connection table of SecureXL. fw getifs -Show list of configured interfaces with IP and netmask. cpstat <app_flag> [-f flavour] -View OS, HW and CP application status. Issue cpstat without any options to see all possible application flags <app_flag> and corresponding flavours. Examples: cpstat fw -f policy – verbose policy info cpstat os -f cpu – CPU utilization statistics cpinfo -y all   -List all installed patches and hotfixes. cpd_sched_config print -Show task scheduled with CPD scheduler. enabled_blades -View enabled software blades avsu_client [-app <app>]   , get_version <app>  -Get signature version and status of content security .Without the -app option “Anti Virus” is used. show configuration -Show

Unable to Connect to Server Checkpoint R80

Unable to Connect to Server Checkpoint R80 Unable to Connect to Server A connection to the management server will fail if: A firewall between SmartConsole and the management server blocks Port 19009 -  port 19009 is used for a new R80 service. Allow traffic on this port for all clients and management servers. No GUI clients are assigned -  Open the Gaia Portal. If the First Time Configuration Wizard opens, complete it. If the First Time Configuration Wizard has already run, open  User Management > GUI Clients  and add a client. When using Multi-Domain Security Management, connect SmartConsole to the Multi-Domain Server and make sure the domains have GUI clients assigned to them. The required processes are not reachable -  Make sure the computer with SmartConsole installed can reach the IP address of the management server, and that these server processes are up and running: cpm fwm Operation time out  – Your connection to the management (cloud demo

Configuring Proxy ARP for Manual NAT

Configuring Proxy ARP for Manual NAT Symptoms After creating a Manual Static NAT rule, Security Gateway does not answer the ARP Requests for the Static NATed IP address that was configured in the Manual NAT rule. Security Gateway replies to ARP requests with a wrong MAC address, mostly for the NAT traffic.  Introduction Let us consider the following scenario: Two networks ( Network_A  and  Network_B ) are separated by a Security Gateway (single Security Gateway or ClusterXL). On each network, there is a host ( Host_A  on  Network_A ,  Host_B  on  Network_B ). Let us assume, that  Network_A  represents the  Internal  network, and  Network_B  represents the  External  network. According to the existing standards, when  Host_B  needs to send data to  Host_A , an ARP Request for the MAC address of  Host_A  will be sent by  Host_B  to  Network_B . Since  Host_A  is located on another network, and the Security Gateway acts as a router, this ARP Request (sent