You are on page 1of 10

AMBO UNIVERSITY

INSTITUTE OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE
GRADUATE PROGRAM IN COMPUTER SCIENCE

ASSIGNMENT REPORT ON IP SECURITY

Prepared by Dejene Techane

This paper is prepared for Computer and Network Security course taught by Henock
Mulugeta(PhD)

DECEMBER 10, 2016


AMBO, ETHIOPIA

Abstract
IPsec (Internet Protocol Security) is a framework for a set of protocols for security at the network or
packet processing layer of network communication. Earlier security approaches have inserted
security at the Application layer of the communications model. IPsec is said to be especially useful
for implementing virtual private networks and for remote user access through dial-up connection to
private networks. IP security (IPSec) is a capability that can be added to either current version of the
internet protocol (IPv4 or IPv6), by means of additional headers. IPsec encompasses three
functional areas authentication, confidentiality and key management. Authentication makes use of
HMAC message authentication code. Authentication mode can be applied to the entire original IP
packet (tunnel mode) or to all of

the packet except for the IP header (transport mode).

Confidentiality is provided by an encryption format known as encapsulating security payload. Both


tunnel and transport modes can be accommodated. IPSec defines a number of techniques for key
management. A big advantage of IPsec is that security arrangements can be handled without
requiring changes to individual user computers. The primary objective of recent work in this area is
to improve robustness of the security mechanism at IP layer for users who request security.
1.1. Introduction
In today's massively interconnected business world of the Internet, intranets, branch offices, and
remote access, sensitive information constantly crosses the networks. Without security, both public
and private networks are susceptible to unauthorized monitoring and access. The challenge for
network administrators and other Information System professionals is to ensure that this traffic is:

Safe from data modification while enroute.

Safe from interception, viewing, or copying.

Safe from being accessed by unauthenticated parties.

These issues are known as data integrity, confidentiality, and authentication. In addition, replay
protection prevents acceptance of a resent packet. Therefore, there are different network security
protocols widespread use for protecting private and public networks such as IP Security(IPSec),
Transport Layer Security(TLS) and Secure Shell(SSH) . Hence, only IPsec protects all application
traffic over an IP network. Applications can be automatically secured by IPsec at the IP layer.
Designed by the Internet Engineering Task Force (IETF) for the Internet Protocol, IPSec supports
network-level authentication, data integrity, and encryption. IPSec integrates with the inherent
security of the IP datagram to provide the ideal platform for safeguarding intranet and Internet
communications. Because IP Security is deployed below the transport level, network managers (and
software vendors) are spared the trouble and expense of trying to deploy and coordinate security

one application at a time. The IPSec framework does not specify exactly which encryption
algorithms must be used by its implementations. Instead, it provides an empty infrastructure where
the desired algorithms may be set. This actually is a smart design decision, because it allows the
implementations to be modular, customizable for specific problems and easily up gradable with new
algorithms. A standard set of default algorithms is specified by the IETF in order to foster the early
adoption of IPSec.
IP security refers to security mechanism implemented at the IP (Internet Protocol) Layer to ensure
integrity, authentication and confidentiality of data during transmission in the open Internet
environment. Internet Protocol Security (IPsec) is a protocol suite for secure Internet Protocol (IP)
communications that works by authenticating and encrypting each IP packet of a communication
session.
IPSec is based on an end-to-end security model, meaning that the only computers that must know
about the traffic being secured are the sending and receiving computers. Each handles security at its
respective end, with the assumption that the medium over which the communication takes place is
not secure. Any computers that only route data from source to destination are not required to
support IPSec. This model allows IPSec to be successfully deployed for your existing enterprise
scenarios:
Local area network (LAN): client/server, peer to peer.
Wide area network (WAN): router to router, gateway to gateway.
Remote access: dial-up clients; Internet access from private networks.
1.2 Goals and Objective of IP Security
IP Security is designed to provide interoperable, high quality, cryptographically-based security for
IPv4 and IPv6.

The set of security services offered includes access control, connectionless

integrity, data origin authentication, protection against replays (a form of partial sequence integrity),
confidentiality (encryption) and limited traffic flow confidentiality. These services are provided at
the IP layer, offering protection for IP and/or upper layer protocols.

1.3 Security architecture


Architecture: Covers the general concepts, security requirements, definitions and mechanisms
defining IPsec technology.

AH

ESP

Authentication Header

Encapsulating Security
Payload

IPSec Security Policy

