Scribd
Upload
83 views37 pages

Web Security: Course: Network Security by DR Adnan Nadeem

This document discusses web security and Secure Sockets Layer (SSL). It provides an overview of web security threats including integrity, confidentiality and denial of service attacks. SSL uses encryption and message authentication codes to provide security for web traffic. It also describes Secure Electronic Transactions (SET) which specifies security protocols for online credit card payments using digital signatures and certificates to authenticate parties and ensure message integrity and privacy.

Uploaded by

Katherine Genail
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
83 views37 pages

Web Security: Course: Network Security by DR Adnan Nadeem

This document discusses web security and Secure Sockets Layer (SSL). It provides an overview of web security threats including integrity, confidentiality and denial of service attacks. SSL uses encryption and message authentication codes to provide security for web traffic. It also describes Secure Electronic Transactions (SET) which specifies security protocols for online credit card payments using digital signatures and certificates to authenticate parties and ensure message integrity and privacy.

Uploaded by

Katherine Genail
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 37

Course: Network Security by Dr Adnan Nadeem

Web Security

This lecture slides are from Network Security Essential , William Stallings

Web Security
Some fundamental questions .. - What is web??? - Protocol ? - Web Security threats ?

Web Security Threats


Threats can be analyzed in various ways Passive & Actives Passive - eavesdropping traffic b/w browser & server Active - altering messages in transit - altering information on web site - impersonating another user

Web Security Threats


Threats based on location - threats at web server

- threats at web browser - threats related to network traffic b/w browser & web server

Web Security thrests


In general web vulnerable to following threats

integrity confidentiality denial of service authentication


need added security mechanisms

Web Security thrests


A comparison of web security threats[RUB197]

SSL (Secure Socket Layer)

SSL (Secure Socket Layer)


transport layer security service originally developed by Netscape version 3 designed with public input subsequently became Internet standard known as TLS (Transport Layer Security) uses TCP to provide a reliable end-to-end service SSL has two layers of protocols

SSL Architecture

SSL Architecture
SSL session
an association between client & server created by the Handshake Protocol define a set of cryptographic parameters may be shared by multiple SSL connections

SSL connection
a transient, peer-to-peer, communications link associated with 1 SSL session

SSL Architecture
Session state
Session id, peer certificate Compression method Cipher spec , encryption & hash algorithm etc.

Connection state
Server /client write keys Byte sequence, sequence no. Initialization vector etc

SSL Record Protocol


SSL record protocol provide two services confidentiality
using symmetric encryption with a shared secret key defined by Handshake Protocol encryption algo IDEA, RC2-40, DES, 3DES, Fortezza message is compressed before encryption

message integrity
using a MAC with shared secret key similar to HMAC but with different padding

SSL Record Protocol operations

SSL Record Protocol operations


Fragment upper layer messages into block of 214 bytes MAC is calculated using shared secret key Encrypt using symmetric encryption Append header consists of content type, version, compress length

SSL Change Cipher Spec Protocol


one of 3 SSL specific protocols which use the SSL Record protocol a single message causes pending state to become current hence updating the cipher suite in use

SSL Alert Protocol


conveys SSL-related alerts to peer entity severity
warning or fatal

specific alert
unexpected message, bad record mac, decompression failure, handshake failure, illegal parameter close notify, no certificate, bad certificate, unsupported certificate, certificate revoked, certificate expired, certificate unknown

compressed & encrypted like all SSL data

SSL Handshake Protocol


allows server & client to:
authenticate each other to negotiate encryption & MAC algorithms to negotiate cryptographic keys to be used

comprises a series of messages in phases


Establish Security Capabilities Server Authentication and Key Exchange Client Authentication and Key Exchange Finish

SSL Handshake Protocol

TLS (Transport Layer Security)


IETF standard RFC 2246 similar to SSLv3 with minor differences
in record format version number uses HMAC for MAC a pseudo-random function expands secrets has additional alert codes some changes in supported ciphers changes in certificate negotiations changes in use of padding

Secure Electronic Transactions (SET)


open encryption & security specification to protect Internet credit card transactions developed in 1996 by Mastercard, Visa etc not a payment system rather a set of security protocols & formats

Participants in Electronic transaction


Cardholder Merchant Issuer (e.g. bank ) Acquirer Payment gateway (function of acquirer or third party) Certificate Authority Now we can set the security requirements

Key features of SET


Confidentiality of information -cardholder account & payment info Integrity of data -payment info & instruction, personal data Card holder account authentication Merchant authentication

SET Components

SET Transaction
1. customer opens account 2. customer receives a certificate 3. merchants have their own certificates (2 keys
signing message & key exchange)

4. customer places an order 5. merchant is verified (customer verify merchants


certificate)

6. order and payment are sent 7. merchant requests payment authorization 8. merchant confirms order 9. merchant provides goods or service 10. merchant requests payment to payment gateway

SET services
SET provide three major services Secure communication channel among all parties during transaction Provide trust by use of X.509v3 certificate Ensures privacy of participants

Dual Signature
customer creates dual messages
order information (OI) for merchant payment information (PI) for bank

neither party needs details of other but must know they are linked use a dual signature for this
signed concatenated hashes of OI & PI

Dual signature construction

SET transaction type

Major SET Transactions


Some of the major transactions in SET are as follows Purchase Request Payment Authorization Payment Capture

Purchase Request Customer


It consists of 4 messages: Initiate Request, Initiate Response, Purchase request & purchase response
Initiate request and response ensures customer and merchants verifies certificates other details

completes order and sends the purchase request

Purchase Request Customer

Purchase Request Merchant

Purchase Request Merchant


1. verifies cardholder certificates using CA sigs 2. verifies dual signature using customer's public signature key to ensure order has not been tampered with in transit & that it was signed using cardholder's private signature key 3. processes order and forwards the payment information to the payment gateway for authorization (described later) 4. sends a purchase response to cardholder

Payment Authorization
Merchant sends an authorization request to payment gateway with Purchase related information (customer)
PI, OI, dual signature, digital envelope

Authorization-related information (merchant)


authorization block, digital envelope

Certificates
card holder & merchant signature key, merchant key exchange certificate

Payment Gateway Authorization


1. verifies all certificates 2. decrypts digital envelope of authorization block to obtain symmetric key & then decrypts the block 3. verifies merchant's signature on authorization block 4. decrypts digital envelope of payment block to obtain symmetric key & then decrypts payment block 5. verifies dual signature on payment block 6. verifies that transaction ID received from merchant matches that in PI received (indirectly) from customer 7. requests & receives an authorization from issuer 8. sends authorization response back to merchant

Payment Capture
merchant sends payment gateway a payment capture request gateway checks request then causes funds to be transferred to merchants account notifies merchant using capture response

Summary
have considered:
need for web security SSL/TLS transport layer security protocols SET secure credit card payment method

You might also like