Unit 4 - Information Security - WWW - Rgpvnotes.in
Unit 4 - Information Security - WWW - Rgpvnotes.in
The revenue we generate from the ads we show on our website and app
funds our services. The generated revenue helps us prepare new notes
and improve the quality of existing study materials, which are
available on our website and mobile app.
If you don't use our website and app directly, it will hurt our revenue,
and we might not be able to run the services and have to close them.
So, it is a humble request for all to stop sharing the study material we
provide on various apps. Please share the website's URL instead.
Downloaded from www.rgpvnotes.in, whatsapp: 8989595022
Subject Notes
Subject Name: Information Security Subject Code: IT 801
Syllabus:
Authentication Applications, Kerberos, X.509 Authentication Service, Public key infrastructure; Electronic
Mail Security:Pretty Good Privacy; IP Security: IP Security Overview, Architecture, Authentication header,
encapsulating security payload, Key management; Web Security: Web security considerations, Secure
Socket Layer and Transport layer Security,Secure Electronic Transaction.
__________________________________________________________________________________________
Course Objective: The objective of this course is to familiarize the students with the fundamentals
of information security and the methods used in protecting both the information present in computer storage
as well as information traveling over computer networks.
__________________________________________________________________________________________
__ Course Outcome : Understand principles of web security to secure network by monitoring and analyzing
the nature of attacks and design/develop security architecture for an organization
UNIT-IV
Authentication Applications
Authontication applications provide a centralized authentication server whose function is to authenticate
users to servers and servers to users. Kerberos provide centralized authentication it relies exclusively on
conventional encryption, making no use of public-key encryption.
The following are the requirements for Authentication applications :
Secure: A network eavesdropper should not be able to obtain the necessary information to impersonate
a user. More generally, Kerberos should be strong enough that a potential opponent does not find it to be
the weak link.
Reliable: For all services that rely on Kerberos for access control, lack of availability of the Kerberos service
means lack of availability of the supported services. Hence, Kerberos should be highly reliable and
should employ a distributed server architecture, with one system able to back up another.
Kerberos:
Kerberos is an authentication protocol for client/server applications. This protocol relies on a combination of
private key encryption and access tickets to safely verify user identities.
The main reasons for adopting Kerberos are:
X.509 is based on the use of public-key cryptography and digital signatures. The standard does not dictate the
use of a specific algorithm but recommends RSA. The digital signature scheme is assumed to require the use of
a hash function. Again, the standard does not dictate a specific hash algorithm. The 1988 recommendation
included the description of a recommended hash algorithm; this algorithm has since been shown to be
insecure and was dropped from the 1993 recommendation.
4. Enter into an agreement with a company to provide a fully compatible, low cost commercial version
of PGP.
PGP has grown explosively and is now widely used. A number of reasons can be cited for this growth.
It is available free worldwide in versions that run on a variety of platform.
It is based on algorithms that have survived extensive public review and are considered extremely
secure. e.g., RSA, DSS and Diffie Hellman for public key encryption CAST-128, IDEA and 3DES for
conventional encryption SHA-1 for hash coding.
It has a wide range of applicability. It was not developed by, nor it is controlled by, any governmental
or standards organization.
Internet Protocol Security (IPSec) is a framework of open standards for ensuring private, secure
communications over Internet Protocol (IP) networks, through the use of cryptographic security services. IPSec
is a suite of cryptography-based protection services and security protocols. Because it requires no changes to
programs or protocols, you can easily deploy IPSec for existing networks. The driving force for the acceptance
and deployment of secure IP is the need for business and government users to connect their private WAN/
LAN infrastructure to the Internet for providing access to Internet services and use of the Internet as a
component of the WAN transport system. As we all know, users need to isolate their networks and at the
same time send and receive traffic over the Internet. The authentication and privacy mechanisms of secure IP
provide the basis for a security strategy for us.
IPsec protects one or more paths between a pair of hosts, a pair of security gateways, or a security gateway
and a host. A security gateway is an intermediate device, such as a switch or firewall, that implements IPsec.
Devices that use IPsec to protect a path between them are called peers.
IP Security Architecture
IPSec (IP Security) architecture uses two protocols to secure the traffic or data flow. These protocols are ESP
(Encapsulation Security Payload) and AH (Authentication Header). IPSec Architecture include protocols,
algorithms, DOI, and Key Management. All these components are very important in order to provide the three
main services:
Confidentiality
Authentication
Integirity
IP Authentication header
IP Authentication Header is used to provide connection-less integrity and data origin authentication. There are
two main advantages that Authentication Header provides,
1. Message Integrity – It means, message is not modified while coming from source.
2. Source Authentication –It means, source is exactly source from whom we were expecting data.
When packet is sent from source A to Destination B, it consists of data that we need to send and header which
consist of information regarding packet. Authentication Header verifies origin of data and also payload to
confirm if there has been modification done in between, during transmission between source and destination.
However, in transit, values of some IP header fields might change (like- Hop count, options, extension
headers). So, values of such fields cannot be protected from Authentication header. Authentication header
cannot protect every field of IP header. It provides protection to fields which are essential to be protected.
Authentication Header :
The question may arise, that how IP header will know that adjacent Extension header is Authentication
Header. Well, there is protocol field in IP Header which tells type of header that is present in packet. So,
protocol field in IP Header should have value of “51” in order to detect Authentication Header.
Key management
In cryptography it is a very tedious task to distribute the public and private key between sender and receiver.
If key is known to the third party (forger/eavesdropper) then the whole security mechanism becomes
worthless. So, there comes the need to secure the exchange of keys.
Distribution of Public Key:
Public key can be distributed in 4 ways: Public announcement, Publicly available directory, Public-key
authority, and Public-key certificates. These are explained as below:
1. Public Announcement:
Here the public key is broadcasted to everyone. Major weakness of this method is forgery. Anyone can
create a key claiming to be someone else and broadcast it. Until forgery is discovered can masquerade
as claimed user.
2. Publicly Available Directory:
In this type, the public key is stored at a public directory. Directories are trusted here, with properties
like Participant Registration, access and allow to modify values at any time, contains entries like {name,
public-key}.Directories can be accessed electronically still vulnerable to forgery or tampering.
3. Public Key Authority:
It is similar to the directory but, improve security by tightening control over distribution of keys from
directory. It requires users to know public key for the directory. Whenever the keys are needed, a real-
time access to directory is made by the user to obtain any desired public key securely.
4. Public Certification:
This time authority provides a certificate (which binds identity to the public key) to allow key exchange
without real-time access to the public authority each time. The certificate is accompanied with some
other info such as period of validity, rights of use etc. All of this content is signed by the trusted Public-
Key or Certificate Authority (CA) and it can be verified by anyone possessing the authority’s public-key.
Alert protocol
Encryption:
TLS/SSL can help to secure transmitted data using encryption.
Interoperability:
TLS/SSL works with most web browsers, including Microsoft Internet Explorer and on most operating
systems and web servers.
Algorithm flexibility:
TLS/SSL provides operations for authentication mechanism, encryption algorithms and hashing
algorithm that are used during the secure session.
Ease of Deployment:
Many applications TLS/SSL temporarily on a windows server 2003 operating systems.
Ease of Use:
Because we implement TLS/SSL beneath the application layer, most of its operations are completely
invisible to client.
Requirements in SET :
SET protocol has some requirements to meet, some of the important requirements are :
It has to provide mutual authentication i.e., customer (or cardholder) authentication by confirming if
the customer is intended user or not and merchant authentication.
It has to keep the PI (Payment Information) and OI (Order Information) confidential by appropriate
encryptions.
It has to be resistive against message modifications i.e., no changes should be allowed in the content
being transmitted.
SET also needs to provide interoperability and make use of best security mechanisms.