Given by Roman Markowski at CPS714 Computational Science Information Track on June 2 and June 7 99. Foils prepared July 6 99
Outside Index
Summary of Material
Introduction to Network Security |
E-commerce - definitions, characteristics, requirements |
Security Standards and Protocols |
Public Key Cryptography and Infrastructure |
Secure Electronic Messaging (PGP, S/MIME) |
Payments on the Web, Electronic Commerce |
C2B: SSL and SET Standards |
Organizing Cyber-Store |
B2B: OFX and OBI Standards |
Firewalls |
Computer Crimes, Threats and Attacks |
Outside Index Summary of Material
Roman Markowski |
IS Manager |
Northeast Parallel Architectures Center |
Syracuse University |
CPS 714, June 1999 |
http://www.npac.syr.edu/users/roman/ |
Introduction to Network Security |
E-commerce - definitions, characteristics, requirements |
Security Standards and Protocols |
Public Key Cryptography and Infrastructure |
Secure Electronic Messaging (PGP, S/MIME) |
Payments on the Web, Electronic Commerce |
C2B: SSL and SET Standards |
Organizing Cyber-Store |
B2B: OFX and OBI Standards |
Firewalls |
Computer Crimes, Threats and Attacks |
Security - protection of information as it traverses the network. Security becomes one of the primary concerns when an organization connects its private intranet to the Internet. |
The Internet is open and public by design. There is no guarantee against information ending-up in the wrong hands. |
Protection components:
|
Protection components:
|
There is no such thing as a 100% secure computer system. We can think of security as a triangle with "security", "performance" and "usability" at corners. We cannot be at all corners at the same time |
Security |
Performance |
Usability |
E-commerce is the utilization of computer technology to accept payments and fulfill delivery of products and services via the Internet or private networks. |
The explosive growth of online transactions push some companies into becoming CSP (Commerce Service Providers):OneHost, AT&T, etc. |
Characteristics:
|
Legacy systems (Unix, Windows) |
LANs and WANs (Ethernet, ATM, FDDI; T1, FR) |
Client / Server technology |
Applications (written in C, Java) |
Routers, gateways |
Telecommunication infrastructure |
(Too) many various protocols |
Transparent to the network |
Security; real time alert system; mutual, strong authentication is necessary |
Standard-based |
Scalable to growth |
Auditable; monitoring: clients, servers, network events |
Affordable; User friendly |
Centralized management |
Domestic and Foreign law |
Performance |
Confidentiality |
Integrity |
Authenticity |
Non-Repudiation |
Availability |
Confidentiality ( unauthorized access)
|
Integrity (protects against data tampering)
|
Authenticity (protects against masquerading)
|
Non-Repudiation (protects against denial of being a party to a transaction)
|
Confidentiality
|
Integrity
|
Authenticity
|
Non-Repudiation
|
Availability
|
ITU X.509 - digital certificate (like identity card authorized by Certificate Authority (CA)) |
SSL - Secure Socket Layer |
PAP - Password Authentication Protocol |
CHAP- Challenge Handshake Authentication Protocol |
TACACS - Terminal Access Controller Access-Control System |
RADIUS - Remote Authentication Dial-In User Service |
PKCS - Public Key Cryptography Standards |
PGP - Pretty Good Privacy |
S/MIME - Secure Multipurpose Internet Mail Extension |
PEM - Privacy Enhanced Mail |
IP Sec - IP Security Protocol (IETF); IP Sec addresses the issues of encryption and integrity |
DES - Data Encryption Standard - private key encryption |
DSS - Digital Signature Standard |
SHA -Secure Hash Algorithm |
DSA - Digital Signature Algorithm |
Secure DNS - is designed to stop DNS spoofing |
Microsoft Crypto API |
Intel Common Data Security Architecture |
SET - Secure Electronic Transactions |
IPSEC - network layer security
|
AH |
ESP |
TCP |
HTTP |
FTP |
SMTP |
SSL - session layer security
|
IP |
TCP |
HTTP |
FTP |
SMTP |
SSL |
S-HTTP and S/MIME application layer security
|
IP |
TCP |
S-HTTP |
S/MIME |
PGP/SET - content based security
|
IP |
TCP |
HTTP |
FTP |
SMTP |
PGP |
SET |
Symmetric Cryptography
|
Secret key, Secure channel |
Cleartext |
message |
Cleartext |
message |
Encrypt |
Decrypt |
Asymmetric (public-key) Cryptography
|
Recipient's |
Public Key |
Cleartext |
message |
Cleartext |
message |
Encrypt |
Decrypt |
Recipient's |
Private key |
Digital Signatures
|
Originator's |
Private Key |
Cleartext |
message |
Cleartext |
message |
Encrypt |
Decrypt |
Originator's |
Public key |
Adding Integrity and Non-Repudiation |
Hash functions (result cannot be decrypted): create unique fingerprint of the original message |
Message |
digest |
Originator's |
Private Key |
Encrypt |
Originator's |
Public key |
Decrypt |
Message |
digest |
Message |
digest |
compare |
Originator's message |
Originator |
Recipient |
PlainText |
Ciphertext |
PlainText |
Encryption |
Decryption |
Most ciphers consists of public algorithm and a key which needs to be long to be safe (40, 56, 128 bits) |
Encryption and decryption is computationally expensive |
Brute force attack:
|
The most popular symmetric encryption algorithms
|
The most popular asymmetric encryption algorithms
|
Requirements
|
Standards
|
PGP - Pretty Good Privacy
|
PGP - Pretty Good Privacy
|
PGP - Pretty Good Privacy |
Plain |
text |
Session |
key |
cipher |
text |
Encrypted |
session |
key |
Plain |
text |
Session |
key |
Encrypted with |
session key |
Decrypted with |
session key |
compressed |
Recipients |
public key |
Recipients |
private key |
Encryption |
Decryption |
S/MIME - Secure/Multipurpose Internet Mail Extension
|
S/MIME
|
S/MIME
|
MIME header |
Content |
S/MIME header |
Encrypted |
Content |
How credit card transaction work ? |
How it is being mapped into the Web ?
|
Transaction types
|
in the real world:
|
Card Holder |
(owner of the card) |
Card Processing |
Network |
(verifone reader |
in supermarket) |
Issuing bank |
(represents a client) |
Acquiring bank |
(represents a merchent) |
The Web is open for business. The number of commercial sites is growing |
Buzzwords: e-commerce, virtual malls, cyber-shops, virtual storefront, electronic shopping carts, etc. |
Despite the hype, the current Internet market is a tiny fraction of the traditional market (growing fast) |
major concern: security |
Models existing systems; built on existing infrastructure |
Technologies such as SSL and SET make purchasing over the Internet possible |
Heavily relies on SSL
|
Users retrieve server certificate |
Clients use user ID and passwords to authenticate to a server |
Client |
Server |
hello |
User ID/password |
Client |
Server |
hello |
Internet Commerce Characteristics
|
Issuing |
BANK |
Purchaser |
Merchant |
Acquiring |
BANK |
Flow of Data |
verification |
settlement |
Certificate |
Certificate |
Settlement |
Merchant |
Server |
Web |
Server |
DB |
Internet |
Banks |
Client |
Customer order |
Payment authoriz. |
Order confirmation |
Database query |
Firewall |
Merchant Server
|
Examples of merchant servers
|
On the internet it is common to deal with vendors and clients we have never meet before, who have no reputation, and whom we can never meet again |
E-commerce allows do business over the Internet (insecure network). Security based on
|
SET and SSL are widely known communication protocols, each providing a way to make payments over the Internet |
Client |
Web |
and |
Merchant |
Servers |
Banks |
SSL |
Order page |
Credit card |
Receipt |
Traditional Clearing |
Stealing credit card information from the Merchant Server happens |
Case Study (SSL)
|
Client Hello (a list of cipher suites supported) |
Server Hello (server selects a cipher suite) |
Certificate: contains the server public key |
Session Key encrypted with server public key |
HTTP communication over secure channel |
Client (browser) |
Merchant (Server) |
verification |
decryption |
SSL does NOT assure me that the Merchant is authorized to accept my credit card |
Is the conversation private ?
|
SSL was originally designed by Netscape |
Netscape made C-based source code available for developers (SSLRef Library): http://home.netscape.com/eng/US-Current (US government restrictions) |
SSL is open, not proprietary protocol |
SSL is easy to apply and use because is built in all major Web browsers (IE, Netscape) and servers |
SSL is using S/MIME to send secure data: a user transmitting information to an SSL server from within his browser will transmit that info within a S/MIME packet) |
Message transfer is 40 bit RC4 (export) and 128 bit RC4 (in USA) |
Public key cryptography - RSA 1024 bit, D-H |
HTTP protocol is using port 80 (by default); HTTP+SSL (https://...) is using port 443 by default |
Naming convention for SSL enabled servers: HTTPS, FTPS, NNTPS |
The same server can run both secure and insecure servers simultaneously: access to catalog of products can be insecure, whereas ordering and payment should be done through the secure channel |
Non-SSL browser cannot access https server |
SET is a messaging protocol specifically designed by Master Card, Visa, and others to secure bank-card payment transactions over open networks
|
Case Study (SET)
|
Case Study (SET) |
Consumer |
CA |
BankNet |
Payment |
Gareway |
Merchant |
Transaction |
Certificate |
Certificate |
Authorization |
Settlement |
Digital |
Wallet |
Cardholder "wallet" software: It allows secure purchases. It communicates with the merchant's (server) software verify the merchant's digital certificate. This program also maintains, and administers the cardholder's certificate (client). |
Merchant Software: This application is required to communicate securely with the cardholder and its financial institution. It also manages the exchange of digital certificates prior to a sale transaction. |
Payment Gateway server software: It performs standard and automatic payment processes. It decrypts payment instructions from cardholders and supports the process of merchant certificate request. |
Certificate authority software: The application allows customers (client) and merchants (server) to register their respective account agreements for secure electronic commerce. It is used to issue digital certificates to cardholders (client) and merchants (server). |
SET messages are essentially the same as those that have been used in the traditional banking networks for years. SET allows them to flow across the insecure, open Internet |
SET defines all necessary communication between banks, merchants, cardholders, whereas SSL creates a secure connection between 2 computers. |
SET provides merchants with assurance that the card holder will not say "it is not me"; the bank has evidence that I made a purchase |
SET provides a card holder with assurance that the merchant is legitimate |
SET offers security at the expense of simplicity |
SET is so complicated that banks and merchants are not eager to deploy it |
In practical implementations:
|
SET extends the current message flow in banking networks into cyberspace |
SET requires appropriate software installed in the banking network, at merchant's locations, and on consumer's computers |
Merchant does not have access to client's account information (privacy of financial data) |
SET offers a complete card payment system (payment transport, confirmation and inquiry) |
Symmetric key Cryptography: DES 56 bit key |
Public key Cryptography: RSA 768, 1024, 2048 bit keys |
Hashing: SHA-1 |
Will SET replace SSL ? NO, there are virtually no technical similarities between SET and SSL, except that both use RSA public key cryptography |
Is SET dead ? NO, it is just much more complex, advanced |
Is SSL good enough for e-commerce ? NO, but it is being used |
Does merchant know who the client is ? NO, credit card-over-SSL authenticate the identity of the server to the browser, but not vice versa; it can be done in SSL but clients have no certificates. |
Going Virtual (From a merchant perspective)
|
To "go virtual" you will need some of the following to start taking credit card orders over the Web:
|
SSL-Enabled Web Site
|
Merchant Account
|
Catalog and Shopping Cart Software
|
Sales-Tax Software
|
Payment Processing Software
|
Focus: User-to-Bank Transactions |
Online banking standard from Microsoft, Checkfree and Intruit |
Merger of 2 standards
|
Built on open standards
|
Supported by: Web browsers and Desktop applications (Quicken, MS Money) |
Transport independent (currently HTTP but not required) |
Services
|
Security
|
More info: www.ofx.com |
Client |
OFX |
Server |
Web |
Server |
Profile |
Server |
Clients locate |
Financial |
Institutions |
via Profile |
Servers |
FI Identifier |
FI Profile |
OFX Request |
OFX Response |
Financial Institution (FI) |
(SSL (OFX Data (Encrypted Password))) |
(OFX Data (Encrypted Password)) |
Focus : Business-to-Business transactions |
Designed as EDI complement (Electronic Data Interchange); targets high volume, low cost corporate orders (distributors, suppliers, business partners, agents, etc.) |
Security based on
|
Characteristics
|
Standard supported by
|
OBI Architecture |
Buying |
Organization |
Requisitioner |
Payment |
Authority |
Selling |
Organization |
Requisitioner: End-user in the system who places an order. It also has a digital certificate, issued by the trusted certificate authority. |
Buying Organization: Represents the purchasing management and the information systems which support purchasing. These systems include the OBI server, receives and requests OBI orders, trading partner information, workflow, approvals, account, and tax status. |
Selling Organization: maintains dynamic online catalog. It also presents price and product information. |
Payment authority: It provides authority for the payment vehicle presented by the requisitioner. |
Firewalls - guardians for areas of the network. The firewall must permit only authorized traffic. The firewall itself must be immune to penetration. Setting up an Internet Firewall without a comprehensive security policy is like placing a steel door on a tent. |
Architecture of firewalls is based on : packet filtering, proxies, state inspection, or network address hiding and translation |
What is a firewall ?
|
Firewall types
|
Firewall characteristics
|
Management and systems personnel often assume that if they have a firewall, they have sufficient security and no further security checks are needed |
Some network services (like ftp, http, sendmail, telnet) are passed through the firewall |
External |
network |
Internal |
Mail, DNS, NIS, FTP |
Print, NFS, WWW |
Web |
Server |
Firewall |
DNS |
Multi-homed firewall |
Gauntlet Firewall 2.0 for Windows NT from Network Associates (http://www.nai.com) |
FireWall-1 for Windows NT from Check Point Software Technologies (http://www.checkpoint.com) |
Firewall policy:
|
Computer crimes
|
Attacks
|
Attacks
|
Attacks
|
Only 5% of crackers write their own code; most cracker tools is publicly available |
Large majority of attacks are INTERNAL |
Hacker attacks (vandalism, springboard) |
Denial of service (competition) |
Theft (software, ideas, money) |
Damage to public image (companies, people) |
Hacker tools getting easier to use (GUI) and easily distributed (hacker groups as distribution houses) |
High quality, extremely functional hacker tools; lots of good tools |
Attack from multiple sources simultaneously at Christmas time, New Years Eve, etc |
New hacks all the time |
The attacks are getting more sophisticated |
Various hacks are combined |
Hackers are one step ahead of security solution deployment |
Against companies to make their computers unusable; damage the company image |
Takes systems attention from real attack |
There are countless DoS attacks out there today ftp://info.cert.org/pub/tech_tips/denial_of_service |
Various forms:
|
Land Attack
|
Land Attack defense
|
DNS - Domain Name Service - critical component of the Internet; maps names to IP addresses; mail exchanger |
Clients use resolver to access DNS servers |
BIND - Berkeley Internet Name Domain - most common DNS |
DNS servers query each other to resolve names (QueryID) |
To lower traffic requirements, DNS servers will cache answers |
Client |
Local |
DNS |
Company |
DNS |
COM |
DNS |
Root |
DNS |
www.company.com |
Evil |
x.y.z.w |
DNS |
good |
DNS |
evil |
DNS |
bank |
(1) any.evil.com ? |
(2) any.evil.com ? |
(3) store Query ID# |
(4) www.bank.com ? |
(5) www.bank.com ? |
(6) spoof answer: |
www.bank.com=x.y.z.w |
(7) Cache: |
www.bank.com |
= x.y.z.w |
Good |
(8) www.bank.com ? |
(9) x.y.z.w |
(10) bank transaction |
Www |
bank |
DNS cache attack affects all versions of BIND and Windows NT Server DNS |
Defense
|
Allows remote control of Win 95 and Win 98 |
Backdoor: allows attacker to bypass system security controls |
Gives remote access to File system, registry, passwords, operating system, network, processes, screen and keyboard |
Introduced in August 1998 by Cult of the Dead Cow (cDc); Free from http://www.cultdeadcow.com |
BO2K (Back Orifice 2000) on the way! |
Contains integrated services: HTTP server, packet sniffer, keyboard monitor for logging keystrokes, connection and application redirection |
Works in Client - Server model; client and server communicate over UDP port 31337; port can be changed; all packets between client and server are "weak" encrypted |
Server must be installed on the victim machine; trivial to install; does not show up in the task list |
Client runs on hacker's machine |
Very nice GUI; there is also command line interface |
Allows an attacker to steal, share, terminate, monitor and log any terminal session that is in progress |
Session stolen across the network |
bypass all forms of strong authentication |
HUNT, session hijacking tool written in November 1998: http://www.rootshell.com allows insertion of commands or takeover of session |
What can be hijacked: telnet, rlogin, rsh, ftp |
Session hijacking scenario:
|
Other tools: Juggernout, TTYWatcher, IPWatcher |
Defenses: use strong authentication (SSH), do not telnet to critical computers |
Web spoofing = URL rewritting |
The attacker creates false "copy" of a the entire Web
|
Defense
|
The attacker inserts a frame into a web page
|
Defense
|
Unix since 1969; never intended to be secure; trusted (C2 and up) versions available; better knowledge what is going on; more mature; eaasier than NT to setup security |
Windows NT - relatively new; many unknown security issues (black box); very unsecure |