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

Labels:

Comments

Post a Comment

Popular posts from this blog

How to modify SSH/HTTP/Telnet time out in Cisco ASA firewall?

How to modify SSH/HTTP/Telnet time out in Cisco ASA firewall? By default tcp idle timeout is 1:0:0 hh:mm:ss. If in case you need to modify it you can do it by MPF (Modular Policy Framework). Let us setup a custom timeout when traffic is coming from particular host 10.77.241.129. !— Match the traffic using the access-list —! object-group service DM_INLINE_TCP_1 tcp port-object eq www port-object eq ssh port-object eq telnet access-list outside_mpc extended permit tcp host 10.77.241.129 <source ip> any object-group DM_INLINE_TCP_1 !— Define the class map Cisco-class –! class-map Cisco-class match access-list outside_mpc !— Call this class-map into policy map and set the connection reset after 10 min when traffic is coming from particular host —! policy-map Cisco-policy class Cisco-class set connection timeout idle 0:10:00 reset !— Apply the policy-map Cisco-policy on the interface. —! service-policy Cisco-p...
Post a Comment
Read more

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 co...
Post a Comment
Read more

FortiGate: Upgrading the firmware via CLI

FortiGate: Upgrading the firmware via CLI To use the following procedure, you must have a TFTP or FTP server that FortiDB can connect to. You must also log in using the “admin” administrator account. Start the FTP or TFTP server. Copy the new firmware image file to the FTP or TFTP server. Log into the CLI. Verify that FortiDB can connect to the FTP or TFTP server. For example, if the IP address of the TFTP server is 192.168.1.168, enter the CLI command: execute ping 192.168.1.168 Enter the following command to copy the firmware image from the TFTP server to FortiDB: execute restore image ftp execute restore image tftp Where is the name and location of the firmware image file and or is the IP address of the FTP or TFTP server. For example, if the firmware image file name is image.out and the IP address of the FTP or TFTP server is 192.168.1.168, enter: execute restore image tftp image.out 192.168.1.168 FortiDB responds with the message: This oper...
Post a Comment
Read more