Network Security and Public Key Infrastructure (PKI)

Slides:



Advertisements
Similar presentations
Chapter 10 Encryption: A Matter of Trust. Awad –Electronic Commerce 1/e © 2002 Prentice Hall 2 OBJECTIVES What is Encryption? Basic Cryptographic Algorithm.
Advertisements

Public Key Infrastructure A Quick Look Inside PKI Technology Investigation Center 3/27/2002.
Cryptography and Network Security
SSL : An Overview Bruhadeshwar Bezawada International Institute of Information Technology, Hyderabad.
SECURITY IN E-COMMERCE VARNA FREE UNIVERSITY Prof. Teodora Bakardjieva.
Grid Security Infrastructure Tutorial Von Welch Distributed Systems Laboratory U. Of Chicago and Argonne National Laboratory.
1 Supplement III: Security Controls What security services should network systems provide? Confidentiality Access Control Integrity Non-repudiation Authentication.
Public Key Infrastructure (PKI) Providing secure communications and authentication over an open network.
16.1 © 2004 Pearson Education, Inc. Exam Planning, Implementing, and Maintaining a Microsoft® Windows® Server 2003 Active Directory Infrastructure.
Part 5:Security Network Security (Access Control, Encryption, Firewalls)
Client/Server Computing Model of computing in which very powerful personal computers (clients) are connected in a network with one or more server computers.
6/4/2015National Digital Certification Agency1 Security Engineering and PKI Applications in Modern Enterprises Mohamed HAMDI National.
EEC 693/793 Special Topics in Electrical Engineering Secure and Dependable Computing Lecture 6 Wenbing Zhao Department of Electrical and Computer Engineering.
Introduction to PKI Seminar What is PKI? Robert Brentrup July 13, 2004.
K. Salah 1 Chapter 31 Security in the Internet. K. Salah 2 Figure 31.5 Position of TLS Transport Layer Security (TLS) was designed to provide security.
BY MUKTADIUR RAHMAN MAY 06, 2010 INTERODUCTION TO CRYPTOGRAPHY.
Secure communications Week 10 – Lecture 2. To summarise yesterday Security is a system issue Technology and security specialists are part of the system.
8-1 What is network security? Confidentiality: only sender, intended receiver should “understand” message contents m sender encrypts message m receiver.
Encryption An Overview. Fundamental problems Internet traffic goes through many networks and routers Many of those networks are broadcast media Sniffing.
Presented by Xiaoping Yu Cryptography and PKI Cosc 513 Operating System Presentation Presented to Dr. Mort Anvari.
Introduction to Public Key Infrastructure (PKI) Office of Information Security The University of Texas at Brownsville & Texas Southmost College.
Chapter 8 Web Security.
Web services security I
Computer Science Public Key Management Lecture 5.
Digital Signature Xiaoyan Guo/ Xiaohang Luo/
CSCI 6962: Server-side Design and Programming
Digital Certificates Public Key Deception Digital Certificates Certificate Authorities Public Key Infrastructures (PKIs)
Chapter 31 Network Security
Lecture 12 Electronic Business (MGT-485). Recap – Lecture 11 E-Commerce Security Environment Security Threats in E-commerce Technology Solutions.
Chapter 14 Encryption: A Matter Of Trust. Awad –Electronic Commerce 2/e © 2004 Pearson Prentice Hall 2 OBJECTIVES What is Encryption? Basic Cryptographic.
SYSTEM ADMINISTRATION Chapter 13 Security Protocols.
Secure Electronic Transaction (SET)
Web Server Administration Chapter 10 Securing the Web Environment.
1 Chapter 9 E- Security. Main security risks 2 (a) Transaction or credit card details stolen in transit. (b) Customer’s credit card details stolen from.
Secure Socket Layer (SSL)
8-1Network Security Chapter 8 roadmap 8.1 What is network security? 8.2 Principles of cryptography 8.3 Message integrity, authentication.
E-Commerce Security Technologies : Theft of credit card numbers Denial of service attacks (System not availability ) Consumer privacy (Confidentiality.
Chapter 37 Network Security. Aspects of Security data integrity – data received should be same as data sent data availability – data should be accessible.
Chapter 9: Using and Managing Keys Security+ Guide to Network Security Fundamentals Second Edition.
Cryptography, Authentication and Digital Signatures
Introduction to Secure Sockets Layer (SSL) Protocol Based on:
E-Commerce Security Professor: Morteza Anvari Student: Xiaoli Li Student ID: March 10, 2001.
©The McGraw-Hill Companies, Inc., 2000© Adapted for use at JMU by Mohamed Aboutabl, 2003Mohamed Aboutabl1 1 Chapter 29 Internet Security.
Chapter 23 Internet Authentication Applications Kerberos Overview Initially developed at MIT Software utility available in both the public domain and.
Cryptography and Network Security (CS435) Part Fourteen (Web Security)
Certificate-Based Operations. Module Objectives By the end of this module participants will be able to: Define how cryptography is used to secure information.
Types of Electronic Infection
23-1 Last time □ P2P □ Security ♦ Intro ♦ Principles of cryptography.
Network Security7-1 CIS3360: Chapter 8: Cryptography Application of Public Cryptography Cliff Zou Spring 2012 TexPoint fonts used in EMF. Read the TexPoint.
1 SSL - Secure Sockets Layer The Internet Engineering Task Force (IETF) standard called Transport Layer Security (TLS) is based on SSL.
Advanced Database Course (ESED5204) Eng. Hanan Alyazji University of Palestine Software Engineering Department.
Upper OSI Layers Natawut Nupairoj, Ph.D. Department of Computer Engineering Chulalongkorn University.
31.1 Chapter 31 Network Security Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
TCP/IP Protocol Suite 1 Chapter 30 Security Credit: most slides from Forouzan, TCP/IP protocol suit.
Security fundamentals Topic 5 Using a Public Key Infrastructure.
Computer and Network Security - Message Digests, Kerberos, PKI –
Chapter 40 Network Security (Access Control, Encryption, Firewalls)
CSCE 715: Network Systems Security Chin-Tser Huang University of South Carolina.
1 Network Security. 2 Security Services Confidentiality: protection of any information from being exposed to unintended entities. –Information content.
Secure Sockets Layer (SSL)
Information Security message M one-way hash fingerprint f = H(M)
Information Security message M one-way hash fingerprint f = H(M)
Message Digest Cryptographic checksum One-way function Relevance
Information Security message M one-way hash fingerprint f = H(M)
The Secure Sockets Layer (SSL) Protocol
Protocol ap1.0: Alice says “I am Alice”
Chapter 8 roadmap 8.1 What is network security?
Presentation transcript:

Network Security and Public Key Infrastructure (PKI) Bill Chu

Introduction to Security Internet environment Information security addresses: Confidentiality E.g. illegal access to secret information Integrity E.g. illegal addition/deletion/modification of data E.g. perform illegal operations E.g. nonrepudiation Availability E.g. Severely load the system so that the system cannot perform normal functions Usability Appropriate use of information

Requirements for Electronic Business Transactions Authentication of transacting partners Am I dealing with the one who claim to be Once authenticated, business evaluations become possible credit history (report), bank verifications Data integrity any change to data are detected by receiver Non-repudiation can not deny if one issued a transaction Confidentiality keep transactions to only transacting partners

How can We Meet these Requirements? Solutions: cryptography-based technologies Cryptography for authentication private key of cryptography is the evident you are who you claim to be you are the only one who has that key data confidentiality data encrypted prevents eavesdrops by others non-repudiation the data is encrypted with your key, you can not deny you did not send it you are the only one who has that encryption key it is typically called encryptedly signed (digital signature) Message digest for data integrity run a “checksum” over the data & encrypt it changing data will be detected by the encrypted “checksum” others can not decrypt the checksum

Cryptography Concept: Secret writing communicating in secret writing prevent others from reading your message Process encrypt messages before send decrypt message after receive secret writing can not be read by others Keys encryption and decryption is private knowledge it is computationally difficult to break encryption/decryption Encryption Decryption “hello” ~!#@$% cleartext ciphertext

Key-based Cryptography Encryption/Decryption with keys computationally difficult without keys Two types private key or symmetric key cryptography one key used for encryption and decryption key has to be kept secret between partners how to distribute the shared private key is a problem public key or asymmetric key cryptography a pair of keys for encryption and decryption each partner has a pair of keys it keeps one key private to itself & publishes another for others to use Encryption Decryption “hello” ~!#@$% cleartext ciphertext key

Digital Signature, non-repudiation Using Cryptography Bob Encryption Decryption “hello” ~!#@$% cleartext ciphertext Private key Alice Alice “I love you” ~!#@$% “I love you” Bob Encryption Decryption cleartext ciphertext cleartext Alice’s private key Allice’s public key Digital Signature, non-repudiation “Meet me at 3” ~!#@$% “Meet me at 3” Alice Bob Encryption Decryption cleartext ciphertext cleartext Bob’s Public key Bob’s private key Confidential message

Cryptographic hash function A hash function is a one-way function (analogous to meat grinder). A cryptographic hash function typically hashes objects of any size to a fixed length hash (e.g. 128 bits) A cryptographic has function has to satisfy the following properties: It is computationally infeasible to find the original object based on the hash result It is computationally infeasible to find two documents that produce the same hash result

Digital Signature and its verification I love you + 67(*% + MD5 + RSA “I love you” ~!#@$% 67Y(*% Send Hash Encription MD5 Allice’s private key Digital signature 67Y(*% “I love you” =? Hash Decription Yes=verification success MD5 Allice’s public key Verification of digital signature

The trust establishment problem In order to verify a signature of Alice we must trust that we know that we have Alice’s public key. Closed trust model: we verify the public keys ourselves, or we know everyone we are dealing with Open trust model: we must deal with people we do not know The Internet is definitely an open world, therefore a closed trust model will not work

Public key infrastructure Have a third trusted party to verify the identity of public keys using signed statements (digital certificates) from the trusted party (certification authority) Have an directory of valid digital certificates so that users can check (analogous to credit card validation)

Digital Certificate A Public-key certificate binds an entity’s (e.g. amazon.com) public key and one or more attributes relating to its identity. Trusted authority Binding process, verification by the trusted authoraty Digital document (digital certificate) as proof Helps key distribution as digital certificates can be transmitted without encryption Fields in a digital certificate: subject name: unique for a CA, however, multiple certificates may be issued to the same entity by a CA subject public key Optional fields Signature of the above. version (1,2,or 3) serial number: unique within a CA signature algorithm id issuer: CA validity period

PKI Basic Components PKI public key certificate or simply certificate an electronic record that binds a public key to an identity of the owner of a public-private key pair, signed by a trusted entity (CA) Certificate Revocation List (CRL) a list of certificates that have been revoked Certification Authority (CA) a trusted entity that issues and revokes public key certificates Registration Authority (RA) an entity trusted by CA to register user identity & associated public key to CA Certificate Repository electronic site that holds certificates & CRLs Relying Party (Certificate user) an entity that uses certificates to know, with certainty, the public key of another entity

PKI policy and practice Certificate policy statements The CA specifies what a give certificate can be used for (e.g. email, secure server) Driver’s License analogy: this license authorizes the holder to operate 4-wheeled vehicles of up to certain size and weight. Certification practice statements Describes the detailed processes/mechanisms used by registration authorities. Driver’s License analogy: types of id accepted, questions for the written test, criterion and mechanism for eye sight test, criterion for road test Cross certification Accepting certificates issued by different CA’s Driver’s License analogy: most state will accept driver’s licenses issued by other states, but additional tests may be necessary, details vary in different states.

Secure Socket Layer (SSL) The client (e.g.SSL inside a browser) chooses a protocol Key exchange algorithm Private key cryptography algorithm Message integrity algorithm Server (e.g. SSL inside a web server) informs the client that it supports the propose protocol Server asserts its identity by sending a digital certificate The client verifies the digital certificate by using public keys of CA’s the client trusts The client then generates a session key and encrypt it with the server’s public key and sends the ciphertext to the server Server decrypts the session key and complete the handshake by sending a message back to the client using the session key for encryption. The client decrypts the messages and is then certain that a secure channel has been established. All data transacted in this session (both directions) are encrypted using the session key

Virtual Private Network SSL/HTTPs provides encrypted communication for web traffic VPN provides an encrypted communication pipe for all network traffic

Intrusion Techniques: Discovery Scanning Target acquisition: map host names, ip addresses Host discovery Port scanning Banner retrieval: types of machines, version information. Vulnerability Scanning: discover known bugs and attacks Exploits NT: obtain user/admin access, NT resource Kit, cover tracks UNIX: obtain root access, root kit, cover tracks Install sniffers, keyboard loggers, acquire access to other parts of the network Spoofing Change data, delete files, steal secrets Dialin and backdoor Social engineering

Summary of Intrusion Techniques Brute force Patience Mis-configurations Out-of-date software versions

Firewalls Characteristics Service control, e.g. no ftp All traffic goes through firewalls Only authorized traffic can go through The firewall itself is immune to penetration Service control, e.g. no ftp direction control user control behavior control (e.g. filter emails, and web addresses) Types of firewalls packet filtering router application level gateway circuit level gateway (prevents end to end TCP connection), e.g. SOCKS

Packet filtering router firewall www.any.com web server Send to port 80 At www.any.com OK Server Client Send to port 670 Send to port 890 Internet Private network

Circuit gateway firewall Server Client Socks lib Socks lib Relay Internet Private network Relay will examine all packets and filter out illegal packets For example, a company’s policy may want to filter out all java applets through the firewall.

Application gateway firewall Server Client App. gateway Internet Private network Application gateway is a proxy server For every application made available through the firewall, there must be a proxy on the application gateway The application gateway forwards requests to the server, it can also do customized filtering of messages

Deterring pranks Install appropriate defensive tools (some of) use files virus scans, detect port scans Intrusion Detection Systems (IDS) Install decoys and deception tools (all.net)

More serious threats Customized virus will evade popular virus scan programs Virus immunology techniques may help, but there is no guarantee! Customized trojans IDS and popular tools are generally ineffective Attack techniques: Be noisy Be quiet Be clever

Denial of service Noisy sync flooding Typical denial of service starts with a hacked account (e.g. AOL surveys!) Synchronized attacks uses multiple staging points, very difficult to detect and deal with.

Best defenses Educate users about password and common sense security precautions Don’t execute active MIME contents Christmas cards etc. Security is a system engineering problem the system is only as secure as its weakest link Clear risk assessment Turn off unwanted services, simplify, simplify and simplify Don’t blindly use defaults! Upgrade software Don’t make information easily available Use biometrics when appropriate User education and more user education

Resources Www.securityfocus.com www.hackernews.com