Presentation is loading. Please wait.

Presentation is loading. Please wait.

EEC 693/793 Special Topics in Electrical Engineering Secure and Dependable Computing Lecture 3 Wenbing Zhao Department of Electrical and Computer Engineering.

Similar presentations


Presentation on theme: "EEC 693/793 Special Topics in Electrical Engineering Secure and Dependable Computing Lecture 3 Wenbing Zhao Department of Electrical and Computer Engineering."— Presentation transcript:

1 EEC 693/793 Special Topics in Electrical Engineering Secure and Dependable Computing Lecture 3 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University wenbing@ieee.org

2 2 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Outline Types of threats Meaning of computer security Vulnerabilities in computer systems Threats in computer networks

3 3 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Type of Threats An interception means that some unauthorized party has gained access to an asset In an interruption, an asset of the system becomes lost, unavailable, or unusable If an unauthorized party not only accesses but tampers with an asset, the threat is a modification An unauthorized party might create a fabrication of counterfeit objects on a computing system

4 4 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Type of Threats

5 5 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Interception An interception means that some unauthorized party has gained access to an asset –Example: illicit copying of program or data files, or wiretapping to obtain data in a network –Unlike a loss, which may be discovered fairly quickly, a silent interceptor may leave no traces by which the interception can be readily detected

6 6 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Interruption In an interruption, an asset of the system becomes lost, unavailable, or unusable –Example: malicious destruction of a hardware device –Example: erasure of a program or data file –Example: (distributed) denial of service attacks

7 7 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Modification If an unauthorized party not only accesses but tampers with an asset, the threat is a modification –Example: someone might change the values in a database, alter a program so that it performs an additional computation –Example: modify message being transmitted over the network –Some cases of modification can be detected with simple measures, but other, more subtle, changes may be almost impossible to detect

8 8 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Fabrication An unauthorized party might create a fabrication of counterfeit objects on a computing system –Example: the intruder may insert spurious transactions to a network communication system or add records to an existing database –Sometimes these additions can be detected as forgeries, but if skillfully done, they are virtually indistinguishable from the real thing

9 9 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Threats: Methods, Opportunity, and Motive A malicious attacker must have three things: –Method: the skills, knowledge, tools, and other things with which to launch an attack –Opportunity: the time and access to accomplish the attack –Motive: a reason to want to perform this attack against this system

10 10 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao The Meaning of Computer Security The purpose of computer security is to devise ways to prevent the weaknesses from being exploited What we mean when we say that a system is secure: –Confidentiality: computer-related assets are accessed only by authorized parties. Confidentiality is sometimes called secrecy or privacy –Integrity: assets can be modified only by authorized parties or only in authorized ways –Availability: assets are accessible to authorized parties at appropriate times

11 11 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Relationship of Security Goals A secure system must meet all three requirements The challenge is how to find the right balance among the goals, which often conflict –For example, it is easy to preserve a particular object's confidentiality in a secure system simply by preventing everyone from reading that object –However, this system is not secure, because it does not meet the requirement of availability for proper access –=> There must be a balance between confidentiality and availability

12 12 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Relationship of Security Goals

13 13 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Confidentiality It is not trivial to ensure confidentiality. For example, –Who determines which people or systems are authorized to access the current system? –By "accessing" data, do we mean that an authorized party can access a single bit? pieces of data out of context? –Can someone who is authorized disclose those data to other parties? Confidentiality is the security property we understand best because its meaning is narrower than the other two We also understand confidentiality well because we can relate computing examples to those of preserving confidentiality in the real world

14 14 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Integrity It is much harder to ensure integrity. One reason is that integrity means different things in different context For example, if we say that we have preserved the integrity of an item, we may mean that the item is: –precise –accurate –unmodified –modified only in acceptable ways –modified only by authorized people –modified only by authorized processes –consistent –internally consistent –meaningful and usable

15 15 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Integrity Aspects of integrity: computerized data are the same as those in source documents; they have not been exposed to accidental or malicious alteration or destruction Aspects of integrity: authorized actions, separation and protection of resources, and error detection and correction Integrity can be enforced in much the same way as can confidentiality: by rigorous control of who or what can access which resources in what ways

16 16 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Availability Availability applies both to data and to services (i.e., to information and to information processing), and it is similarly complex We say a data item, service, or system is available if –There is a timely response to our request –There is a fair allocation of resources, so that some requesters are not favored over others –The service or system involved are fault tolerant - hardware or software faults lead to graceful cessation of service or to work- arounds rather than to crashes and abrupt loss of information –The service or system can be used easily and in the way it was intended to be used –….