IKE
The Internet Key Exchange
IPSec provides security in three situations: Host-to-host, host-to-gateway and gateway-to-gateway.
IPsec uses the following protocols to perform various functions:
Authentication Headers (AH) provide connectionless data integrity and data origin
authentication for IP datagrams and provides protection against replay attacks.
Encapsulating Security Payloads (ESP) provide confidentiality, data-origin authentication,
connectionless integrity, an anti-replay service (a form of partial sequence integrity), and
limited traffic-flow confidentiality.
Security Associations (SA) provide the bundle of algorithms and data that provide the
parameters necessary for AH and/or ESP operations. The Internet Security Association and
Key Management Protocol (ISAKMP) provides a framework for authentication and key
exchange, with actual authenticated keying material provided either by manual configuration
with pre-shared keys, Internet Key Exchange (IKE and IKEv2), Kerberized Internet
Negotiation of Keys (KINK), or IPSECKEY DNS records.
1.3.1 Authentication Header
The authentication header provides support for data integrity and authentication of IP packets. The
data integrity feature ensures that undetected modification to the content of a packet in transit is not
possible. The authentication feature enables an end system or network device to authenticate the

user or application and filter traffic accordingly; it also prevents the address spoofing attacks
observed in today's Internet.
IPSec Authentication Header

Authentication is based on the use of a Message Authentication Code (MAC); hence the two parties
must share a secret key. The authentication header consists of the following fields :
Next Header (8 bits): This field identifies the type of header immediately following this
header.
Payload Length (8 bits): This field gives the length of the authentication header in 32-bit
words, minus 2. For example, the default length of the authentication data field is 96 bits, or
three 32-bit words. With a three-word fixed header, there are a total of six words in the
header, and the Payload Length field has a value of 4.
Reserved (16 bits): This field is reserved for future use.
Security Parameters Index (32 bits): This field identifies a security association.
Sequence Number (32 bits): This field contains a monotonically increasing counter value.
Authentication Data (variable): This variable-length field (must be an integral number of
32-bit words) contains the Integrity Check Value (ICV), or MAC, for this packet.
1.3.2 Encapsulating Security Payload
The encapsulating security payload provides confidentiality service, including confidentiality of
message contents and limited traffic flow confidentiality. As an optional feature, ESP can also
provide the same authentication services as AH.

IPSec ESP Format

Figure shows the format of an ESP packet. It contains the following fields:

Security Parameters Index (32bits): Identifies a security association

Sequence Number (32 bits): A monotonically increasing counter value.

Payload Data (variable): A transport-level segment (transport mode) or IP packet (tunnel


mode) that is protected by encryption.

Padding (0-255 bytes): Extra bytes that may be required if the encryption algorithm requires
the plaintext to be a multiple of some number of octets

Pad Length (8 bits): Indicates the number of pad bytes immediately preceding this field

Next Header (8 bits): Identifies the type of data contained in the payload data field by
identifying the first header in that payload (for example, an extension header in IPv6, or an
upper-layer protocol such as TCP)

Authentication Data (variable): A variable-length field (must be an integral number of 32-bit


words) that contains the integrity check value computed over the ESP packet minus the
Authentication Data field

Transport and Tunnel Modes


Both AH and ESP support two modes of use: transport and tunnel mode.
Transport Mode
Transport mode provides protection primarily for upper-layer protocols. That is, transport mode
protection extends to the payload of an IP packet. Examples include a TCP or UDP segment, or an
Internet Control Message Protocol (ICMP) packet, all of which operate directly above IP in a host
protocol stack. When a host runs AH or ESP over IPv4, the payload is the data that normally follow
the IP header. For IPv6, the payload is the data that normally follow both the IP header and any

IPv6 extensions header that are present, with the possible exception of the destination options
header, which may be included in the protection.
ESP in transport mode encrypts and optionally authenticates the IP payload but not the IP header.
AH in transport mode authenticates the IP payload and selected portions of the IP header.
Tunnel Mode
Tunnel mode provides protection to the entire IP packet. To achieve this, after the AH or ESP fields
are added to the IP packet, the entire packet plus security fields is treated as the payload of the new
outer IP packet with a new outer IP header. The entire original or inner packet travels through a
tunnel from one point of an IP network to another no routers along the way are able to examine the
inner IP header .because the original packet is encapsulated the new larger packet may not have
totally different source and destination address adding to the security
ESP in tunnel mode encrypts and optionally authenticates the entire inner IP packet, including the
inner IP header. AH in tunnel mode authenticates the entire inner IP packet and selected portions of
the outer IP header.

AH

ESP
ESP with Authentication

Transport Mode SA
Authenticates IP payload and
selected portions of IP header
and IPv6 extension headers
Encrypts IP payload and any
IPv6 extension header
Encrypts IP payload and any
IPv6 extension header

