Security in Computing, Fifth Edition: Chapter 1: Introduction
Security in Computing, Fifth Edition: Chapter 1: Introduction
SECURITY IN
COMPUTING,
FIFTH EDITION
Chapter 1: Introduction
2
Assets
Values of Assets
Basic Terms
• Vulnerability
• Threat
• Attack
• Countermeasure or control
7
C-I-A Triad
• Confidentiality
• Integrity
• Availability
• Sometimes two other desirable characteristics:
• Authentication
• the process or action of proving or showing something to be true,
genuine, or valid.
• Nonrepudiation
• is the assurance that someone cannot deny something.
• i.e. nonrepudiation refers to the ability to ensure that a party to a
contract or a communication cannot deny the authenticity of their
signature on a document or the sending of a message that they
originated
10
Access Control
Policy:
Who + What + How =Yes/No
Object
Mode of access (what)
Subject (how)
(who)
11
Types of Threats
Threats
Natural Human
causes causes
Examples: Fire,
Benign Malicious
power failure
intent intent
Example:
Human error
Random Directed
Types of Attackers
Terrorist
Criminal-
Hacker
for-hire
Loosely
Individual connected
group
Organized
crime member
14
Types of Harm
Interception Interruption
Modification Fabrication
15
Threats
• In an interception means that some unauthorized party
has gained access to an asset.
Method—Opportunity—Motive (MOM)
Opportunity
Motive
Method
17
Controls/Countermeasures
Kind of Threat
Physical
Procedural
Confidentiality
Technical
Protects
Integrity
Availability
19
Security Goals
• When we talk about computer security, we mean that we are addressing three
important aspects of any computer-related system: confidentiality, integrity, &
availability (CIA)
Confidentiality
Secure
Integrity Availability
Slide #1-21
Goals of Security
• Prevention
• Prevent attackers from violating security policy
• Detection
• Detect attackers’ violation of security policy
• Recovery
• Stop attack, assess and repair damage
• Continue to function correctly even if attack succeeds
Slide #1-22
• Policies
• Unambiguously partition system states
• Correctly capture security requirements
• Mechanisms
• Assumed to enforce policy
• Support mechanisms work correctly
23
Controls Available
• Encryption
• We take data in their normal, unscrambled state, called:
• cleartext or plaintext, and transform them so that they are unintelligible
to the outside observer; the transformed data are called enciphered
text or ciphertext.
Controls Available
• Encryption does not solve all computer security
problems, and other tools must complement its use.
• if encryption is not used properly, it may have no effect on security
or could even degrade the performance of the entire system.
Controls Available
• Software/Program Controls
• Programs must be secure enough to prevent outside attack
• They must also be developed and maintained so that we can be confident of
the programs' dependability.
Controls Available
• Development controls:
• quality standards under which a program is designed, coded
(implementation), tested, and maintained to prevent software
faults from becoming exploitable vulnerabilities
• i.e. Penetration testing (pen testing or ethical hacking), is the practice
of testing a computer system, network or web application to find security
vulnerabilities that an attacker could exploit.
Controls Available
• Hardware Controls
• Numerous hardware devices have been created to
assist in providing computer security. These devices
include a variety of means, such as
• hardware or smart card implementations of encryption
• locks or cables limiting access or deterring theft
• devices to verify users' identities
• firewalls
• intrusion detection systems
• circuit boards that control access to storage media
29
Controls Available
• Policies and Procedures
• Sometimes, we can rely on agreed-on procedures or policies
among users rather than enforcing security through hardware or
software means
• i.e. frequent changes of passwords
• We must not forget the value of community standards and
expectations when we consider how to enforce security.
• Physical Controls
• i.e. locks on doors,
• guards at entry points,
• backup copies of important software and data, and
• physical site planning that reduces the risk of natural disasters.
30
Effectiveness of Controls
• Awareness of Problem
• People using controls must be convinced of the need for security.
That is, people will willingly cooperate with security requirements
only if they understand
• why security is appropriate in a given situation.
31
Effectiveness of Controls
• Likelihood of Use
• Of course, no control is effective unless it is used
• Principle of Effectiveness:
• Controls must be used properly to be effective.
• They must be efficient, easy to use, and appropriate.
Effectiveness of Controls
• Overlapping Controls
• Several different controls may apply to address a single
vulnerability.
• Periodic Review
• Just when the security specialist finds a way to secure assets
against certain kinds of attacks, the opposition doubles its efforts in
an attempt to defeat the security mechanisms. Thus, judging the
effectiveness of a control is an ongoing task.
33
Summary
• Vulnerabilities are weaknesses in a system;
• threats exploit those weaknesses;
• controls protect those weaknesses from exploitation
• Confidentiality, integrity, and availability are the three
basic security primitives
• Different attackers pose different kinds of threats based
on their capabilities and motivations
• Different controls address different threats; controls come
in many flavors and can exist at various points in the
system