E-Commerce Security and Authentication Details Jerry Post

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

CP3397 ECommerce.
SECURITY IN E-COMMERCE VARNA FREE UNIVERSITY Prof. Teodora Bakardjieva.
1 MIS 2000 Class 22 System Security Update: Winter 2015.
Crime and Security in the Networked Economy Part 4.
By: Mr Hashem Alaidaros MIS 326 Lecture 6 Title: E-Business Security.
1 Supplement III: Security Controls What security services should network systems provide? Confidentiality Access Control Integrity Non-repudiation Authentication.
1 Pertemuan 12 Authentication, Encryption, Digital Payments, and Digital Money Matakuliah: M0284/Teknologi & Infrastruktur E-Business Tahun: 2005 Versi:
Chapter 13 Paying Via The Net. Agenda Digital Payment Requirements Fraud Detection Online Payment Methods Online Payment Types The Future Payment.
Public Key Infrastructure (PKI) Providing secure communications and authentication over an open network.
Client/Server Computing Model of computing in which very powerful personal computers (clients) are connected in a network with one or more server computers.
Secure communications Week 10 – Lecture 2. To summarise yesterday Security is a system issue Technology and security specialists are part of the system.
Apr 22, 2003Mårten Trolin1 Agenda Course high-lights – Symmetric and asymmetric cryptography – Digital signatures and MACs – Certificates – Protocols Interactive.
Computer and Network Security. Introduction Internet security –Consumers entering highly confidential information –Number of security attacks increasing.
Chapter 9 - Control in Computerized Environment ATG 383 – Spring 2002.
1 Applications of Computers Lecture-3 2 E-Commerce 4 Almost all major companies have their homes on the web, mainly for advertising 4 Companies were.
Business Data Communications, Fourth Edition Chapter 10: Network Security.
Elias M. Awad Third Edition ELECTRONIC COMMERCE From Vision to Fulfillment 13-1© 2007 Prentice-Hall, Inc ELC 200 Day 23.
Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE CSci530: Computer Security Systems Authentication.
Introduction to Public Key Infrastructure (PKI) Office of Information Security The University of Texas at Brownsville & Texas Southmost College.
Security on the Internet Jan Damsgaard Dept. of Informatics Copenhagen Business School
Electronic Commerce. On-line ordering---an e-commerce application On-line ordering assumes that: A company publishes its catalog on the Internet; Customers.
“Electronic Payment System”
 2001 Prentice Hall, Inc. All rights reserved. Chapter 7 – Computer and Network Security Outline 7.1Introduction 7.2Ancient Ciphers to Modern Cryptosystems.