Tunnel Mode SA
Authenticates entire inner IP
packet plus selected portions of
outer IP header
Encrypts inner IP packet
Encrypts inner IP packet
Authenticates inner IP packet

Authenticates IP payload but no


IP header
Key Management:
The key management portion of IPSec involves the determination and distribution of the secret
keys. A typical requirement is four keys for communication between two applications: transmit and
receive pairs for both AH and ESP. The IPSec architecture document mandates support for two
types of key management.
Manual: A system administrator manually configure each system with its own keys and with the
keys of the other communicating systems. This is practically for small, relatively static
environments.

Automated: An automated system enables the on demand creation of keys for SAs and facilities
the use of keys in a large distributed system with an evolving configuration.

1.3.3 Security Associations


A key concept that appears in both the authentication and confidentiality mechanisms for IP is the
Security Association (SA). An association is a one-way relationship between a sender and a
receiver that affords security services to the traffic carried on it. If a peer relationship is needed, for
two-way secure exchange, then two security associations are required. Security services are
afforded to an SA for the use of AH or ESP, but not both. A security association is uniquely
identified by three parameters:
Security Parameters Index (SPI): The SPI assigns a bit string to this SA that has local
significance only. The SPI is carried in AH and ESP headers to enable the receiving system
to select the SA under which a received packet will be processed.
IP destination address : Currently, only unicast addresses are allowed; this is the address of
the destination endpoint of the SA, which may be an end-user system or a network system
such as a firewall or router.
Security protocol identifier : This indicates whether the association is an AH or ESP
security association.
1.4 Benefits of IP Security
The benefits of IP Security include:
When IPSec is implemented in a firewall or router, it provides strong security that can be
applied to all traffic crossing the perimeter. Traffic within a company or workgroup does not
incur the overhead of security-related processing.
IPSec is below the transport layer (TCP, UDP), so is transparent to applications. There is no
need to change software on a user or server system when IPSec is implemented in the
firewall or router. Even if IPSec is implemented in end systems, upper layer software,
including applications, is not affected.
IPSec can be transparent to end users. There is no need to train users on security
mechanisms, issue keying material on a per-user basis, or revoke keying material when users
leave the organization.
IPSec can provide security for individual users if needed. This feature is useful for offsite
workers and also for setting up a secure virtual subnetwork within an organization for
sensitive applications.

1.5 Applications of IPSEC


1. Secure branch office connectivity over the Internet: A company can build a secure virtual
private network over the Internet or over a public WAN. This enables a business to rely
heavily on the Internet and reduce its need for private networks, saving costs and network
management overhead.
2. Secure remote access over the Internet: An end user whose system is equipped with IP
security protocols can make a local call to an Internet Service Provider (ISP) and gain secure
access to a company network. This reduces the cost of toll charges for traveling employees
and telecommuters.
3. Establishment of extranet and intranet connectivity with partners: IPSec can be used to
secure communication with other organizations, ensuring authentication and confidentiality
and providing a key exchange mechanism.
4. Enhancement of electronic commerce security: Most efforts to date to secure electronic
commerce on the Internet have relied upon securing Web traffic with SSL since that is
commonly found in Web browsers and is easy to set up and run. There are new proposals
that may utilize IPSec for electronic commerce.

1.6 Conclusion
IP Security importance is growing, but unfortunately its operation imposes a significant burden on
the encrypting devices. Furthermore, certain applications may suffer from the increase in latency
(i.e., the time required to pass through an IPSec network device) due to the extra processing.
Finally, at a time when network security is increasingly vital, IPSec makes it easy for network
managers to provide a strong layer of protection to their organization's information resources.

1.7 Recommendation
The standard Internet communication protocol is completely unprotected, allowing hosts to inspect
or modify data in transit. Today's Internet is primarily comprised of

public, un-trusted, and

unreliable IP networks because of this inherent lack of security, the Internet is subject to various
types of threats. Adding IPSec to the system will resolve this limitation by providing strong
encryption, integrity, authentication and replay protection.

1.8 Bibliography

1.
2.
3.
4.
5.
6.
7.

IP Security - The Internet Protocol Journal - Volume 3, No. 1 by William Stallings


https://technet.microsoft.com/en-us/library/cc959511.aspx
Network security essential by William stallings
http://en.wikipedia.org/wiki/IPsec
http://www.itd.nrl.navy.mil/
http://ezine.daemonnews.org/199812/security.html
http://www.cisco.com/en/US/tech/tk583/tk372/technologies_tech_note09186a00800
94203.shtml
8. http://support.microsoft.com/?kbid=884909
9. http://support.microsoft.com/kb/818043/en-us
10. http://www.microsoft.com/windows2000/technologies/communications/ipsec/default
.mspx