17 17 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Availability The security community is just beginning to understand what availability implies and how to ensure it A small, centralized control of access is fundamental to preserving confidentiality and integrity, but it is not clear that a single access control point can enforce availability Much of computer security's past success has focused on confidentiality and integrity; full implementation of availability is security's next great challenge

18 18 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Vulnerabilities When we prepare to specify, design, code, or test a secure system, we try to imagine the vulnerabilities that would prevent us from reaching one or more of our three security goals The three assets (hardware, software and data) and the connections among them are all potential security weak points

19 19 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Vulnerabilities

20 20 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Software Vulnerabilities Software is surprisingly easy to delete and to copy Software is vulnerable to modifications that either cause it to fail or cause it to perform an unintended task

21 21 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Software Vulnerabilities Logic bomb: a program that has been maliciously modified to fail when certain conditions are met or when a certain date or time is reached Trojan horse: a program that overtly does one thing while covertly doing another Virus: a specific type of Trojan horse that can be used to spread its "infection" from one computer to another Trapdoor: a program that has a secret entry point Information leaks in a program: code that makes information accessible to unauthorized people or programs

22 22 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Data Vulnerabilities Data items have greater public value than hardware and software, because more people know how to use or interpret data By themselves, out of context, pieces of data have essentially no intrinsic value On the other hand, data items in context do relate to cost, perhaps measurable by the cost to reconstruct or redevelop damaged or lost data

23 23 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Data Vulnerabilities Confidential data leaked to a competitor may narrow a competitive edge Data incorrectly modified can cost human lives Inadequate security may lead to financial liability if certain personal data are made public

24 24 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Data Vulnerabilities The value of data over time is far less predictable or consistent Initially, data may be valued highly. However, some data items are of interest for only a short period of time, after which their value declines precipitously

25 25 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Principle of Adequate Protection Principle of Adequate Protection: –Computer items must be protected only until they lose their value –They must be protected to a degree consistent with their value

26 26 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Security of Data Confidentiality prevents unauthorized disclosure of a data item Integrity prevents unauthorized modification Availability prevents denial of authorized access

27 27 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Threats in Networks Networks are specialized collections of hardware, software, and data –Each network node is itself a computing system –It experiences all normal security problems A network must also confront communication problems that involve the interaction of system components and outside resources

28 28 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Threats in Networks The challenges to achieve network security are rooted in –A network's lack of physical proximity –Use of insecure, shared media, and –The inability of a network to identify remote users positively

29 29 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao What Makes a Network Vulnerable Anonymity. An attacker can mount an attack from thousands of miles away and never come into direct contact with the system, its administrators, or users Many points of attack—both targets and origins. An attack can come from any host to any host, so that a large network offers many points of vulnerability

30 30 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao What Makes a Network Vulnerable Sharing. Because networks enable resource and workload sharing, more users have the potential to access networked systems than on single computers Complexity of system. A network combines two or more possibly dissimilar operating systems. Unknown network boundary. A network's expandability also implies uncertainty about the network boundary

31 31 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao What Makes a Network Vulnerable Unknown network boundary

32 32 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao What Makes a Network Vulnerable Unknown path in message routing. There may be many paths from one host to another. Some intermediate node might not be trustworthy

33 33 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Methods of Defense Harm occurs when a threat is realized against a vulnerability To protect against harm, we can neutralize the threat, close the vulnerability, or both The possibility for harm to occur is called risk

34 34 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Methods of Defense We can deal with harm in several ways. We can seek to –Prevent it, by blocking the attack or closing the vulnerability –Deter it, by making the attack harder, but not impossible –Deflect it, by making another target more attractive (or this one less so) –Detect it, either as it happens or some time after the fact –Recover from its effects

35 35 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Methods of Defense – Multiple Controls

36 36 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Countermeasures / Controls Encryption –Scrambling process Software controls Hardware controls –hardware or smart card implementations of encryption Policies and Procedures –Example: change password periodically Physical Controls –Example: Locks on doors, guards at entry points

37 37 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Software Controls Internal program controls: parts of the program that enforce security restrictions, such as access limitations Operating system and network system controls: limitations enforced by the operating system or network to protect each user from all other users Independent control programs: application programs, such as password checkers, intrusion detection utilities, or virus scanners, that protect against certain types of vulnerabilities Development controls: quality standards under which a program is designed, coded, tested, and maintained, to prevent software faults from becoming exploitable vulnerabilities

38 38 Spring 2007EEC693: Secure & Dependable ComputingWenbing Zhao Principle of Effectiveness Principle of Effectiveness: Controls must be used — and used properly — to be effective. They must be efficient, easy to use, and appropriate


Download ppt "EEC 693/793 Special Topics in Electrical Engineering Secure and Dependable Computing Lecture 3 Wenbing Zhao Department of Electrical and Computer Engineering."

Similar presentations


Ads by Google