







Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
The importance of web security, the types of security threats faced when using the Web, and approaches to providing web security. It covers passive and active attacks, SSL and IPsec, and e-mail security. The document also introduces SSL concepts such as SSL sessions and SSL connections.
Typology: Lecture notes
Uploaded on 06/08/2021
5
(1)8 documents
1 / 13
This page cannot be seen from the preview
Don't miss anything!








The World Wide Web is fundamentally a client/server application running over the Internet and TCP/IP intranets. The reason to come up with web security are the following.
using IPsec is that it is transparent to end users and applications and provides a general- purpose solution. Furthermore, IPsec includes a filtering capability so that only selected traffic need incur the overhead of IPsec processing. Another relatively general-purpose solution is to implement security just above TCP (Figure 5.1b). The foremost example of this approach is the Secure Sockets Layer (SSL) and the follow-on Internet standard known as Transport Layer Security (TLS). At this level, there are two implementation choices. For full generality, SSL (or TLS) could be provided as part of the underlying protocol suite and therefore be transparent to applications. Alternatively, SSL can be embedded in specific packages. For example, Netscape and Microsoft Explorer browsers come equipped with SSL, and most Web servers have implemented the protocol. Application-specific security services are embedded within the particular application. Figure 5.1c shows examples of this architecture. The advantage of this approach is that the service can be tailored to the specific needs of a given application.
Between any pair of parties (applications such as HTTP on client and server), there may be multiple secure connections. In theory, there may also be multiple simultaneous sessions between parties, but this feature is not used in practice. There are a number of states associated with each session. Once a session is established, there is a current operating state for both read and write (i.e., receive and send). In addition, during the Handshake Protocol, pending read and write states are created. Upon successful conclusion of the Handshake Protocol, the pending states become the current states. SSL Record Protocol The SSL Record Protocol provides two services for SSL connections:
Next, the compressed message plus the MAC are encrypted using symmetric encryption. Encryption may not increase the content length by more than 1024 bytes, so that the total length may not exceed 2^14 + 2048. The following encryption algorithms are permitted: For stream encryption, the compressed message plus the MAC are encrypted. Note that the MAC is computed before encryption takes place and that the MAC is then encrypted along with the plaintext or compressed plaintext. For block encryption, padding may be added after the MAC prior to encryption. The padding is in the form of a number of padding bytes followed by a one-byte indication of the length of the padding. The total amount of padding is the smallest amount such that the total size of the data to be encrypted (plaintext plus MAC plus padding) is a multiple of the cipher’s block length.
Handshake Protocol The most complex part of SSL is the Handshake Protocol. This protocol allows the server and client to authenticate each other and to negotiate an encryption and MAC algorithm and cryptographic keys to be used to protect data sent in an SSL record. The Handshake Protocol is used before any application data is transmitted. The Handshake Protocol consists of a series of messages exchanged by client and server. Each message has three fields.
Ideally, any organization would want its own private network for communication to ensure security. However, it may be very costly to establish and maintain such private network over geographically dispersed area. It would require to manage complex infrastructure of communication links, routers, DNS, etc. IPsec provides an easy mechanism for implementing Virtual Private Network (VPN) for such organizations. VPN technology allows organization’s inter-office traffic to be sent over public
Internet by encrypting traffic before entering the public Internet and logically separating it from other traffic. Figure 5.3 Virtual Private Network Overview of IPsec The IPsec suite can be considered to have two separate operations, when performed in unison, providing a complete set of security services. These two operations are IPsec Communication and Internet Key Exchange. IPsec Communication It is typically associated with standard IPsec functionality. It involves encapsulation, encryption, and hashing the IP datagrams and handling all packet processes. It is responsible for managing the communication according to the available Security Associations (SAs) established between communicating parties. It uses security protocols such as Authentication Header (AH) and Encapsulated SP (ESP). IPsec communication is not involved in the creation of keys or their management. IPsec communication operation itself is commonly referred to as IPsec. Internet Key Exchange (IKE) IKE is the automatic key management protocol used for IPsec. Technically, key management is not essential for IPsec communication and the keys can be manually managed. However, manual key management is not desirable for large networks. IKE is responsible for creation of keys for IPsec and providing authentication during key establishment process. Though, IPsec can be used for any other key management protocols, IKE is used by default. IKE defines two protocol (Oakley and SKEME) to be used with already defined key management framework Internet Security Association Key Management Protocol (ISAKMP). ISAKMP is not IPsec specific, but provides the framework for creating SAs for any protocol.
some out-of-band mechanism, and IKE (Internet Key Exchange) is a sophisticated mechanism for doing this online. PPTP Point-to-Point Tunneling Protocol (PPTP) is the oldest of the three protocols used in VPNs. It was originally designed as a secure extension to Point-to-Point Protocol (PPP). PPTP works at the data link layer of the OSI model. PPTP offers two different methods of authenticating the user:
Nowadays, e-mail has become very widely used network application. Let’s briefly discuss the email infrastructure before proceeding to know about e-mail security protocols. E-mail Infrastructure The simplest way of sending an e-mail would be sending a message directly from the sender’s machine to the recipient’s machine. In this case, it is essential for both the machines to be running on the network simultaneously.
However, this setup is impractical as users may occasionally connect their machines to the network. Hence, the concept of setting up e-mail servers arrived. In this setup, the mail is sent to a mail server which is permanently available on the network. When the recipient’s machine connects to the network, it reads the mail from the mail server. In general, the e-mail infrastructure consists of a mesh of mail servers, also termed as Message Transfer Agents (MTAs) and client machines running an e-mail program comprising of User Agent (UA) and local MTA. Typically, an e-mail message gets forwarded from its UA, goes through the mesh of MTAs and finally reaches the UA on the recipient’s machine. The protocols used for e-mail are as follows:
1 or MD5. S/MIME specifies the additional MIME type, such as “application/pkcs7-mime”, for data enveloping after encrypting. The whole MIME entity is encrypted and packed into an object. S/MIME has standardized cryptographic message formats (different from PGP). In fact, MIME is extended with some keywords to identify the encrypted and/or signed parts in the message. S/MIME relies on X.509 certificates for public key distribution. It needs top- down hierarchical PKI for certification support. Employability of S/MIME Due to the requirement of a certificate from certification authority for implementation, not all users can take advantage of S/MIME, as some may wish to encrypt a message, with a public/private key pair. For example, without the involvement or administrative overhead of certificates. In practice, although most e-mailing applications implement S/MIME, the certificate enrollment process is complex. Instead PGP support usually requires adding a plug-in and that plug-in comes with all that is needed to manage keys. The Web of Trust is not really used. People exchange their public keys over another medium. Once obtained, they keep a copy of public keys of those with whom e-mails are usually exchanged. One of the schemes, either PGP or S/MIME, is used depending on the environment. A secure eemail communication in a captive network can be provided by adapting to PGP. For e-mail security over Internet, where mails are exchanged with new unknown users very often, S/MIME is considered as a good option.