Scribd
Upload
313 views

Cryptography and Network Security: Fourth Edition by William Stallings

The document discusses web security and protocols for secure communication over the web, including SSL/TLS and SET. SSL/TLS provides transport layer security using encryption, message authentication codes, and authentication between clients and servers. SET defines security protocols and formats for secure electronic credit card transactions over the internet using digital signatures and certificates to authenticate parties and ensure integrity and privacy of transaction information.

Uploaded by

kstu1112
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
313 views

Cryptography and Network Security: Fourth Edition by William Stallings

The document discusses web security and protocols for secure communication over the web, including SSL/TLS and SET. SSL/TLS provides transport layer security using encryption, message authentication codes, and authentication between clients and servers. SET defines security protocols and formats for secure electronic credit card transactions over the internet using digital signatures and certificates to authenticate parties and ensure integrity and privacy of transaction information.

Uploaded by

kstu1112
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/ 24

Cryptography and Network

Security
Chapter 17
Fourth Edition
by William Stallings
Chapter 17 – Web Security

Use your mentality


Wake up to reality
—From the song, "I've Got You
under My Skin“ by Cole Porter
Web Security
 Web now widely used by business,
government, individuals
 but Internet & Web are vulnerable
 have a variety of threats
 integrity
 confidentiality
 denial of service
 authentication
 need added security mechanisms
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 connection
 a transient, peer-to-peer, communications
link
 associated with 1 SSL session
 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 Record Protocol Services
 message integrity
 using a MAC with shared secret key
 similar to HMAC but with different padding
 confidentiality
 using symmetric encryption with a shared
secret key defined by Handshake Protocol
 AES, IDEA, RC2-40, DES-40, DES, 3DES,
Fortezza, RC4-40, RC4-128
 message is compressed before encryption
SSL Record Protocol Operation
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
 fatal: unexpected message, bad record mac,
decompression failure, handshake failure, illegal
parameter
 warning: 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
1. Establish Security Capabilities
2. Server Authentication and Key Exchange
3. Client Authentication and Key Exchange
4. 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 types & negotiations
 changes in crypto computations & 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
 secure communications amongst parties
 trust from use of X.509v3 certificates
 privacy by restricted info to those who need it
SET Components
SET Transaction
1. customer opens account
2. customer receives a certificate
3. merchants have their own certificates
4. customer places an order
5. merchant is verified
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
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
DS=E(PRc, [H(H(PI)||H(OI))])
SET Purchase Request
 SET purchase request exchange consists of
four messages
1. Initiate Request - get certificates
2. Initiate Response - signed response
3. Purchase Request - of OI & PI
4. Purchase Response - ack order
Purchase Request – Customer
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
Purchase Request – Merchant
Payment Gateway Authorization
1. verifies all certificates
2. decrypts digital envelope of authorization block to
obtain symmetric key & then decrypts authorization
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
protocols

You might also like