Payment Systems for Electronic Commerce
Alter – Information Systems 4th ed. © 2002 Prentice Hall 1 E-Business Security.
Privacy and Encryption The threat of privacy due to the sale of sensitive personal information on the internet Definition of anonymity and how it is abused.
Traditional and Electronic Payment Methods Chapter 3.
Digital Certificates. What is a Digital Certificate? A digital certificate is the equivalent of your business card in the e-commerce world. It says who.
CSCI 6962: Server-side Design and Programming
Supporting Technologies III: Security 11/16 Lecture Notes.
E-business Security Dana Vasiloaica Institute of Technology Sligo 22 April 2006.
Lecture 12 Electronic Business (MGT-485). Recap – Lecture 11 E-Commerce Security Environment Security Threats in E-commerce Technology Solutions.
Digital Cash By Gaurav Shetty. Agenda Introduction. Introduction. Working. Working. Desired Properties. Desired Properties. Protocols for Digital Cash.
Chapter 14 Encryption: A Matter Of Trust. Awad –Electronic Commerce 2/e © 2004 Pearson Prentice Hall 2 OBJECTIVES What is Encryption? Basic Cryptographic.
PART THREE E-commerce in Action Norton University E-commerce in Action.
MOBILE DEVICE SECURITY. WHAT IS MOBILE DEVICE SECURITY? Mobile Devices  Smartphones  Laptops  Tablets  USB Memory  Portable Media Player  Handheld.
1 An Introduction to Electronic Commerce Electronic commerce: conducting business activities (e.g., distribution, buying, selling, marketing, and servicing.
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.
BUSINESS B1 Information Security.
Electronic Payment Systems. How do we make an electronic payment? Credit and debit cards Smart cards Electronic cash (digital cash) Electronic wallets.
E-Commerce Security Technologies : Theft of credit card numbers Denial of service attacks (System not availability ) Consumer privacy (Confidentiality.
E-commerce Vocabulary Terms. E-commerce Buying and selling of goods, services, or information via World Wide Web, , or other pathways on the Internet.
E-commerce Vocabulary Terms By: Laura Kinchen. Buying and selling of goods, services, or information via World Wide Web, , or other pathways on the.
Traditional and Electronic Payment Methods Chapter 3.
Protecting Internet Communications: Encryption  Encryption: Process of transforming plain text or data into cipher text that cannot be read by anyone.
Cryptography, Authentication and Digital Signatures
E-Commerce Security Professor: Morteza Anvari Student: Xiaoli Li Student ID: March 10, 2001.
Security Protocols and E-commerce University of Palestine Eng. Wisam Zaqoot April 2010 ITSS 4201 Internet Insurance and Information Hiding.
ECE Lecture 1 Security Services.
System Security Chapter no 16. Computer Security Computer security is concerned with taking care of hardware, Software and data The cost of creating data.
Types of Electronic Infection
Authentication 3: On The Internet. 2 Readings URL attacks
Customer Interface for wuw.com 1.Context. Customer Interface for wuw.com 2. Content Our web-site can be classified as an service-dominant website. 3.
Advanced Database Course (ESED5204) Eng. Hanan Alyazji University of Palestine Software Engineering Department.
1 Network and E-commerce Security Nungky Awang Chandra Fasilkom Mercu Buana University.
Traditional Security Issues Confidentiality –Prevent unauthorized access or reading of information Integrity –Insure that writing or operations are allowed.
OBJECTIVES  To understand the concept of Electronic Payment System and its security services.  To bring out solution in the form of applications to.
CIS 325: Data Communications1 Chapter Seventeen Network Security.
© Copyright 2009 SSLPost 01. © Copyright 2009 SSLPost 02 a recipient is sent an encrypted that contains data specific to that recipient the data.
Vijay V Vijayakumar.  Implementations  Server Side Security  Transmission Security  Client Side Security  ATM’s.
Electronic Banking & Security Electronic Banking & Security.
Information Systems Design and Development Security Precautions Computing Science.
BY GAWARE S.R. DEPT.OF COMP.SCI
Electronic Payment Security Technologies
Presentation transcript:

E-Commerce Security and Authentication Details Jerry Post Westgate Management Development Center Eberhardt School of Business University of the Pacific

E-Commerce Transaction Issues Customer Perspective Assurance of delivery Product specification Price Quantity Accounting and auditing Anonymity (occasional) Privacy Merchant Perspective Assurance of payment Validity of orders, non-repudiation Accounting and auditing Customer relationship management (CRM) Government Perspective Financial statements Taxable transactions Identify and track fraud Track money (drugs, terrorists, etc.)

E-Commerce Security Issues Unauthorized changes to site Unauthorized theft of data (e.g., credit cards) Interception of transmission Stolen credit cards: identity of consumer Fraudulent sites, spoofing: identity of merchant Physical site threats (fire, etc.) Employee/Insider threats

E-Commerce Threat Points Intercept or change data False Site Fraudulent merchant False consumer Stolen card Purchase choice Credit Card data Merchant Server Outside attack on server Insider fraud on purchases or sales Customer Stolen shipments Products

Encryption Single key encryption Data Encryption Standard (DES) DES Plain text message Single key encryption Data Encryption Standard (DES) IBM 1960s 56-bit Brute force attack RSA contest: < 24 hours in 1999 Key management and distribution is a major problem Algorithm is fast Encrypted transmissions are always slower—more random data DES Key: 9837362 Encrypted text Single key: e.g., DES Encrypted text DES Key: 9837362 Plain text message

Dual-key Encryption Alice Bob Message Message Encrypted Public Keys Private Key 13 Use Bob’s Private key Private Key 37 Use Bob’s Public key Alice sends message to Bob that only he can read. Brute force attack prevented by length of key: 40 digits is too small, standard is 128 digits.

Dual key: Authentication Message Transmission Message Encrypt+T+M Alice Encrypt+M Encrypt+T Private Key 13 Bob Use Alice’s Private key Public Keys Alice 29 Bob 17 Private Key 37 Use Bob’s Private key Use Alice’s Public key Use Bob’s Public key Bob sends message to Alice: His key guarantees it came from him. Her key prevents anyone else from reading message.

Digital Signature 5983 Plain Text Order Message hash (CRC check bytes) Encrypt hash with private key Signature is unique to document, cannot be reused Can be time-stamped Encrypt order with merchant’s public key Transmit It cannot be read or changed It can be lost or deleted Recipient decrypts document and verifies authenticity 5983 Simple hash: 5+9+8+3 = 25 Better: row hash And column hash Best: Cyclic Redundancy Check: polynomial

Encryption Solutions Rivest-Shamir-Adelman (RSA: company) U.S. patent on common dual-key method (expires soon) Used by browsers and most security systems Correctly implemented, it solves most problems Transmission cannot be intercepted or changed Customer is authenticated Order cannot be repudiated or altered If merchant re-encrypts and stores data, it cannot be stolen

Dual-Key Authentication Issues How distribute and verify the public keys? People are authenticated based on public key. How stop someone from registering public key in your name? How validate the public key server? Spoofing: false server or key list Alice 13 Bob 17 Impersonation

Digital Certificates Almost any server can generate digital keys Can use it “in-house” to reduce costs But how do you know which servers to trust? Some government agencies generate certificates, but not for commercial use. Now, one commercial company: Verisign Merchant certificate is “required” for encryption Consumers can purchase certificates Verify identity Merchants: DUNS number and some options Consumers: levels, Notary public; but no one registers

User Identification Merchant authentication Consumer authentication Merchants generally register with Verisign Merchants almost always register with credit card, merchant bank Consumers are protected by credit card rules Consumer authentication No one registers with Verisign All authentication is handled by credit card Can verify card number, expiration date, address online Can get online test of cards reported stolen or invalid

Consumer Authentication Purchases Credit card is the best we can do right now Merchant is still at risk International sales are dangerous, so most merchants will not accept them

Individual Identification Username and password Have to find a way to get them to the correct person Have to handle forgotten passwords Could use a billing number, but need to randomize them Credit card Not everyone has a card Some are not willing to give the number SSN Too easily found or forged Restrictions on government use Digital certificate/signature Individuals unwilling to pay Need infrastructure IP Address Not always unique Can be spoofed

Biometrics Many new devices Cost is reasonable ($100-$500) Fingerprint, handprint readers Iris scanners Infrared scanners Cost is reasonable ($100-$500) Hard to use for external identification No standard devices No standard software, authentication scheme

Identity Solution? Determine the level of identification you need for each application Absolute identity (digital signature) Best test of documents (e.g., credit card) Reasonably certain (e.g., billing ID number) Open to public Examples Sales: Best test of documents Car registration (DMV): Absolute identity Check water bill: Reasonably certain

Escrow Keys: Government Developed by the NSA, the federal government tried to force the use of escrow keys for all encryption, but mostly for digital cell phones. Decrypted conversation Escrow keys Judicial or government office Intercept Encrypted conversation Clipper chip in phones

Encryption Issues Transmission speed drops enormously Encryption/decryption takes processor time—can purchase hardware solution: nCipher You must protect the private key, which is hard when someone steals a laptop In a civil suit, you will be forced to decrypt any data requested Federal government actively breaks encryption for criminal cases (when possible) You still have to trust your employees

Security Best Practices Limit access to hardware Physical locks Video monitoring Fire and environment monitors Employee logs / cards Monitor usage Hardware logs Access failures/attacks Software and data usage Background checks Employees Consultants Backups! Encrypt sensitive data Transmissions Storage Assign access rights Protect disposal of data Disaster planning Virus protection Backups Anti-virus software limited value Only run trusted software

Digital Cash Trusted Party Bank Vendor (data) Consumer Conversion to “real” money. Bank NetBill (1) Price, product decryption key, customer code are sent to third party. Digital Cash (A) Consumer purchases a cash value that can be used only once. NetBill (2) Accounts are debited and credited. Product key is sent to customer. Digital Cash (B) “Cash” amount is verified and added to vendor account. Customer chooses product, sends ID or digital cash number. Vendor (data) Consumer

Digital Cash Goals Requirements Lower transaction costs (affordable to $0.25?) Merchant and consumer protection Anonymity, non-traceable Requirements Conversion to/from real world cash Trusted third-party Customer uses digital wallet Some technologies in use today, but limited acceptance by consumers

Secure Electronic Transactions (SET) Current usage is known as Secure Sockets Layer (SSL) Vendor handles security using Verisign Encryption is one-way (consumer to vendor) No authentication SET specifies steps to ensure strong security in entire process SET requires consumers to obtain digital certificates, digital signatures Consumers show limited enthusiasm

Anonymity Computers all have an IP Address Every computer on the Internet must have an IP address (number) so that messages are sent/returned correctly. Many IP addresses can be traced back to a specific user. A few ISPs use dynamic IP assignment, so not always possible to identify exact person. Computer labs and libraries are often open to the public and do not track individual usage Anonymity Servers Church of Scientology dispute—forced server operator in Denmark to release records. Zero-Knowledge in Canada is new with a strong assurance of anonymity: http://www.zeroknowledge.com for $50/year.

Server and Network Monitoring Customer evaluation Web site usability evaluation Load evaluation (time of day, month, etc.) Network performance Security threats

Network & Server Stats: MRTG Free download: http://ee-staff.ethz.ch/~oetiker/

Web Log Analyzer: SurfStats Cost: $90 www.surfstat.com Site activity Clients File/Pages Browsers Referers Errors

Server Monitor (Win 2000) Free, continuous monitoring plus alerts, choose hundreds of variables. Particularly good for monitoring processor and memory.