Or Read Directly
ism best notes | Information Security Management
Download PDf directly
Or Read Directly
1
Geethanjali College of Engineering and Technology
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
(Name of the Subject/Lab Course):Information Security Management
(JNTU CODE: ) Programme: UG/PG
Branch: CSE Version No: 1
Year: III Document Number : GCET/CSE
Semester: II No. of Pages:136
Classification status (Unrestricted/Restricted ) :
Distribution List:
Prepared by :
1) Name : M. Vijay Bhasker Reddy
2) Sign :
3) Design : Assistant Professor
4) Date :
Updated by :
1) Name :
2) Sign :
3) Design :
4) Date :
Verified by : *For Q.C only
1) Name : 1)Name :
2) Sign : 2) Sign :
3) Design : 3) Design :
4) Date : 4) Date :
Approved by (HOD) :
1) Name: Prof. Dr. Nagender Kumar Suryadevara
2) Sign :
3) Date :
2
Contents
S. No Topic Page. No.
1 Cover Page 1
2 Syllabus copy 3
3 Vision of the Department 4
4 Mission of the Department 4
5 PEOs and POs 5
6 Course objectives and outcomes 6
7 Course mapping with POs 7
8 Brief notes on the importance of the course and how it fits into the curriculum 8
9 Prerequisites if any 8
10 Instructional Learning Outcomes 9
11 Class Time Table 11
12 Individual Time Table 13
13 Lecture schedule with methodology being used/adopted 14
14 Detailed notes 21
15 Question Bank 129
16 Discussion topics , if any 130
17 References, Journals, websites and E-links if any 130
18 Student List 131
19 Group-Wise students list for discussion topic 134
3
2. SYLLABUS
UNIT-I
Information Security Management:
Information Security Overview, Threat and Attack Vectors, Types of Attacks, Common
Vulnerabilities and Exposure (CVE), Security Attacks, Fundamentals of Information Security,
Computer Security Concerns, Information Security Measures etc.
Manage Your Work to Meet Requirements (NOS 9001)
UNIT-II
Fundamentals of Information Security:
Key Elements of Networks, Logical Elements of Networks, Critical Information
Characteristics, Information States etc.
Work Effectively with Colleagues (NOS 9002)
UNIT-III
Data Leakage:
What is Data Leakage and Statistics, Data Leakage Threats, Reducing the Risk of Data Loss,
Key Performance Indicators (KPI), Database Security etc.
UNIT-IV
Information Security Policies, Procedures and Audits:
Information Security Policies-Necessity-Key Elements and Characteristics, Security Policy
Implementation, Configuration, Security Standards-Guidelines and Frameworks etc.
UNIT-V
Information Security Management- Roles and Responsibilities:
Security Roles and Responsibilities, Accountability, Roles and Responsibilities of Information
Security Management, Team Responding to Emergency Situation- Risk Analysis Process etc.
TEXT BOOKS:
1. Management of Information Security by Michael E.Whilman and Herbert J.Mattord
REFERENCE BOOKS:
1. http://www.iso.org/iso/home/standards/management-standards/iso27001.html
2. http://csrc.nist.gov/publications/nistpubs/800-55-Rev1/SP800-55-rev1.pdf
4
3. Vision of the Department
To produce globally competent and socially responsible computer science engineers
contributing to the advancement of engineering and technology which involves
creativity and innovation by providing excellent learning environment with world class
facilities.
4. Mission of the Department
1. To be a center of excellence in instruction, innovation in research and scholarship,
and service to the stake holders, the profession, and the public.
2. To prepare graduates to enter a rapidly changing field as a competent computer
science engineer.
3. To prepare graduate capable in all phases of software development, possess a firm
understanding of hardware technologies, have the strong mathematical background
necessary for scientific computing, and be sufficiently well versed in general theory
to allow growth within the discipline as it advances.
4. To prepare graduates to assume leadership roles by possessing good communication
skills, the ability to work effectively as team members, and an appreciation for their
social and ethical responsibility in a global setting.
5
5. Program Educational Objectives (PEOs) of C.S.E.
1. To provide graduates with a good foundation in mathematics, sciences and
engineering fundamentals required to solve engineering problems that will facilitate
them to find employment in industry and / or to pursue postgraduate studies with an
appreciation for lifelong learning.
2. To provide graduates with analytical and problem solving skills to design algorithms,
other hardware / software systems, and inculcate professional ethics, inter-personal
skills to work in a multi-cultural team.
3. To facilitate graduates to get familiarized with the art software / hardware tools,
imbibing creativity and innovation that would enable them to develop cutting-edge
technologies of multi-disciplinary nature for societal development.
Program Outcomes (CSE)
1. An ability to apply knowledge of mathematics, science and engineering to develop and
analyze computing systems.
2. An ability to analyze a problem and identify and define the computing requirements
appropriate for its solution under given constraints.
3. An ability to perform experiments to analyze and interpret data for different
applications.
4. An ability to design, implement and evaluate computer-based systems, processes,
components or programs to meet desired needs within realistic constraints of time
and space.
5. An ability to use current techniques, skills and modern engineering tools necessary to
practice as a CSE professional.
6. An ability to recognize the importance of professional, ethical, legal, security and
social issues and addressing these issues as a professional.
7. An ability to analyze the local and global impact of systems /processes /applications
/technologies on individuals, organizations, society and environment.
8. An ability to function in multidisciplinary teams.
9. An ability to communicate effectively with a range of audiences.
6
10. Demonstrate knowledge and understanding of the engineering, management and
economic principles and apply them to manage projects as a member and leader in a
team.
11. A recognition of the need for and an ability to engage in life-long learning and
continuing professional development
12. Knowledge of contemporary issues.
13. An ability to apply design and development principles in producing software systems
of varying complexity using various project management tools.
14. An ability to identify, formulate and solve innovative engineering problems.
6. Course Objectives
1. To introduce the terminology, technology and its applications.
2. To introduce the concept of Security Analyst.
3. To introduce the tool, technologies and programming languages which is used in day
to day security analyst job role.
Course Outcomes
Students will able to
CO 1: Understand the difference between threats and attacks.
CO 2: Understand the Security Issues and Measures.
CO 3: Know the KEY Elements and Logical Elements of Networks
CO 4: Understand the Data Leakage, its Threats and Mitigation.
CO 5: Understand the Database Security.
CO 6: Understand the Policies, Guideline and Framework of Information Security.
CO 7: Understand the Roles and Responsibilities of ISM.
7
7. Course Mapping with POs
MAPPING OF COURSE TO PEOS
Pos 1 2 3 4 5 6 7 8 9 10 11 12 13 14
ISM
CO1: Understand
the difference
between threats
and attacks.
M M M H M M
CO2: Understand
the Security
Issues and
Measures.
M M M H M M M M H
CO3: Know the
KEY Elements and
Logical Elements
of Networks
L H H H M M H M
CO4: Understand
the Data Leakage,
its Threats and
Mitigation.
M M H H M M H M
CO5: Understand
the Database
Security.
M L L H L M M
CO6: Understand
the Policies,
M L H L M
Course PEOS POs Teaching Aids
Information
Security
Management
PEO1,PEO2,
PEO3
PO 2, PO 4, PO
5, PO 6, PO 7,
PO 8, PO 10, PO
12, PO 13
Chalk & Talk, OHP/LCD Projector,
Internet, Q&A , Group Tasks ,Etutorials,
8
Guideline and
Framework of
Information
Security.
CO7: Understand
the Roles and
Responsibilities
of ISM.
M M M H M M M M
8. Brief Notes on the Importance of the Course
An ISMS is a systematic approach to managing sensitive company information so that it
remains secure. It includes people, processes and IT systems by applying a risk
management process.
It can help small, medium and large businesses in any sector keep information assets
secure.
The ISO 27000 family of standards helps organizations keep information assets secure.
Using this family of standards will help your organization manage the security of assets
such as financial information, intellectual property, employee details or information
entrusted to you by third parties.
ISO/IEC 27001 is the best-known standard in the family providing requirements for an
information security management system (ISMS).
9. Prerequisites
Data Communication and Computer Networks, Information Security, Database
Management Systems.
9
10. Instructional Learning Outcomes
S. No. Topic Topic Outcomes
UNIT-1
1
Information Security
Management
2
Information Security
Overview Basic Understanding of IS
3 Threat and Attack Vectors Differences between Threats and Attacks
4 Types of Attacks Types of Attacks
5
Common Vulnerabilities
and Exposure (CVE) Vulnerabilities and its Impact
6
Fundamentals of
Information Security Basic Understanding of IS
7
Computer Security
Concerns Issues of CS
8
Information Security
Measures Measures of IS
9
Manage Your Work to Meet
Requirements (NOS 9001) Task to be done to meet the requirements for IS
UNIT-II
10
Fundamentals of
Information Security
11 Key Elements of Networks Understanding the Key Elements of Networks
12
Logical Elements of
Networks Understanding the Logical Elements of Networks
13
Critical Information
Characteristics Understanding the Char. Of Critical Information
14 Information States Understanding the States of Information
15
Work Effectively with
Colleagues (NOS 9002) Task to be done
UNIT-III
16 Data Leakage:
17
What is Data Leakage and
Statistics Understanding Data Leakage and its Statistics
18 Data Leakage Threats Understanding DL Threats
10
19
Reducing the Risk of Data
Loss Understanding DL Mitigations
20
Key Performance
Indicators (KPI) Understanding the KPI of DL
21 Database Security Understanding DB Sec
UNIT-IV
22
Information Security Policies,
Procedures and Audits
23
Information Security
Policies Understanding Policies
24
Necessity-Key Elements
and Characteristics Understanding Char of IS
25
Security Policy
Implementation Implementation of Security Policy
26 Configuration Understanding Configuration of IS Policies
27
Security StandardsGuidelines and
Frameworks
Understanding the Standards, Guidelines and
Frameworks
UNIT-V
28
Information Security
Management- Roles and
Responsibilities Understanding the Roles and Responsibilities of ISM
29
Security Roles and
Responsibilities Understanding the Roles and Responsibilities of ISM
30 Accountability
31
Roles and Responsibilities
of Information Security
Management Understanding the Roles and Responsibilities of ISM
32
Team Responding to
Emergency Situation
33 Risk Analysis Process Understanding Intruders and Detection system
11
11. Class Time Tables
3 CSE A
Time 09.30-
10.20
10.20-
11.10
11.10-
12.00
12.00-
12.50
12.50-
1.30
1.30-
2.20 2.20-3.10 3.10-4.00
Period 1 2 3 4
LUNCH
5 6 7
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
3 CSE-B
Time 09.30-
10.20
10.20-
11.10
11.10-
12.00
12.00-
12.50
12.50-
1.30
1.30-
2.20 2.20-3.10 3.10-4.00
Period 1 2 3 4
LUNCH
5 6 7
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
12
3 CSE-C
Time 09.30-
10.20
10.20-
11.10
11.10-
12.00
12.00-
12.50
12.50-
1.30
1.30-
2.20 2.20-3.10 3.10-4.00
Period 1 2 3 4
LUNCH
5 6 7
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
3 CSE D
Time 09.30-
10.20
10.20-
11.10
11.10-
12.00
12.00-
12.50
12.50-
1.30
1.30-
2.20 2.20-3.10 3.10-4.00
Period 1 2 3 4
LUNCH
5 6 7
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
13
12. Individual Time Tables
Lokeshwari Subject :III YR ISM
Time 09.30-
10.20
10.20-
11.10
11.10-
12.00
12.00-
12.50
12.50-
1.30
1.30-
2.20
2.20-
3.10
3.10-
4.00
Period 1 2 3 4
LUNCH
5 6 7
Monday
Tuesday
Wednesda
y
Thursday
Friday
Saturday
M Vijay Bhasker Reddy Subject :III YR ISM
Time 09.30-
10.20
10.20-
11.10
11.10-
12.00
12.00-
12.50
12.50-
1.30
1.30-
2.20
2.20-
3.10
3.10-
4.00
Period 1 2 3 4
LUNCH
5 6 7
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
14
13. Lecture schedule with methodology being used/adopted
Lesson plan
S. No.
Period
No. Topic
Regular/
Additional
Teaching
aids
used
PPT/
OHP/ BB Remarks
UNIT-1
1 1
Information Security
Management Regular BB
2 2
Information Security
Overview Regular BB
3 3,4
Threat and Attack
Vectors Regular BB
4 5,6 Types of Attacks Regular
BB, PPT
5 7
Common
Vulnerabilities and
Exposure (CVE) Regular BB
6 8,9
Fundamentals of
Information Security Regular BB
7 10,11
Computer Security
Concerns Regular BB,
8 12
Information Security
Measures Regular BB
9 13
Manage Your Work to Meet
Requirements (NOS 9001) Regular BB
UNIT-II
10 14,15
Fundamentals of
Information Security Regular BB
11 16,17
Key Elements of
Networks Regular BB
12 18,19
Logical Elements of
Networks
20
Critical Information
Characteristics Regular BB
13 21 Information States Regular BB,
14 22,23
Work Effectively with
Colleagues (NOS 9002) Regular BB
UNIT-III
15
15 24 Data Leakage: Regular BB
16 25,26
What is Data Leakage
and Statistics Regular BB
17 27,28 Data Leakage Threats Regular BB
18 29,30
Reducing the Risk of
Data Loss Regular BB
19 31
Key Performance
Indicators (KPI) Regular BB
20 32,33,34 Database Security Regular BB, PPT
UNIT-IV
21 35
Information Security
Policies, Procedures and
Audits Regular BB
22 36,37
Information Security
Policies Regular BB
23 38,39
Necessity-Key Elements
and Characteristics Regular BB
24 40,41
Security Policy
Implementation Regular BB
25 42 Configuration Regular BB, PPT
26 43,44
Security StandardsGuidelines and
Frameworks Regular BB, PPT
UNIT-V
28 45
Information Security
Management- Roles and
Responsibilities Regular BB
29 46,47
Security Roles and
Responsibilities Regular BB, PPT
30 48 Accountability Regular BB, PPT
31 48,49
Roles and
Responsibilities of
Information Security
Management Regular BB, PPT
32 50,51
Team Responding to
Emergency Situation Regular BB
33 52,53 Risk Analysis Process Regular BB, PPT
**Tentative Classes ***Excluding Tutorials, Internals and Revision Classes
16
14. Lesson schedule
Geethanjali College of Engineering & Technology
Department of Computer Science andEngineering
Lesson Plan & Schedule
Year & Sem: III year Sem-II(Sec-A, B) Sub: ISM
Faculty Name:
S. No. Date Topic to be Covered
Total No. of
Periods
UNIT-1
1 07.12.15 Information Security Management 1
2 08.12.15 Information Security Overview 1
3
09.12.15
10.12.15 Threat and Attack Vectors 2
4
11.12.15
14.12.15 Types of Attacks 2
5 15.12.15 Common Vulnerabilities and Exposure (CVE) 1
6
16.12.15
17.12.15 Fundamentals of Information Security 2
7
18.12.15
19.12.15 Computer Security Concerns 2
8 20.12.15 Information Security Measures 1
9 21.12.15
Manage Your Work to Meet Requirements (NOS
9001) 1
Total No. of Periods 13
UNIT-II
13
24.12.15
26.12.15 Fundamentals of Information Security 2
14
27.12.15
28.12.15 Key Elements of Networks 2
17
15
29.12.15
30.12.15 Logical Elements of Networks 2
16 31.12.15 Critical Information Characteristics 1
17 02.01.16 Information States 1
18
04.01.16
05.01.16 Work Effectively with Colleagues (NOS 9002) 2
Total No. of Periods 10
UNIT-III
24 06.01.16 Data Leakage: 1
25
07.01.16
08.01.16 What is Data Leakage and Statistics 2
26
11.01.16
12.01.16 Data Leakage Threats 2
27
18.01.16
19.01.16 Reducing the Risk of Data Loss 2
28 20.01.16 Key Performance Indicators (KPI) 1
29
21.01.16
22.01.16
23.01.16 Database Security 3
Total No. of Periods 11
UNIT-IV
33 25.01.16
Information Security Policies, Procedures and
Audits 1
34
27.01.16
28.01.16 Information Security Policies 2
35
29.01.16
30.01.16 Necessity-Key Elements and Characteristics 2
36
08.02.16
09.02.16 Security Policy Implementation 2
37 10.02.16 Configuration 1
38
11.02.16
12.02.16
Security Standards-Guidelines and
Frameworks 2
Total No. of Periods 10
UNIT-V
18
40 15.02.16
Information Security Management- Roles and
Responsibilities
41
16.02.16
17.02.16 Security Roles and Responsibilities 1
42
18.02.16
19.02.16 Accountability 2
43 01.03.16
Roles and Responsibilities of Information
Security Management 2
44
02.03.16
03.03.16 Team Responding to Emergency Situation 2
45
04.03.16
05.03.16 Risk Analysis Process 2
Total No. of Periods 09
Total No. of Periods 53
**Tentative Dates Subject to Change *** Excluding Tutorial, Internals and Revision Classes
Geethanjali College of Engineering & Technology
Department of Computer Science andEngineering
Lesson Plan & Schedule
Year & Sem: III year Sem-1(Sec-C, D) Sub: IS
Faculty Name:
S. No. Date Topic to be Covered
Total No. of
Periods
UNIT-1
1 07.12.15 Information Security Management 1
2 08.12.15 Information Security Overview 1
3
09.12.15
10.12.15 Threat and Attack Vectors 2
4
11.12.15
14.12.15 Types of Attacks 2
5 15.12.15 Common Vulnerabilities and Exposure (CVE) 1
19
6
16.12.15
17.12.15 Fundamentals of Information Security 2
7
18.12.15
19.12.15 Computer Security Concerns 2
8 20.12.15 Information Security Measures 1
9 21.12.15
Manage Your Work to Meet Requirements (NOS
9001) 1
Total No. of Periods 13
UNIT-II
13
24.12.15
26.12.15 Fundamentals of Information Security 2
14
27.12.15
28.12.15 Key Elements of Networks 2
15
29.12.15
30.12.15 Logical Elements of Networks 2
16 31.12.15 Critical Information Characteristics 1
17 02.01.16 Information States 1
18
04.01.16
05.01.16 Work Effectively with Colleagues (NOS 9002) 2
Total No. of Periods 10
UNIT-III
24 06.01.16 Data Leakage: 1
25
07.01.16
08.01.16 What is Data Leakage and Statistics 2
26
11.01.16
12.01.16 Data Leakage Threats 2
27
18.01.16
19.01.16 Reducing the Risk of Data Loss 2
28 20.01.16 Key Performance Indicators (KPI) 1
29
21.01.16
22.01.16
23.01.16 Database Security 3
Total No. of Periods 11
20
UNIT-IV
33 25.01.16
Information Security Policies, Procedures and
Audits 1
34
27.01.16
28.01.16 Information Security Policies 2
35
29.01.16
30.01.16 Necessity-Key Elements and Characteristics 2
36
08.02.16
09.02.16 Security Policy Implementation 2
37 10.02.16 Configuration 1
38
11.02.16
12.02.16
Security Standards-Guidelines and
Frameworks 2
Total No. of Periods 10
UNIT-V
40 15.02.16
Information Security Management- Roles and
Responsibilities
41
16.02.16
17.02.16 Security Roles and Responsibilities 1
42
18.02.16
19.02.16 Accountability 2
43 01.03.16
Roles and Responsibilities of Information
Security Management 2
44
02.03.16
03.03.16 Team Responding to Emergency Situation 2
45
04.03.16
05.03.16 Risk Analysis Process 2
Total No. of Periods 09
Total No. of Periods 53
**Tentative Dates Subject to Change *** Excluding Tutorial, Internals and Revision Classes
21
15. Detailed Notes
UNIT –I
Information Security Management:
Information Security Overview, Threat and Attack Vectors, Types of Attacks, Common
Vulnerabilities and Exposure (CVE), Security Attacks, Fundamentals of Information
Security, Computer Security Concerns, Information Security Measures etc.
Manage Your Work to Meet Requirements (NOS 9001)
INFORMATION SECURITY OVERVIEW
Computer data often travels from one computer to another, leaving the safety of
its protected physical surroundings. Once the data is out of hand, people with bad
intention could modify or forge your data, either for amusement or for their own benefit.
Cryptography can reformat and transform our data, making it safer on its trip between
computers. The technology is based on the essentials of secret codes, augmented by
modern mathematics that protects our data in powerful ways.
• Computer Security - generic name for the collection of tools designed to protect data
and to thwart hackers
• Network Security - measures to protect data during their transmission
• Internet Security - measures to protect data during their transmission over a collection
of interconnected networks
THE OSI SECURITY ARCHITECTURE
To assess effectively the security needs of an organization and to evaluate and
choose various security products and policies, the manager responsible for security
needs some systematic way of defining the requirements for security and characterizing
the approaches to satisfying those requirements. The OSI security architecture was
developed in the context of the OSI protocol architecture, which is described in Appendix
H. However, for our purposes in this chapter, an understanding of the OSI protocol
architecture is not required. For our purposes, the OSI security architecture provides a
22
useful, if abstract, overview of many of the concepts. The OSI security architecture focuses
on security attacks, mechanisms, and services. These can be defined briefly as follows:
Threat
A potential for violation of security, which exists when there is a circumstance,
capability, action, or event that could breach security and cause harm. That is, a
threat is a possible danger that might exploit a vulnerability.
Attack
An assault on system security that derives from an intelligent threat; that is, an
intelligent act that is a deliberate attempt (especially in the sense of a method or
technique) to evade security services and violate the security policy of a system.
Information Security: It can be defined as “measures adopted to prevent the
unauthorized use, misuse, modification or denial of use of knowledge, facts, data or
capabilities”. Three aspects of IS are:
Security Attack: Any action that comprises the security of information
Security Mechanism: A mechanism that is designed to detect, prevent, or recover
from a security.
Security Service: It is a processing or communication service that enhances the
security of the data processing systems and information transfer. The services are
intended to counter security attacks by making use of one or more security
mechanisms to provide the service.
SECURITY ATTACK
any action that compromises the security of information owned by an
organization
information security is about how to prevent attacks, or failing that, to detect
attacks on information-based systems
often threat & attack used to mean same thing
have a wide range of attacks
can focus of generic types of attacks
23
Passive
Active
PASSIVE ATTACK
A Passive attack attempts to learn or make use of information from the system, but does
not affect system resources.
Two types:
Release of message content
It may be desirable to prevent the opponent from learning the contents (i.e
sensitive or confidential info) of the transmission.
Traffic analysis
A more subtle technique where the opponent could determine the location and
identity of communicating hosts and could observe the frequency & length of encrypted
messages being exchanged there by guessing the nature of communication taking place.
Passive attacks are very difficult to detect because they do not involve any alternation of
the data. As the communications take place in a very normal fashion, neither the sender
24
nor receiver is aware that a third party has read the messages or observed the traffic
pattern. So, the emphasis in dealing with passive attacks is on prevention rather than
detection.
ACTIVE ATTACK
Active attacks involve some modification of the data stream or creation of a false
stream. An active attack attempts to alter system resources or affect their operation.
Four types:
Masquerade: Here, an entity pretends to be some other entity. It usually includes
one of the other forms of active attack.
Replay: It involves the passive capture of a data unit and its subsequent
retransmission to produce an unauthorized effect.
Modification of messages: It means that some portion of a legitimate message is
altered, or that messages are delayed to produce an unauthorized effect.
Ex: “John’s acc no is 2346” is modified as “John’s acc no is 7892”
Denial of service: This attack prevents or inhibits the normal use or management
of communication facilities.
Ex: a: Disruption of entire network by disabling it
b: Suppression of all messages to a particular destination by a third party. Active
attacks present the opposite characteristics of passive attacks. Whereas passive attacks
are difficult to detect, measures are available to prevent their success. On the other hand,
it is quite difficult to prevent active attacks absolutely, because of the wide variety of
potential physical, software and network vulnerabilities. Instead, the goal is to detect
active attacks and to recover from any disruption or delays caused by them.
25
INTERRUPTION
An asset of the system is destroyed or becomes unavailable or unusable. It is an attack
on availability.
Examples:
Destruction of some hardware
Jamming wireless signals
Disabling file management systems
INTERCEPTION
An unauthorized party gains access to an asset. Attack on confidentiality.
Examples:
Wire tapping to capture data in a network.
Illicitly copying data or programs
Eavesdropping
MODIFICATION
When an unauthorized party gains access and tampers an asset. Attack is on Integrity.
26
Examples:
Changing data file
Altering a program and the contents of a message
FABRICATION
An unauthorized party inserts a counterfeit object into the system. Attack on
Authenticity. Also called impersonation
Examples:
Hackers gaining access to a personal email and sending message
Insertion of records in data files
Insertion of spurious messages in a network
SECURITY SERVICES
It is a processing or communication service that is provided by a system to give a
specific kind of production to system resources. Security services implement security
policies and are implemented by security mechanisms.
Confidentiality
Confidentiality is the protection of transmitted data from passive attacks. It is used
to prevent the disclosure of information to unauthorized individuals or systems. It has
been defined as “ensuring that information is accessible only to those authorized to have
access”.
The other aspect of confidentiality is the protection of traffic flow from analysis.
Ex: A credit card number has to be secured during online transaction.
27
Authentication
This service assures that a communication is authentic. For a single message
transmission, its function is to assure the recipient that the message is from intended
source. For an ongoing interaction two aspects are involved. First, during connection
initiation the service assures the authenticity of both parties. Second, the connection
between the two hosts is not interfered allowing a third party to masquerade as one of
the two parties. Two specific authentication services defines in X.800 are
Peer entity authentication: Verifies the identities of the peer entities involved in
communication. Provides use at time of connection establishment and during data
transmission. Provides confidence against a masquerade or a replay attack
Data origin authentication: Assumes the authenticity of source of data unit, but
does not provide protection against duplication or modification of data units. Supports
applications like electronic mail, where no prior interactions take place between
communicating entities.
Integrity
Integrity means that data cannot be modified without authorization. Like
confidentiality, it can be applied to a stream of messages, a single message or selected
fields within a message. Two types of integrity services are available. They are
Connection-Oriented Integrity Service: This service deals with a stream of
messages, assures that messages are received as sent, with no duplication, insertion,
modification, reordering or replays. Destruction of data is also covered here. Hence, it
attends to both message stream modification and denial of service.
Connectionless-Oriented Integrity Service: It deals with individual messages
regardless of larger context, providing protection against message modification only.
An integrity service can be applied with or without recovery. Because it is related to
active attacks, major concern will be detection rather than prevention. If a violation is
detected and the service reports it, either human intervention or automated recovery
machines are required to recover.
Non-repudiation
Non-repudiation prevents either sender or receiver from denying a transmitted
message. This capability is crucial to e-commerce. Without it an individual or entity can
deny that he, she or it is responsible for a transaction, therefore not financially liable.
28
Access Control
This refers to the ability to control the level of access that individuals or entities
have to a network or system and how much information they can receive. It is the ability
to limit and control the access to host systems and applications via communication links.
For this, each entity trying to gain access must first be identified or authenticated, so that
access rights can be tailored to the individuals.
Availability
It is defined to be the property of a system or a system resource being accessible
and usable upon demand by an authorized system entity. The availability can significantly
be affected by a variety of attacks, some amenable to automated counter measures i.e
authentication and encryption and others need some sort of physical action to prevent or
recover from loss of availability of elements of a distributed system.
SECURITY MECHANISMS:
According to X.800, the security mechanisms are divided into those implemented
in a specific protocol layer and those that are not specific to any particular protocol layer
or security service. X.800 also differentiates reversible & irreversible encipherment
mechanisms. A reversible encipherment mechanism is simply an encryption algorithm
that allows data to be encrypted and subsequently decrypted, whereas irreversible
encipherment include hash algorithms and message authentication codes used in digital
signature and message authentication applications
SPECIFIC SECURITY MECHANISMS:
Incorporated into the appropriate protocol layer in order to provide some of the
OSI security services,
Encipherment: It refers to the process of applying mathematical algorithms for
converting data into a form that is not intelligible. This depends on algorithm used and
encryption keys.
Digital Signature: The appended data or a cryptographic transformation applied
to any data unit allowing to prove the source and integrity of the data unit and protect
against forgery.
Access Control: A variety of techniques used for enforcing access permissions to
the system resources.
29
Data Integrity: A variety of mechanisms used to assure the integrity of a data unit
or stream of data units.
Authentication Exchange: A mechanism intended to ensure the identity of an
entity by means of information exchange.
Traffic Padding: The insertion of bits into gaps in a data stream to frustrate traffic
analysis attempts.
Routing Control: Enables selection of particular physically secure routes for
certain data and allows routing changes once a breach of security is suspected.
Notarization: The use of a trusted third party to assure certain properties of a
data exchange
PERVASIVE SECURITY MECHANISMS:
These are not specific to any particular OSI security service or protocol layer.
Trusted Functionality: That which is perceived to b correct with respect to some
criteria
Security Level: The marking bound to a resource (which may be a data unit) that
names or designates the security attributes of that resource.
Event Detection: It is the process of detecting all the events related to network
security.
Security Audit Trail: Data collected and potentially used to facilitate a security
audit, which is an independent review and examination of system records and activities.
Security Recovery: It deals with requests from mechanisms, such as event
handling and management functions, and takes recovery actions.
MODEL FOR NETWORK SECURITY
30
Data is transmitted over network between two communicating parties, who must
cooperate for the exchange to take place. A logical information channel is established by
defining a route through the internet from source to destination by use of communication
protocols by the two parties. Whenever an opponent presents a threat to confidentiality,
authenticity of information, security aspects come into play. Two components are present
in almost all the security providing techniques.
A security-related transformation on the information to be sent making it unreadable
by the opponent, and the addition of a code based on the contents of the message, used to
verify the identity of sender.
Some secret information shared by the two principals and, it is hoped, unknown to
the opponent. An example is an encryption key used in conjunction with the transformation
to scramble the message before transmission and unscramble it on reception
A trusted third party may be needed to achieve secure transmission. It is
responsible for distributing the secret information to the two parties, while keeping it
away from any opponent. It also may be needed to settle disputes between the two parties
regarding authenticity of a message transmission. The general model shows that there
are four basic tasks in designing a particular security service:
1. Design an algorithm for performing the security-related transformation. The
algorithm should be such that an opponent cannot defeat its purpose
2. Generate the secret information to be used with the algorithm
3. Develop methods for the distribution and sharing of the secret information
4. Specify a protocol to be used by the two principals that makes use of the security
algorithm and the secret information to achieve a particular security service
Various other threats to information system like unwanted access still exist. The
existence of hackers attempting to penetrate systems accessible over a network remains
a concern. Another threat is placement of some logic in computer system affecting various
applications and utility programs. This inserted code presents two kinds of threats.
Some basic terminologies used:
CIPHER TEXT - the coded message
CIPHER - algorithm for transforming plaintext to ciphertext
KEY - info used in cipher known only to sender/receiver
31
ENCIPHER (ENCRYPT) - converting plaintext to ciphertext
DECIPHER (DECRYPT) - recovering ciphertext from plaintext
CRYPTOGRAPHY - study of encryption principles/methods
CRYPTANALYSIS (CODEBREAKING) - the study of principles/ methods of deciphering
ciphertext without knowing key
CRYPTOLOGY - the field of both cryptography and cryptanalysis
CRYPTOGRAPHY
Cryptographic systems are generally classified along 3 independent dimensions:
Type of operations used for transforming plain text to cipher text
All the encryption algorithms are abased on two general principles: substitution,
in which each element in the plaintext is mapped into another element, and
transposition, in which elements in the plaintext are rearranged.
The number of keys used
If the sender and receiver uses same key then it is said to be symmetric key (or)
single key (or) conventional encryption. If the sender and receiver use different keys
then it is said to be public key encryption.
The way in which the plain text is processed
A block cipher processes the input and block of elements at a time, producing
output block for each input block. A stream cipher processes the input elements
continuously, producing output element one at a time, as it goes along.
CRYPTANALYSIS
The process of attempting to discover X or K or both is known as cryptanalysis. The strategy
used by the cryptanalysis depends on the nature of the encryption scheme and the
information available to the cryptanalyst. There are various types of cryptanalytic attacks
based on the amount of information known to the cryptanalyst.
Cipher text only – A copy of cipher text alone is known to the cryptanalyst.
Known plaintext – The cryptanalyst has a copy of the cipher text and the corresponding
plaintext.
32
Chosen plaintext – The cryptanalysts gains temporary access to the encryption machine.
They cannot open it to find the key, however; they can encrypt a large number of suitably
chosen plaintexts and try to use the resulting cipher texts to deduce the key.
Chosen cipher text – The cryptanalyst obtains temporary access to the decryption machine,
uses it to decrypt several string of symbols, and tries to use the results to deduce the key.
COMMON VULNERABILITIES AND EXPOSURE (CVE)
Common Vulnerabilities and Exposures (CVE) is a dictionary-type reference
system or list for publicly known information-security threats. Every exposure or
vulnerability included in the CVE list consists of one common, standardized CVE name.
CVE is maintained by the MITRE Corporation and sponsored by the National Cyber
Security Division (NCSD) of the Department of Homeland Security. The CVE dictionary, a
shared information security vulnerability data list, may be viewed by the public.
In information security,
A VULNERABILITY is a software coding error that is used by hackers to enter an
information system and perform unauthorized activities while posing as an authorized
user.
AN EXPOSURE is a software error that allows hackers to break into a system. During an
exposure, attackers may gain information or hide unauthorized actions.
Items in the CVE list get names based on the year of their formal inclusion and the
order in which they were included in the list that year. The CVE helps computer security
tool vendors identify vulnerabilities and exposures. Before CVE, tools had proprietary
vulnerability databases, and no common dictionary existed. The key objective of CVE is
to help share data across different vulnerable databases and security tools.
CVE is used by the Security Content Automation Protocol, and CVE IDs are listed on
MITRE's system as well as the US National Vulnerability Database.
CVE IDENTIFIERS
33
MITRE Corporation's documentation defines CVE Identifiers (also called "CVE
names", "CVE numbers", "CVE-IDs", and "CVEs") as unique, common identifiers for
publicly known information-security vulnerabilities in publicly released software
packages. Historically, CVE identifiers had a status of "candidate" ("CAN-") and could then
be promoted to entries ("CVE-"), however this practice was ended some time ago and all
identifiers are now assigned as CVEs. The assignment of a CVE number is not a guarantee
that it will become an official CVE entry (e.g. a CVE may be improperly assigned to an
issue which is not a security vulnerability, or which duplicates an existing entry).
CVEs are assigned by a CVE Numbering Authority (CNA);[3] there are three primary types
of CVE number assignments:
1. The MITRE Corporation functions as Editor and Primary CNA
2. Various CNAs assign CVE numbers for their own products (e.g. Microsoft, Oracle,
HP, Red Hat, etc.)
3. A third-party coordinator such as CERT Coordination Center may assign CVE
numbers for products not covered by other CNAs
When investigating a vulnerability or potential vulnerability it helps to acquire a
CVE number early on. CVE numbers may not appear in the MITRE or NVD CVE databases
for some time (days, weeks, months or potentially years) due to issues that are
embargoed (the CVE number has been assigned but the issue has not been made public),
or in cases where the entry is not researched and written up by MITRE due to resource
issues. The benefit of early CVE candidacy is that all future correspondence can refer to
the CVE number. Information on getting CVE identifiers for issues with open source
projects is available from Red Hat.[4]
CVEs are for software that has been publicly released; this can include betas and
other pre-release versions if they are widely used. Commercial software is included in the
"publicly released" category, however custom-built software that is not distributed
would generally not be given a CVE. Additionally services (e.g. a Web-based email
provider) are not assigned CVEs for vulnerabilities found in the service (e.g. an XSS
vulnerability) unless the issue exists in an underlying software product that is publicly
distributed.
34
What is the new CVE-ID Syntax?
The new CVE-ID syntax is variable length and includes:
CVE prefix + Year + Arbitrary Digits
NOTE: The variable length arbitrary digits will begin at four (4) fixed digits and expand
with arbitrary digits only when needed in a calendar year, for example, CVE-YYYY-NNNN
and if needed CVE-YYYY-NNNNN, CVE-YYYY-NNNNNNN, and so on. This also means there
will be no changes needed to previously assigned CVE-IDs, which all include 4 digits.
This is a standardized text description of the issue(s). One common entry is:
“** RESERVED ** This candidate has been reserved by an organization or individual that
will use it when announcing a new security problem. When the candidate has been
publicized, the details for this candidate will be provided.”
This means that the entry number has been reserved by Mitre for an issue or a CNA
has reserved the number. So in the case where a CNA requests a block of CVE numbers in
advance (e.g. Red Hat currently requests CVEs in blocks of 500), the CVE number will be
marked as reserved even though the CVE itself may not be assigned by the CNA for some
time. Until the CVE is assigned AND Mitre is made aware of it (e.g. the embargo passes
and the issue is made public), AND Mitre has researched the issue and written a
description of it, entries will show up as "** RESERVED **"
CVE attempts to assign one CVE per security issue, however in many cases this would
lead to an extremely large number of CVEs (e.g. where several dozen cross-site scripting
vulnerabilities are found in a PHP application due to lack of use of htmlspecialchars() or
the insecure creation of files in /tmp). To deal with this there are guidelines (subject to
change) that cover the splitting and merging of issues into distinct CVE numbers. As a
general guideline consider issues to be merged, then split them by the type of
vulnerability (e.g. buffer overflow vs. stack overflow), then by the software version
affected (e.g. if one issue affects version 1.3.4 through 2.5.4 and the other affects 1.3.4
through 2.5.8 they would be SPLIT) and then by the reporter of the issue (e.g. Alice
reports one issue and Bob reports another issue the issues would be SPLIT into separate
CVE numbers). Another example is Alice reports a /tmp file creation vulnerability in
version 1.2.3 and earlier of ExampleSoft web browser, in addition to this issue several
35
other /tmp file creation issues are found, in some cases this may be considered as two
reporters (and thus SPLIT into two separate CVEs, or if Alice works for ExampleSoft and
an ExampleSoft internal team finds the rest it may be MERGE'ed into a single CVE).
Conversely issues can be merged, e.g. if Bob finds 145 XSS vulnerabilities in
ExamplePlugin for ExampleFrameWork regardless of the versions affected and so on they
may be merged into a single CVE.
COMPUTER SECURITY CONCERNS
People who fall in love with the Net do so for different reasons. Many love the
ability to quickly and cheaply keep up with friends and loved ones via e-mail, while others
love the vast oceans of information or the rush of playing Internet games.
However, it's likely that most Internet users share one thing in common as they
surf: the last thing on their minds is computer security.
While that's understandable, it's also a big mistake. It is important to remember
that surfing the Net comes with certain inherent risks. When you log onto the Net, you
step into the public arena, even if you're surfing from a bedroom computer while lounging
around in your skivvies!
There are as many bad guys in cyberspace as there are in everyday life, and those
shady characters are constantly prowling the Internet in search of new victims to scam.
However, the media often exaggerate these dangers. It is extremely unlikely
(though not impossible) that anyone reading this article will fall prey to an Internet crime,
and in truth the risks are not much greater than those associated with many fun activities.
Does the potential of breaking a bone keep you from enjoying your favorite ski
slope or bike trail? Of course not. Instead, the smart person uses the necessary caution
that will allow for a safe and enjoyable experience.
That ethos also applies to those who want to surf the Web safely. There are
countless ways that thieves and mischief makers can wreak havoc with your sense of
security, but there are just as many ways to keep intruders at bay via safe-surfing
techniques or security software.
Some of the Concerns/Issues of Computer Security
36
Hacking unauthorized access to or use of data, systems, server or networks, including any
attempt to probe, scan or test the vulnerability of a system, server or network or to breach
security or authentication measures without express authorization of the owner of the
system, server or network. Members of the University should not run computer programs
that are associated with hacking without prior authorisation. Obtaining and using such
programs is not typical of normal usage and may therefore otherwise be regarded as misuse.
Use of University owned computer equipment, including the network, for illegal activities
including copying Copyright material without permission. The vast majority of files shared
on P2P (peer-to-peer) networks violate copyright law because they were posted without
permission of the artist or label.
Sending abusive e-mails or posting offensive Web pages.
Creation or transmission of any offensive or indecent images.
Giving unauthorized access to University computing resources e.g. allowing an account to
be used by someone not authorized to use it.
Deliberately creating or spreading computer viruses or worms.
Unauthorized running of applications that involve committing the University to sharing its
computing resources, e.g. network bandwidth, in an uncontrolled and unlimited way.
To secure a computer system, it is important to understand the attacks that can be
made against it, and these threats can typically be classified into one of the categories
below:
Backdoors
A backdoor in a computer system, a cryptosystem or an algorithm, is any secret
method of bypassing normal authentication or security controls. They may exist for a
number of reasons, including by original design or from poor configuration. They may
also have been added later by an authorized party to allow some legitimate access, or by
an attacker for malicious reasons; but regardless of the motives for their existence, they
create a vulnerability.
Denial-of-service attack
Denial of service attacks are designed to make a machine or network resource
unavailable to its intended users. Attackers can deny service to individual victims, such
37
as by deliberately entering a wrong password enough consecutive times to cause the
victim account to be locked, or they may overload the capabilities of a machine or
network and block all users at once. While a network attack from a single IP address can
be blocked by adding a new firewall rule, many forms of Distributed denial of
service (DDoS) attacks are possible, where the attack comes from a large number of
points – and defending is much more difficult. Such attacks can originate from the zombie
computers of a botnet, but a range of other techniques are possible including reflection
and amplification attacks, where innocent systems are fooled into sending traffic to the
victim.
Direct-access attacks
Common consumer devices that can be used to transfer data surreptitiously.
An unauthorized user gaining physical access to a computer is most likely able to directly
download data from it. They may also compromise security by making operating
system modifications, installing software worms, key loggers, or covert listening devices.
Even when the system is protected by standard security measures, these may be able to
be by passed by booting another operating system or tool from a CD-ROM or other
bootable media. Disk encryption and Trusted Platform Module are designed to prevent
these attacks.
Eavesdropping
Eavesdropping is the act of surreptitiously listening to a private conversation,
typically between hosts on a network. For instance, programs such
as Carnivore and NarusInsight have been used by the FBI and NSA to eavesdrop on the
systems of internet service providers. Even machines that operate as a closed system (i.e.,
with no contact to the outside world) can be eavesdropped upon via monitoring the
faint electro-magnetic transmissions generated by the hardware; TEMPEST is a
specification by the NSA referring to these attacks.
Spoofing
Spoofing of user identity describes a situation in which one person or program
successfully masquerades as another by falsifying data.
38
Tampering
Tampering describes a malicious modification of products. So-called "Evil Maid"
attacks and security services planting of surveillance capability into routers[6] are
examples.
Privilege escalation
Privilege escalation describes a situation where an attacker with some level of
restricted access is able to, without authorization, elevate their privileges or access level.
So for example a standard computer user may be able to fool the system into giving them
access to restricted data; or even to "become root" and have full unrestricted access to a
system.
Phishing
Phishing is the attempt to acquire sensitive information such as usernames,
passwords, and credit card details directly from users. Phishing is typically carried out by
email spoofing or instant messaging, and it often directs users to enter details at a fake
website whose look and feel are almost identical to the legitimate one. Preying on a
victim's trusting, phishing can be classified as a form of social engineering.
INFORMATION SECURITY MEASURES
Information is one of the most valuable assets. The use of proper preventive
measures and safeguards can reduce the risk of potentially devastating security attacks,
which could cost you the future of your business. Some losses might be irrecoverable,
such as the loss of a business deal due to leaks of confidential data to your competitor.
CYBER CRIME SYNDICATES
Although the lone criminal mastermind still exists, these days most malicious
hacking attacks are the result of organized groups, many of which are professional.
Traditional organized crime groups that used to run drugs, gambling, prosecution, and
extortion have thrown their hats into the online money grab ring, but competition is
fierce, led not by mafiosos but several very large groups of professional criminals aimed
specifically at cybercrime.
39
Many of the most successful organized cybercrime syndicates are businesses that
lead large affiliate conglomerate groups, much in the vein of legal distributed marketing
hierarchies. In fact, today's cybercriminal probably has more in common with an Avon or
Mary Kay rep than either wants to admit.
Small groups, with a few members, still hack, but more and more, IT security pros
are up against large corporations dedicated to rogue behavior. Think full-time employees,
HR departments, project management teams, and team leaders.
SMALL-TIME CONS -- AND THE MONEY MULES AND LAUNDERS SUPPORTING THEM
Not all cybercriminal organizations are syndicates or corporations. Some are
simply entrepreneurial in nature, small businesses after one thing: money.
These malicious mom-and-pop operations may steal identities and passwords, or
they may cause nefarious redirection to get it. In the end, they want money. They initiate
fraudulent credit card or banking transactions and convert their ill-gotten gains into local
currency using money mules, electronic cash distribution, e-banking, or some other sort
of money laundering.
It's not hard to find money launders. There are dozens to hundreds of entities
competing to be the one that gets to take a large percentage cut of the illegally procured
loot. In fact, you'd be surprised at the competitive and public nature of all the other people
begging to do support business with Internet criminals. They advertise "no questions
asked," "bulletproof" hosting in countries far from the reaches of legal subpoenas, and
they offer public bulletin boards, software specials, 24/7 telephone support, bidding
forums, satisfied customer references, antimalware avoidance skills, and all the servicing
that helps others to be better online criminals. Many of these groups make tens of millions
of dollars each year.
Many of these groups and the persons behind them have been identified (and
arrested) over the past few years. Their social media profiles show happy people with big
houses, expensive cars, and content families taking foreign vacations. If they're the
slightest bit guilty from stealing money from others, it doesn't show.
40
Imagine the neighborhood barbeques where they tell neighbors and friends that
they run an "Internet marketing business" -- all the while social engineering their way to
millions to the consternation of IT security pros who have done just about everything you
can to protect users from themselves.
HACKTIVISTS
Whereas exploit bragging was not uncommon in the early days, today's cyber
criminal seeks to fly under the radar -- with the exception of the growing legions of
hacktivists.
These days IT security pros have to contend with an increasing number of loose
confederations of individuals dedicated to political activism, like the infamous
Anonymous group. Politically motivated hackers have existed since hacking was first
born. The big change is that more and more of it is being done in the open, and society is
readily acknowledging it as an accepted form of political activism.
Political hacking groups often communicate, either anonymously or not, in open
forums announcing their targets and hacking tools ahead of time. They gather more
members, take their grievances to the media to drum up public support, and act
astonished if they get arrested for their illegal deeds. Their intent is to embarrass
and bring negative media attention to the victim as much as possible, whether that
includes hacking customer information, committing DDoS (distributed denial of service)
attacks, or simply causing the victim company additional strife.
More often than not, political hacktivism is intent on causing monetary pain to its
victim in an attempt to change the victim's behavior in some way. Individuals can be
collateral damage in this fight, and regardless of whether one believes in the hacktivist's
political cause, the intent and methodology remain criminal.
INTELLECTUAL PROPERTY THEFT AND CORPORATE ESPIONAGE
While the likelihood of dealing with hacktivists may be low, most IT security pros
have to contend with the large group of malicious hackers that exist only to steal
intellectual property from companies or to perform straight-up corporate espionage.
41
The method of operations here is to break into a company's IT assets, dump all the
passwords, and over time, steal gigabytes of confidential information: patents, new
product ideas, military secrets, financial information, business plans, and so on. Their
intent is to find valuable information to pass along to their customers for financial gain,
and their goal is to stay hidden inside the compromised company's network for as long
as possible.
To reap their rewards, they eavesdrop on important emails, raid databases, and
gain access to so much information that many have begun to develop their own malicious
search engines and query tools to separate the fodder from the more interesting
intellectual property.
This sort of attacker is known as an APT (advanced persistent threat) or DHA
(determined human adversary). There are few large companies that have not been
successfully compromised by these campaigns.
MALWARE MERCENARIES
No matter what the intent or group behind the cybercrime, someone has to make
the malware. In the past, a single programmer would make malware for his or her own
use, or perhaps to sell. Today, there are teams and companies dedicated solely to writing
malware. They turn out malware intended to bypass specific security defenses, attack
specific customers, and accomplish specific objectives. And they're sold on the open
market in bidding forums.
Often the malware is multiphased and componentized. A smaller stub program is
tasked with the initial exploitation of the victim's computer, and once securely placed to
ensure it lives through a reboot, it contacts a "mothership" Web server for further
instructions. Often the initial stub program sends out DNS queries looking for the
mothership, itself often a compromised computer temporarily acting as a mothership.
These DNS queries are sent to DNS servers that are just as likely to be innocently infected
victim computers. The DNS servers move from computer to computer, just as the
mothership Web servers do.
42
Once contacted, the DNS and mothership server often redirect the initiating stub
client to other DNS and mothership servers. In this way, the stub client is directed over
and over (often more than a dozen times) to newly exploited computers, until eventually
the stub program receives its final instructions and the more permanent malicious
program is installed.
All in all, the setup used by today's malware writers makes it very difficult for IT
security pros to defend against their wares.
THE INCREASINGLY COMPROMISED WEB
At the most basic level, a website is simply a computer, just like a regular end-user
workstation; in turn, Webmasters are end-users like everyone else. It's not surprising to
find the legitimate Web is being increasingly littered with malicious JavaScript
redirection links.
But it's not entirely a matter of Webmasters' computers being exploited that's
leading to the rise in Web server compromises. More often, the attacker finds a weakness
or vulnerability in a website that allows them to bypass admin authentication and write
malicious scripts.
Common website vulnerabilities include poor passwords, cross-site scripting
vulnerabilities, SQL injection, vulnerable software, and insecure permissions. TheOpen
Web Application Security Project Top 10 list is the authority on how most Web servers
get compromised.
Many times it isn't the Web server or its application software but some link or
advertisement that gets hacked. It's fairly common for banner ads, which are often placed
and rotated by general advertising agencies, to end up infected. Heck, many times the
malware guys simply buy ad space on popular Web servers.
ALL-IN-ONE MALWARE
Today's sophisticated malware programs often offer all-in-one, soup-to-nuts
functionality. They will not only infect the end-user but also break into websites and
modify them to help infect more victims. These all-in-one malware programs often come
43
with management consoles so that their owners and creators can keep track of what the
botnet is doing, who they are infecting, and which ones are most successful.
Most malicious programs are Trojan horses. Computer viruses and worms have
long since ceased to be the most popular types of malware. In most cases, the end-user is
tricked into running a Trojan horse that's advertised as a necessary antivirus scan, disk
defragmentation tool, or some other seemingly essential or innocuous utility. The user's
normal defenses are fooled because most of the time the Web page offering the rogue
executable is a trusted site they've visited many times. The bad guys simply compromised
the site, using a host of tricks, and inserted a few lines of JavaScript that redirect the user's
browsers to the Trojan horse program.
Because many of the evildoers present themselves as businessmen from
legitimate corporations, complete with corporate headquarters, business cards, and
expense accounts, it's not always so easy to separate the legitimate ad sources from the
bad guys, who often begin advertising a legitimate product only to switch out the link in
the ad to a rogue product after the ad campaign is under way. One of the more interesting
exploits involved hackers compromising a cartoon syndicate so that every newspaper
republishing the affected cartoons ended up pushing malware. You can't even trust a
cartoon anymore.
Another problem with hacked websites is that the computers hosting one site can
often host multiple sites, sometimes numbering in the hundreds or thousands. One
hacked website can quickly lead to thousands more.
No matter how the site was hacked, the innocent user, who might have visited this
particular website for years without a problem, one day gets prompted to install an
unexpected program. Although they're surprised, the fact that the prompt is coming from
a website they know and trust is enough to get them to run the program. After that, it's
game over. The end-user's computer (or mobile device) is yet another cog in someone's
big botnet.
44
CYBER WARFARE
Nation-state cyber warfare programs are in a class to themselves and aren't
something most IT security pros come up against in their daily routines. These covert
operations create complex, professional cyber warfare programs intent on monitoring
adversaries or taking out an adversary's functionality, but as Stuxnet andDuqu show, the
fallout of these methods can have consequences for more than just the intended targets.
Crime and no punishment
Some victims never recover from exploitation. Their credit record is forever scarred by a
hacker's fraudulent transaction, the malware uses the victim's address book list to
forward itself to friends and family members, victims of intellectual property theft spend
tens of millions of dollars in repair and prevention.
The worst part is that almost none of those who use the above malicious attacks are
successfully prosecuted. The professional criminals on the Internet are living large
because the Internet isn't good at producing court-actionable evidence. It's anonymous
by default, and tracks are lost and covered up in milliseconds. Right now we live in the
"wild, wild West" days of the Internet. As it matures, the criminal safe havens will dry up.
Until then, IT security pros have their work cut out for them.
Definitions: Risk = Threat X Vulnerability
Being “at risk" is being exposed to threats.
Risks are subjective -- the potential to incur consequences of harm or loss
of target assets.
A Risk Factor is the likelihood of resources being attacked.
Threats are dangerous actions that can cause harm. The degree of
threat depends on the attacker's Skills, Knowledge, Resources, Authority, and
Motives.
Vulnerabilities are weaknesses in victims that allow a threat to become effective.
45
Who They Are
A rogue user is an authorized user who, without permission, accessing restricted
assets.
A bogie is an unauthorized user who subverts security systems.
A cracker breaks into others' computing facilities for their own personal gain - be
it financial, revenge, or amusement.
A hacktivistis a cracker with a cause. (Example of hactivism: Building Peekabooty
to get around governments blocking websites)
A terrorist uses fear to blackmail others into doing what they want.
White Hats are also called “ethical" hackers, such as the Axent (now Symantec)
Tiger Team
Black Hats disregard generally accepted social conventions and laws.
Script kiddie is a derogatory term for a wannabe cracker who lacks programming
skills and thus relies on prewritten scripts and toolkits for their exploits.
Journeyman is an experienced hacker: someone who has collected many tools
and made many connections.
A Puppet Master (wizard) produces exploits.
Malware is a generic term for malicious software such as trojan horses, worms,
and viruses.
Warez is a nickname for pirated software (illegal copies of copyrighted software).
Serialz are serial numbers illegally shared used to unlock software.
46
UNIT-2
Fundamentals of Information Security:
Key Elements of Networks, Logical Elements of Networks, Critical Information
Characteristics, Information States etc.
Work Effectively with Colleagues (NOS 9002)
KEY ELEMENTS OF NETWORKS
Computer networks share common devices, functions, and what features
including servers, clients, transmission media, shared data, shared printers and other
hardware and software resources, network interface card(NIC), local operating
system(LOS), and the network operating system (NOS).
Servers - Servers are computers that hold shared files, programs, and the network
operating system. Servers provide access to network resources to all the users of the
network. There are many different kinds of servers, and one server can provide several
functions. For example, there are file servers, print servers, mail servers, communication
servers, database servers, fax servers and web servers, to name a few.
Clients - Clients are computers that access and use the network and shared network
resources. Client computers are basically the customers (users) of the network, as they
request and receive services from the servers.
Transmission Media - Transmission media are the facilities used to interconnect
computers in a network, such as twisted-pair wire, coaxial cable, and optical fiber cable.
Transmission media are sometimes called channels, links or lines.
Shared data - Shared data are data that file servers provide to clients such as data files,
printer access programs and e-mail.
Shared printers and other peripherals -Shared printers and peripherals are hardware
resources provided to the users of the network by servers. Resources provided include
data files, printers, software, or any other items used by clients on the network.
Network Interface Card - Each computer in a network has a special expansion card
called a network interface card (NIC). The NIC prepares (formats) and sends data,
47
receives data, and controls data flow between the computer and the network. On the
transmit side, the NIC passes frames of data on to the physical layer, which transmits the
data to the physical link. On the receiver's side, the NIC processes bits received from the
physical layer and processes the message based on its contents.
Local Operating System - A local operating system allows personal computers to access
files, print to a local printer, and have and use one or more disk and CD drives that are
located on the computer. Examples are MS-DOS, UNIX, Linux, Windows 2000, Windows
98, Windows XP etc.
Network Operating System - The network operating system is a program that runs on
computers and servers, and allows the computers to communicate over the network.
Hub - Hub is a device that splits a network connection into multiple computers. It is like
a distribution center. When a computer requests information from a network or a specific
computer, it sends the request to the hub through a cable. The hub will receive the request
and transmit it to the entire network. Each computer in the network should then figure
out whether the broadcast data is for them or not.
Switch - Switch is a telecommunication device grouped as one of computer network
components. Switch is like a Hub but built in with advanced features. It uses physical
device addresses in each incoming messages so that it can deliver the message to the right
destination or port.
Like a hub, switch doesn't broadcast the received message to entire network, rather
before sending it checks to which system or port should the message be sent. In other
words, switch connects the source and destination directly which increases the speed of
the network. Both switch and hub have common features: Multiple RJ-45 ports, power
supply and connection lights.
LOGICAL ELEMENTS OF NETWORKS
A network element is usually defined as a manageable logical entity uniting one
or more physical devices. This allows distributed devices to be managed in a unified way
using one management system. According to Telecommunications Act of 1996, the term
`network element' means a facility or equipment used in the provision of a
telecommunications service. Such term also includes features, functions, and capabilities
48
that are provided by means of such facility or equipment, including subscriber numbers,
databases, signaling systems, and information sufficient for billing and collection or used
in the transmission, routing, or other provision of a telecommunications service.
With development of distributed networks, network management had become an
annoyance for administration staff. It was hard to manage each device separately even if
they were of the same vendor. Configuration overhead as well as misconfiguration
possibility were quite high. A provisioning process for a basic service required complex
configurations of numerous devices. It was also hard to store all network devices and
connections in a plain list. Network structuring approach was a natural solution.
CRITICAL INFORMATION CHARACTERISTICS
Availability
Availability enables users who need to access information to do so without
interference or obstruction, and to receive it in the required format.
Availability of information
Is accessible to any user.
Requires the verification of the user as one with authorized access to the
information.
The information, then, is said to be available to an authorized user when and
where needed and in the correct format.
Example:-
Consider the contents of a library
Research libraries that require identification before
entrance.
Librarians protect the contents of the library, so that it is
available only to authorized patrons.
49
The librarian must see and accept a patron’s proof of
identification before that patron has free and easy access to
the contents available in the bookroom.
Accuracy
Information is accurate
when it is free from mistakes or errors and
It has the value that the end user expects.
Information contains a value different from the user’s expectations due to
the intentional or unintentional modification of its content, it is no longer
accurate.
Example :-
Consider the checking account
Inaccuracy of the information in your checking account can
be caused by external or internal means.
If a bank teller, for instance, mistakenly adds or subtracts too
much from your account, the value of the information has
changed.
In turn, as the user of your bank account, you can also
accidentally enter an incorrect amount into your account
register. This also changes the value of the information.
Authenticity
Authenticity of information is the quality or state of being genuine or original,
rather than a reproduction or fabrication.
Information is authentic when it is the information that was originally
Created,
Placed,
Stored, or
Transferred.
Example :-
Consider for a moment some of the assumptions made about e-mail.
50
When you receive e-mail, you assume that a specific individual or group of
individuals created and transmitted the e-mail—you assume know the
origin of the e-mail. This is not always the case.
E-Mail spoofing, the process of sending an e-mail message with a modified
field, is a problem for many individuals today, because many times the field
modified is the address of the originator.
Spoofing the address of origin can fool the e-mail recipient into thinking
that the message is legitimate traffic.
In this way, the spoofer can induce the e-mail readers into opening e-mail
they otherwise might not have opened.
The attack known as spoofing can also be applied to the transmission of
data across a network, as in the case of user data protocol (UDP) packet
spoofing, which can enable unauthorized access to data stored on
computing systems.
Confidentiality
The confidentiality of information is the quality or state of preventing disclosure
or exposure to unauthorized individuals or systems.
Confidentiality of information is ensuring that only those with the rights and
privileges to access a particular set of information are able to do so, and that those
who are not authorized are prevented from obtaining access.
When unauthorized individuals or systems can view information, confidentiality
is breached.
To protect the confidentiality of information, you can use a number of measure:
Information classification
Secure documents storage
Application of general security policies
Education of information custodians and end users
Example:-
Ex: 1 A security is an employee throwing away a document containing
critical information without shredding it.
51
Ex: 2 A hacker who successfully breaks into an internal database of a Webbased organization and steals sensitive information about the clients such as
Names
Addresses and
Credit card numbers.
Integrity
The quality or state of being whole, complete, and uncorrupted is the integrity
of information.
The integrity of information is threatened when the information is exposed to
Corruption,
Damage,
Destruction, or
Other disruption of its authentic state.
The threat of corruption can occur while information is being stored or
transmitted.
Many computer viruses and worms have been created with the specific purpose
of corrupting data.
For this reason the key method for detecting the virus or worm
1. First Key methodology is to look for changes in file integrity as shown by the size
of the file.
2. Another key methodology for assuring information integrity is through file
hashing.
With file hashing, a file is read by a special algorithm that uses the value
of the bits in the file to compute a single large number called a Hash value.
The hash value for any combination of bits is different for each
combination.
Utility
The Utility information is the quality or state of having value for some purpose or
end.
52
Information has value when it serves a particular purpose. This means that if
information is available, but not in a format meaningful to the end user, it is not
useful.
Possession
The Possession of information is the quality or state of having ownership or
control of some object or item.
Information is said to be in possession if one obtains it, independent of format or
other characteristic.
A breach of confidentiality always results in a breach of possession, a breach of
possession does not always result in a breach of confidentiality.
Example:-
Assume a company stores its critical customer data using an encrypted file
system.
An employee, who has quit, decides to take a copy of the tape backups to
sell the customer records to the competition.
The removal of the tapes from their secure environment is a breach of
possession, because the data is encrypted, neither the employee nor
anyone else can read it without the proper decryption methods, therefore
there is no breach of confidentiality.
INFORMATION STATES
Different States of the Information that is processed between two or more
Communication entities.
53
UNIT-3
Data Leakage:
What is Data Leakage and Statistics, Data Leakage Threats, Reducing the Risk of Data Loss,
Key Performance Indicators (KPI), Database Security etc.
WHAT IS DATA LEAKAGE?
Definition: Data Leakage is the unauthorized transmission of data (or
information) from within an organization to an external destination or recipient. This
may be electronic, or may be via a physical method. Data Leakage is synonymous with the
term Information Leakage. The reader is encouraged to be mindful that unauthorized
does not automatically mean intentional or malicious. Unintentional or inadvertent data
leakage is also unauthorized.
Definition: Data leakage is defined as the accidental or unintentional distribution
of private or sensitive data to an unauthorized entity.
Sensitive data in companies and organizations include intellectual property (IP),
financial information, patient information, personal credit-card data, and other
information depending on the business and the industry.
Data leakage poses a serious issue for companies as the number of incidents and
the cost to those experiencing them continue to increase. Data leakage is enhanced by the
fact that transmitted data (both inbound and outbound), including emails, instant
messaging, website forms, and fi le transfers among others, are largely unregulated and
unmonitored on their way to their destinations.
Furthermore, in many cases, sensitive data are shared among various
stakeholders such as employees working from outside the organization’s premises (e.g.,
on laptops), business partners, and customers. This increases the risk that confidential
information will fall into unauthorized hands. Whether caused by malicious intent or an
inadvertent mistake by an insider or outsider, exposure of sensitive information can
seriously hurt an organization.
54
The potential damage and adverse consequences of a data leakage incident can be
classified into two categories: direct and indirect losses.
Direct losses refer to tangible damage that is easy to measure or to estimate
quantitatively.
Indirect losses, on the other hand, are much harder to quantify and have a much
broader impact in terms of cost, place, and time [Bunker, 2009].
Direct losses include violations of regulations (such as those protecting customer
privacy) resulting in fines, settlements or customer compensation fees; litigation
involving lawsuits; loss of future sales; costs of investigation and remedial or restoration
fees.
Indirect losses include reduced share price as a result of negative publicity;
damage to a company’s goodwill and reputation; customer abandonment; and exposure
of intellectual property (business plans, code, financial reports, and meeting agendas) to
competitors.
Data leakage can occur in many forms and in any place. In a 2009 Data Breach
Investigation Report (by the Verizon Business RISK team), 90 data breaches occurring in
2008 were analyzed. In addition to the significant number of compromised records (285
million), the investigation revealed other interesting aspects of this problem as well. One
of the most intriguing aspects revealed by the compiled data is that most breaches have
been caused by external parties (74%). However, the number of breaches resulting
exclusively from the actions of insiders is still significant (20%). Incidents in which
business partners have been involved account for 32% of the total. According to the
nonprofit consumer organization Privacy Rights Clearinghouse, a total of 227,052,199
individual records containing sensitive personal information were involved in security
breaches in the United States between January 2005 and May 2008.
STATISTICS
Some recent high-profile leakage incidents, selected from www.datalossdb.org,
are presented in Table 3.1. This sample of recent leakage incidents emphasizes the
55
difficulty of providing a “one-stop-shop” silver-bullet solution for preventing all data
leakage scenarios.
TABLE 3.1 DATA LEAKAGE INCIDENTS
Date Organization Description
Oct. 2008 UPS A UPS employee’s laptop
containing payroll
information for 9000 U.K.
employees was stolen. In
response UPS announced
that it will encrypt all data
stored on all the company’s
mobile devices.
Sept. 2011 Science Applications
International Corp
Backup tapes stolen from a
car containing 5,117,799
patients’ names, phone
numbers, Social Security
numbers, and medical
information.
Oct. 2009 U.S. National Archive U.S. National Archive and
Records administration
improperly disposed of
hard drives containing 76
million names, addresses,
and SSNs of US military
veterans.
July 2008 Google Data were stolen, not from
Google offices, but from the
headquarters of an HR
outsourcing company, Colt
56
Express. The thieves broke
in and stole company
computers containing
unencrypted data
including names, addresses
and SSNs of Google
employees. As a result,
Google terminated its
partnership with Colt
Express.
Jan. 2008 Stockport Primary Care
Trust (U.K.)
A member of staff lost a
USB memory stick
containing data extracted
from the medical records of
patients. The data were
being carried personally to
avoid sending them by email because the employee
thought that they would be
more secure.
June 2004 AOL An employee of America
Online Inc. stole the
computerized employee
identification code of
another AOL worker to
gain access to AOL’s
subscriber data. He then
stole 92 million email
addresses belonging to 30
million subscribers and
sold them to spammers.
57
July 2009 American Express DBA stole a laptop
containing thousands of
American Express card
numbers. The DBA
reported it stolen, “…he
(DBA) was one of the few
who could have possibly
downloaded all their
account holders’
information, including the
PIN numbers used to
access money from ATM
machines at various
banks.”
2007 Wagner Resource Group An employee of a McLean
investment firm decided to
trade some music using a
file-sharing network while
using the company
computer. In doing so, he
inadvertently opened the
private files of his firm,
Wagner Resource Group, to
the public. Social Security
numbers, dates of birth,
and names of 2,000 clients
were exposed.
Aug. 2007 Nuclear Laboratory in Los
Alamos
An employee of the U.S.
nuclear laboratory in Los
Alamos transmitted
confidential information by
58
email. The incident was
classified as a serious
threat to the country’s
nuclear safety
Feb. 2008 Eli Lilly & Co. One of Eli Lilly & Co.’s
subcontracted lawyers at
Philadelphia-based Pepper
Hamilton mistakenly
emailed confidential Eli
Lilly discussions to Times
reporter Alex Berenson
(instead of to Bradford
Berenson, her co-counsel),
costing Eli Lilly nearly $1
billion.
Sep. 2007 Scarborough & Tweed The Web servers of
Scarborough & Tweed, a
company that sells
corporate gifts online, were
compromised and
information about 570
customers may have been
accessed using an SQL
injection attack. The
information included
customers’ names,
addresses, telephone
numbers, account
numbers, and credit card
numbers.
59
May 2009 Alberta Health Services Personal health
information on thousands
of Albertans was skimmed
from the Alberta Health
Services Edmonton
network as a computer
virus infected the network
and stole medical
information on 1,582
people, including
laboratory test results and
diagnostic imaging reports.
The virus captured
information from a
computer screen and then
transmitted it to an
external website.
Apr. 2009 Prague hotel (Czech
Republic)
A data leakage incident
occurred in a Prague hotel
(Czech Republic). The fl
ight details and passport
numbers of approximately
200 EU leaders were
leaked by accident. The
data was related to an EUUS summit held in Prague
and attended by U.S.
President Obama.
Jan. 2009 Heartland Payment
Systems
Malicious software/hack
compromised tens of
millions of credit and debit
60
card transactions. “The
data include the digital
information encoded onto
the magnetic stripe …
thieves can fashion
counterfeit credit cards…”
2003 British Intelligence A British intelligence
report in the form of a
Word document containing
the names of the authors of
a paper in its revision log
metadata was cited by the
United States in a speech to
the United Nations. The
metadata showed that the
report was in fact written
by U.S. researchers
DATA LEAKAGE THREATS
The above sample also indicates that enterprises should broaden the focus of their
security efforts beyond merely securing network perimeters and internal hosts from
classic threats i.e., viruses, Trojan horses, worms, D/DoS attacks and intrusions.
Classified into two types:
1. Internal threats –or inadvertent?
2. External threats.
61
INTERNAL THREATS – INTENTIONAL OR INADVERTENT?
According to data compiled from EPIC.org and PerkinsCoie.com, 52% of Data
Security breaches are from internal sources compared to the remaining 48% by external
hackers.
The noteworthy aspect of these figures is that, when the internal breaches are examined,
the percentage due to malicious intent is remarkably low, at less than 1%. The corollary
of this is that the level of inadvertent data breach is significant (96%). This is further
deconstructed to 46% being due to employee oversight, and 50% due to poor business
process.
INTENTIONAL INTERNAL DATA LEAKAGE OR SABOTAGE
Whilst the data presented suggests the main threat to internal data leakage is from
inadvertent actions, organizations are nevertheless still at risk of intentional
unauthorized release of data and information by internal users. The methods by which
insiders leak data could be one or many, but could include mediums such as Remote
Access; Instant Messaging; email; Web Mail; Peer-to-Peer; and even File Transfer
Protocol. Use of removable media, hard copy, etc is also possible.
Motivations are varied, but include reasons such as corporate espionage, financial
reward, or a grievance with their employer. The latter appears to be the most likely.
According to a study conducted by The US Secret Service and CERT, 92% of insider
related offences was following a “negative work-related event”. Of these, the offenders
were predominantly male (96%) and the majority held technical roles (86%). Whilst the
consequences of these attacks related not just to data, of the attacks studied, 49%
included the objective of “sabotaging information and/or data”. An example of such an
attack is described in the USSS/CERT study as follows, note how the characteristics match
the findings above (highlighted in bold):
“An application developer, who lost his IT sector job as a result of company
downsizing, expressed his displeasure at being laid off just prior to the Christmas
holidays by launching a systematic attack on his former employer’s computer network.
………. He also sent each of the company’s customers an email message advising that the
62
Web site had been hacked. Each email message also contained the customer’s usernames
and passwords for the Web site.”
UNINTENTIONAL INTERNAL DATA LEAKAGE
A significant amount of data security breaches are due to either employee
oversight or poor business process. This presents a challenge for businesses as the
solution to these problems will be far greater than simply deploying a secure content
management system. Business processes will need to be examined, and probably reengineered; personnel will need to be retrained, and a cultural change may be required
within the organization. These alone are significant challenges for a business. A recent
example of what is probably unintentional featured an Australian employment agency’s
web site publishing “Confidential data including names, email addresses and passwords
of clients” from its database on the public web site. An additional embarrassing aspect of
this story was the fact that some of the agency’s staff made comments regarding
individuals, which were also included. For instance, “a client is referred to as a ‘retard’
and in another a client is called a ‘lazy good for nothing’”. This alone raises the possibility
of legal action from those clients.
INTERNAL DATA LEAKAGE VECTORS
INSTANT MESSAGING / PEER-TO-PEER
Many organizations allow employees to access Instant Messaging from their
workstations or laptops, with a 2005 estimate suggesting 80% of large companies in the
US having some form of Instant Messaging. This includes products such as MSN
Messenger; Skype; AOL; GoogleTalk; ICQ; and numerous others. Many of the clients
available (and all of those mentioned here) are capable of file transfer. It would be a
simple process for an individual to send a confidential document (such as an Excel file
containing sensitive pricing or financial data) to a third party. Equally a user could divulge
confidential information in an Instant Messaging chat session.
63
Instant Messaging is also increasingly becoming a vector for Malware. For example the
highly popular Skype has been targeted in recent times.Recent examples of malware
targeting Skype include W32/Pykse.worm.b, W32/Skipi.A and W32.Pykspa.D
Instant Messaging Data Leakage Vector
Peer-to-peer (P2P) also presents a significant threat to data confidentiality. Popular P2P
clients include eDonkey and BitTorrent, with the latter appearing to have between 50 and
75% share of global P2P traffic.It has recently been described as “new national security
risk” by Retired General Wesley K. Clark, who is a board member with an organization
that scans through peer-to-peer networks for confidential or sensitive data. He
commented “We found more than 200 classified government documents in a few hours
search over P2P networks” and “We found everything from Pentagon network server
secrets to other sensitive information on P2P networks that hackers dream about”. A few
moments consideration regarding the implications of these findings will yield the issue
of potential widespread distribution and availability of the data. The number of potential
users on P2P networks that could access the confidential or sensitive data is enormous.
64
EMAIL
Traditional email clients, such as Microsoft Outlook, Lotus Notes, Eudora, etc are
ubiquitous within organizations. An internal user with the motivation could email a
confidential document to an unauthorized individual as an attachment. They may also
choose to compress and / or encrypt the file, or embed it within other files in order to
disguise its presence. Steganography may also be utilized for this purpose. Alternatively,
instead of attaching a document, text could be copied into the email message body.
Email also represents a vector for inadvertent disclosure due to employee
oversight or poor business process. An employee could attach the wrong file
inadvertently, select the wrong recipient in the email, or even be tricked into sending a
document through social engineering.
Email Data Leakage Vector
WEB MAIL
Web Mail is well entrenched with users. Gmail, Yahoo, and Hotmail are popular
examples. It represents another way for an individual to leak confidential data, either as
an attachment or in the message body. Because Web Mail runs over HTTP/S a firewall
may allow it through un-inspected as port 80 or 443 will in most organizations be
65
allowed, and the connection is initiated from an internal IP address. HTTPS represents a
more complex challenge due to the encryption of the traffic.
WEB LOGS / WIKIS
Web Logs (Blogs) are web sites where people can write their thoughts, comments,
opinions on a particular subject. The blog site may be their own, or a public site, which
could include the input from thousands of individuals. Blogs could be used by someone
to release confidential information, simply through entering the information in their blog.
However, they would most likely be able to be tracked, so this is perhaps a less likely
medium. A wiki site is “a collaborative website which can be directly edited by anyone
with access to it”, such as wikipedia.org. These sites are often available to most internet
users around the world, and contain the possibility that confidential information may be
added to a wiki page.
MALICIOUS WEB PAGES
Web sites that are either compromised or are deliberately malicious, present the
risk of a user’s computer being infected with malware, simply by visiting a web page
containing malicious code with an OS/browser that contains a vulnerability. The malware
could be in the form of a key logger, Trojan, etc. With a key logger the risk of data theft is
introduced. A recent example was the Miami Dolphin’s (host to the NFL Super Bowl XLI)
web site being compromised. Users with vulnerabilities MS06-014 and MS07-004 would
download a key logger/backdoor, “providing the attacker with full access to the
compromised computer”.
FILE TRANSFER PROTOCOL (FTP)
FTP is included in this discussion as it represents another (perhaps less likely)
method for an individual to release information. It is straightforward to install and
configure a basic FTP server external to the organization (or it may be a special folder on
a competitor’s FTP server). The individual then merely has to install a publicly available
FTP client and upload the file or files to the server. This method could even utilize a “dead
drop” public FTP site hosted off-shore, where the third party also has access. As FTP is a
popular protocol there is the likelihood it will be allowed through the firewall. FTP is
66
probably more likely to be used in intentional leakage than unintentional leakage, due to
the fact that uploading a file to an FTP server is generally not something an average user
performs on a daily basis, nor would do inadvertently, as compared to attaching a file to
an email.
FTP Data Leakage Vector
REMOVABLE MEDIA / STORAGE
Symantec reported in March 2007 that “Theft or loss of a computer or data storage
medium, such as a USB memory key, made up 54 percent of all identity theft-related data
breaches”. In March 2007, the price for a 2GB USB Flash Drive (brand withheld) was
US$23.19 on Amazon.com (roughly 1.1c per MB). This is very cheap removable storage.
Copying a large spreadsheet or document (say 500MB) onto a USB key is effortless. The
user merely needs to insert the device, open Windows Explorer, and drag and drop the
target files to the device. The key is then removed, placed in the employees pocket and
walked out of the building. Alternatively, if the user has a CD or DVD burner on their
laptop or desktop, they can copy the information that way. Due to their small size, USB
keys are also easy to lose. Even if the copying of data onto the key is legitimate, the risk
67
exists that the key could be lost by the user and found by a third party. Other forms of
USB mass storage include portable hard drives, digital cameras, and even musical devices
such as an Apple iPod – one model contains an 80GB hard drive. A proof-of-concept
application called slurp.exe, written by Abe Usher, has the ability to automatically copy
all business documents (e.g. .doc, .xls, .ppt, etc) from a PC connected to a device such as
an iPod that is running the application. Various Firewire and Bluetooth devices are also
capable of holding corporate data. Are companies going to ban employees from bringing
their iPod to work because of the threat of data leakage? It seems unlikely.
EXTERNAL THREATS
According to the Privacy Rights Clearinghouse, in 2005 US companies exposed the
personal information of over 53 million people.
DATA THEFT BY INTRUDERS
An ever-popular topic in the media is the electronic break-in to an organization by
intruders including the theft of sensitive information. There have been numerous stories
in the press of the theft of credit card information by intruders (note that the press often
refer to intruders as hackers). In 2005 it was estimated that as many as 40 Million credit
card numbers were stolen by intruders from MasterCard, VISA, American Express, and
other credit card brands.
More recently, Monster.com lost hundreds of thousands (potentially as many as
1.3 million) of job site users’ IDs to intruders “…hackers grabbed resumes and used
information on those documents to craft personalized "phishing" e-mails to job seekers.”
This particular event holds significant concern, because resumes contain a significant
amount of information about an individual, including their full name, address, phone
number(s), employment history, interests, and possibly contact details of third parties,
such as referees. This allows for particularly targeted, and if crafted well, believable
phishing attacks, or perhaps even more audacious social engineering attacks such as
phone calls. Another scenario to consider is that phishers may start developing
fraudulent employment web sites, and attempt to attract users to send their resumes
68
directly to them. This is slightly outside the scope of this paper however it is important
that this possibility is pointed out, as I believe it is a vector yet to emerge.
SQL INJECTION
Web sites that use an SQL server as the back end database may be vulnerable to
SQL Injection attacks, if they fail to correctly parse user input. This is usually a direct
result of poor coding. SQL Injection attacks can result in content within the database
being stolen. For example, a site that does not correctly sanitize user input may cause a
server error to occur. For example:
The initial action of the attack could be to enter a single quote within the input
data in a POST element on a website, which may generate an SQL statement as follows:
SELECT info
FROM table
WHERE search = ‘mysearch’’
Note the additional quote mark. Should the application not sanitize the user input
correctly a server error may occur. This indicates to the attacker that the user input is not
being sanitized and that the site is vulnerable to further exploitation. Further trial and
error by the attacker could eventually reveal table names, field names, and other
information, that, once obtained, will allow them to construct an SQL query within the
POST element that yields sensitive data
MALWARE
In recent years, the SirCam worm would, after infecting a computer, scan through
the My Documents folder and send a file at random out via email to the user’s email
contacts. If malware is classified as a zero day threat, and there is no signature yet
available, there is a higher likelihood that the malware will evade inbound gateway
protection measures and desktop anti-virus. Once this malware infects a PC, it may then
initiate outbound communications, potentially sending out files which may contain
sensitive data. One aspect to be mindful of is that to a firewall, the traffic is from an
69
internal source. This is an important point, because most firewalls will not restrict traffic
that is initiated internally via an acceptable protocol.
Malware Data Leakage Vector
PHISHING AND PRE-PHISHING
Phishing sites, and the spam email that solicits visits to them, pose a threat to
organizations, and not just individuals. Phishing spam may be received at peoples’ work
email address. Should they be fooled into visiting the phishing site, then they may lose
personal information and or financial information. It is also possible that the spam
received directs them to a site hosting malware, which could download a key logger (as
previously discussed). Phishers have recently been using the lure of tax returns from
various taxation offices as a means to fool people. For example in Australia, the Australian
Tax Office has been targeted by phishers.29 Phishing is of course a form of social
70
engineering (which will be discussed shortly). Phishing activity has increased
significantly in the past ten months, to a peak of almost 45,000 validated phishing sites in
May 2007. There was a significant decline after May 2007 (back to November / December
2006 levels). Figures obtained from phishtank.com follow on the next page.
PRE-PHISHING
Pre-phishing is emerging as a new method used by phishers, initially as a
reconnaissance attack. Instead of attempting to directly obtain credentials for a financial
site, social networking and email sites are targeted. The attack seeks to obtain username
and password combinations, on the (likely) assumption that in many cases, users will use
the same or similar combinations on other web sites. The second part of the attack is to
conduct a CSS History Hack, where the phishers can determine whether the user has
visited specified sites.31 The CSS History Hack uses the ‘a: visited’ component in CSS
which alters the behavior of links that have been visited.32 Banking sites visited by users
may be obtained, and the phishers can then visit these and attempt to gain access using
the compromised credential combinations.
SOCIAL ENGINEERING
Without going into excessive detail about Social Engineering, some of the common
scenarios and risks include:
• Phone calls to Help Desk from a social engineer claiming to be an employee in
another office, desperate for a password reset.
• Phone calls to unsuspecting employees from social engineer tricking them into
sending out sensitive information. Individuals that would not recognize the fact
that the information is sensitive are prime targets.
• Phishing emails and similar scams which rely on ignorance, stupidity, gullibility,
greed, and many other human frailties, to trick people into divulging private data.
The sad reality is that they do work. We would not be deluged by so much spam if
they didn’t.
71
PHYSICAL THEFT
Physical theft of computer systems, laptops, backup tapes, and other media also
presents a data leakage risk to organizations. This may be due to poor physical security
at an organization’s premises or poor security practice by individuals. For instance, a
laptop may be left unattended in the back seat of a car whilst the owner pays for petrol,
allowing an opportunistic theft to occur. Also possible is the mass theft of laptops from
within an organizations premises after hours, should the business fail to secure the
laptops overnight.
REDUCING THE RISK OF DATA LOSS/ MITIGATION
1. TECHNOLOGY BASED MITIGATION
SECURE CONTENT MANAGEMENT / INFORMATION LEAK PROTECTION
This approach utilizes a number of techniques including lexical analysis of traffic
passing through a specific device on the network, and fingerprinting. A gateway based
device examines the content of the message looking for specific keywords, patterns, and
regular expressions. It and then categorizes the traffic and acts on it accordingly (e.g. pass,
quarantine, notify, block, etc).
Keyword filtering will detect specific words or phrases. For example, an email
exchange between two employees in conflict with one another could trigger a
“Threatening Language” alert. Confidential information being sent out as an attachment
may be detected with the word “Confidential” or phrase “Commercial in confidence” for
instance.
Dictionaries extend keyword filtering through the inclusion of pre-built wordlists.
Regular Expressions will detect patterns of characters or digits. For example a
sixteen digit sequence could represent a credit card number. It is essential that an
organization have a clear understanding of the format of data contained within its
databases in order to develop appropriate expression lists. For example, a customer
72
record within a database will have a number of fields. Each field will have a specified
maximum length and will have a name.
Regular Expressions can be tailored to identify such fields being transmitted. This
may also mitigate the risk of SQL injection attacks from retrieving confidential
information from databases accessible via the web.
Data fingerprinting is a technology that will analyze data at rest and build a
database of fingerprints. Fingerprinting involves the creation of a number of hashes for a
given document. This collection of hashes forms the document “fingerprint” and will be
stored in a database. Fingerprinting is done initially on a document “at rest”, and is
achieved by either having a user drop a document into a special network folder, or by
agents deployed on workstations which catalogue and fingerprint documents on the
workstations. If a user attempts to send out a document that has been fingerprinted, the
outbound document will be fingerprinted and compared to the database of known
hashes. Detection should extend to replicas of the document, or if the document has been
modified.
Clustering is a technique which focuses on groups of documents which are similar,
by correlating words, word counts, and patterns across the group of documents.
Implementation of a Secure Content Management Solution will help mitigate the
threat of confidential information being released through electronic channels (including
email, FTP, HTTP, Web mail, IM) and also, with some vendors, removable media, for both
intentional and inadvertent activity. For instance Australian software developer Lync
Software, produces a suite of products which control the ability of users to copy files to
removable media37. These products provide sufficient granularity to define policies for
specific users or computers, groups, or Active Directory domains, and what file types they
can copy to removable media (e.g. USB thumb drive). For example it is then possible to
prevent a specific computer user from copying Microsoft Word documents onto a USB
device.
As an example, the screenshot below displays the creation of a rule to prevent MS
Word files (.doc) from being copied onto a USB. Having selected the appropriate file type
the ‘Write’ permission can then be set to Block, as seen below:
73
USB Protection 1
The administrator may then specify the type of device. As can be seen below, some of the
possibilities include USB Storage, iPods, DVD/CDR, Scanners, etc.
USB Protection 2
Solutions such as LyncRMS utilize an agent based approach, where software
agents are installed on desktops and laptops and run in the background, quietly enforcing
company policy. When selecting a Secure Content Management solution it is important to
give consideration to the following:
74
• Rate of False Positives. High rates of FP will result in increased workload in analyzing
and responding to events. They may also result in reduced productivity due to the
prevention of legitimate documents and messages from reaching employees.
• Rate of False Negatives. As with other security measures, a high rate of false negatives
will lead to a false sense of security, plus potentially placing the organization in jeopardy
from confidential data which is leaked without being identified.
• Ability to scan attachments. Solutions that merely analyze the content of email or web
pages will fail to detect confidential data leaked via file attachments.
• Range of file formats able to be scanned.
• Ability to fingerprint data at rest and in motion.
• Ability to detect data flooding, file type/format manipulation, hidden or embedded data,
and graphical files (e.g. print screens)
Other considerations include
• Provision of in-built compliance mechanisms, for SOX, HIPAA, and GLBA. Certain
vendors provide this capability, where the product will look for general and related
terms, and codes relevant to any or all of these compliance programs.
• Whether or not an agent based approach is used.
• Inspection of all content – i.e. Headers, body, attachments
• Communication mediums – i.e. email (including platforms), IM/P2P, FTP, HTTP (Web
mail and Blogs), and VOIP.
• Automated enforcement of policy – i.e. the solution should automatically block any
traffic that violates the policies, preventing the protected data being leaked.
• Reporting and auditing capabilities – these are essential as they provide management
with the knowledge of any unauthorized activity (be it intentional or inadvertent), and
provides a mechanism to demonstrate the compliance with any relevant regulations.
75
Advantages: High granularity of control; pre-defined compliance requirements built-in;
wide range of coverage.
Disadvantages: Initial cost may be high; ongoing management may require dedicated
resources, so ongoing costs may also be high.
REPUTATION SYSTEMS
A growing solution to Spam/Phishing/etc is to deploy a Reputation based solution
where the email sender must have an acceptable reputation score in order to be allowed.
This type of system effectively supersedes older Black-list / White-list systems (including
Real Time varieties from organizations such as ORBS.org). Reputation solutions will
mitigate the risk of receiving email from untrustworthy or unknown sources.
A definition of ‘reputation’: “the estimation in which a person or thing is held,
especially by the community or public generally”.
A key point with this definition is the use of the phrase “community or public
generally”. This conveys the sense that reputation is achieved by widespread assessment,
rather than one or two individual’s opinions (which in the past is how a company could
be added to a Blacklist).
Today, we now have a number of vendors offering what are called “Reputation
Services” and it is certain that more vendors will follow suit.
One of the key differences with the current generation is the use of legitimate
corporate email to build a positive reputation, as well as building negative reputations
for poor behavior. Blacklists and ORBS essentially only provide half the picture - negative
reputation. They may also block entire domains or net blocks rather than one offending
IP address.
To achieve this, Reputation Services capture and analyze billions of email every
month from customer reporting nodes (the thousands of appliances deployed worldwide). This email is correlated and analysis performed to determine a number of
behavioral attributes for each sender. The more email received from a sender the better
the reputation score can become – or – the worse the reputation can become.
76
Now is an appropriate time to reflect upon the earlier point with regard to reputation
– “community or public generally”. Traffic from thousands of sources worldwide is
correlated to determine the behavior and then reputation of sender IP addresses. For
example, IronPort’s Reputation Filters features a network of over 100,000 organizations
that feed email data into their reputation service correlation engines.
If the behavior deviates from what is normal, the reputation of the sender will be
updated, and distributed to the vendor’s customer base. For example if a cable modem
home user is infected with a spam engine, their email activity will jump significantly. The
traffic from their IP address will be detected as being unusually high (as previously it
would have been negligible) and the reputation score altered. This information is then
distributed back to the customer base. After this point, any requests for connection from
the offending IP address will be denied (subject to the configuration of customer
appliances). Should the infected system then be cleaned, the traffic will fall back to a
minimal level, and reputation systems will detect this change and improve the reputation
score, to the point where the IP address will be accepted.
Advantages: Remove additional processing by identifying which IP addresses to
terminate connections with; reduce spam and malicious email and web sites. Reputation
services can detect malicious traffic emerging from new IP addresses and domains. It will
complement existing AntiVirus/AntiSpyware products.
Disadvantages: May involve additional cost, probably on a subscription basis.
THIN CLIENT / VIRTUAL DESKTOP INFRASTRUCTURE
Companies should consider the possibility of utilizing thin clients, which provide
users with a ‘walled garden’ containing only the applications they need to do their work,
via a diskless (and USBless) terminal. This will prevent a user from copying data to
portable media, however if they have email or web access as an application (most likely),
it will still be possible for them to send information out via email, web mail, or blog.
Examples of vendors that provide Thin Client systems are hp, Sun, and Wyse Technology.
Another solution is Application Streaming, featuring a cut-down virtual operating system
that includes authorized applications being streamed to a users PC, either within the
77
network or from a remote location. This may also be used within a Thin Client
environment.
MINIMIZING LEAKAGE VIA CD OR DVD
To prevent data being copied onto CD or DVD an organization could have a policy
of providing systems without these devices. Laptops may present more of a challenge, as
most are supplied with a DVD writer nowadays. However one solution could be to
implement a Standard Operating Environment which removes burning media from
systems, and monitor for systems that have unauthorized installation of burning software
by users.
ANTIVIRUS / ANTISPYWARE / ANTIPHISHING
Traditional AntiVirus / AntiSpam / AntiPhishing products should prevent, in most
cases, users from either being infected by malicious code which may steal data, or from
visiting a Phishing site. All products in this space feature malware signature databases,
and some feature some form of “intelligence” - a heuristic detection mechanism to
identify malware which does not have a known signature - aimed at capturing zero day
threats
PROTECTIVE MARKINGS
Some vendors develop products that provide Protective Markings. Protective
Markings address the issue of Security Classification errors (or intentional actions).
This solution requires the sender of an email to explicitly state what level of
classification the email they are sending belongs to, and the recipient must have a security
clearance of at least the level of classification specified. This helps to protect data from
inadvertent or intentional unauthorized release. An email marked Top Secret will not be
able to be sent to a user with a classification of Secret or below.
Often used by Governments (for example the UK and Australian Governments),
different classification models are available. For example, in the UK, the classification
model includes the classifications TOP SECRET, SECRET, CONFIDENTIAL, and
RESTRICTED.45 The Australian Government has a more elaborate list, including
78
PERSONAL, UNCLASSIFIED, IN-CONFIDENCE, PROTECTED, HIGHLY-PROTECTED,
RESTRICTED, CONFIDENTIAL, SECRET, and TOP SECRET. Some further definitions are
also available for some of these classification levels.
Corporations may also benefit from this, especially with regard to protection of
intellectual property and confidential communications via email. A classification model
including PERSONAL, UNOFFICIAL, UNCLASSIFIED, X-IN-CONFIDENCE, PROTECTED,
and HIGHLY PROTECTED may be suitable for business.
Protective Markings are implemented via modification of the subject line, and Internet
message header (X-Protective-Marking). Protective Markings are also available for
Microsoft Office products.
Advantages: Enforces the flow of email between classification levels, preventing
inadvertent or intentional sending of classified information to unauthorized recipients.
Disadvantages: Cost will be involved; initial deployment cost involved; users may be
resistant to change.
APPLICATION PROXY FIREWALLS
Stateful Inspection firewalls will examine traffic at the Transport or Network layer
and either allow it to pass through, or block it based on its rule set. For example a rule
that allows inbound SMTP connections to a mail server may look something like this:
access-list 101 permit tcp any host 10.1.2.3 eq smtp
This rule will examine the packet headers to ensure that the conditions in the rule
are satisfied, however this type of firewall does not examine the payload. As such Stateful
Inspection does not apply the same rigor as a genuine Application Proxy Firewall, which
works on all seven layers of the OSI model, and examines the payload of each packet.
Application Proxy Firewalls in essence strip down the traffic, and re-assemble it again,
analyze the behavior, only sending it to its destination if acceptable. A number of popular
protocols are understood by the Application Proxy Firewall, based on RFCs, and should
an application not comply with the expected behavior, the traffic will stop. The
connection from the source is terminated at the Application Proxy Firewall, analyzed, and
if acceptable another connection is made between the Application Proxy Firewall and the
79
destination. Hence there is no direct connection established between source and
destination (which is not the case with Stateful Inspection). Examples of Application
Proxy Firewalls include Secure Computing’s Sidewinder48. Readers should be aware of
the difference between a true Application Proxy Firewall, and a Stateful Inspection
Firewall that also utilizes application attack signatures. The latter may not prevent a zeroday application attack as there will be no signature, whereas the Application Proxy
Firewall will prevent the attack despite the signature of the attack being unknown,
because the behavior does not comply with acceptable standards. When deciding
between these types of firewall readers should carefully evaluate the performance of an
application proxy firewall against a stateful inspection firewall with application
signatures enabled, rather than a stateful inspection firewall without application
signatures.
80
KEY PERFORMANCE INDICATORS (KPI)
A Key Performance Indicator is a measurable value that demonstrates how
effectively a company is achieving key business objectives. Organizations use KPIs at
multiple levels to evaluate their success at reaching targets. High-level KPIs may focus on
the overall performance of the enterprise, while low-level KPIs may focus on processes
in departments such as sales, marketing or a call center.
What makes a KPI effective?
A KPI is only as valuable as the action it inspires. Too often, organizations blindly
adopt industry-recognized KPIs and then wonder why that KPI doesn't reflect their own
business and fails to affect any positive change. One of the most important, but often
81
overlooked, aspects of KPIs is that they are a form of communication. As such, they abide
by the same rules and best-practices as any other form of communication. Succinct, clear
and relevant information is much more likely to be absorbed and acted upon.
In terms of developing a strategy for formulating KPIs, your team should start with
the basics and understand what your organizational objectives are, how you plan on
achieving them, and who can act on this information. This should be an iterative process
that involves feedback from analysts, department heads and managers. As this fact
finding mission unfolds, you will gain a better understanding of which business processes
need to be measured with KPIs and with whom that information should be shared.
Being SMART about your KPIs
One way to evaluate the relevance of a KPI is to use the SMART criteria. The letters
are typically taken to stand for specific, measurable, attainable, relevant,time-bound.
In other words:
Is your objective Specific?
Can you Measure progress towards that goal?
Is the goal realistically Attainable?
How Relevant is the goal to your organization?
What is the Time-frame for achieving this goal?
Seven Characteristics of effective KPIs
NonFinancial
They are non-financial measures (not expressed in dollars, yen, pounds, Euro, etc.)
Timely They are measured frequently (e.g., 24/7, daily or weekly)
CEO focus They are acted upon by the CEO and senior management team
82
Simple All staff understand the measure and what corrective action is required
Team-based
Responsibility can be assigned to a team or a cluster of teams who work closely
together
Significant
impact
They affect more than one of the organization’s top Critical Success Factors and
more than one balanced scorecard perspective
Limited dark
side
They encourage appropriate action - i.e., they have been tested to ensure they have
a positive impact on performance (whereas poorly thought through measures can
lead to dysfunctional behaviour)
IDENTIFYING KPIS OF ORGANIZATION
Performance indicators differ from business drivers and aims (or goals). A school might
consider the failure rate of its students as a key performance indicator which might help
the school understand its position in the educational community, whereas a business
might consider the percentage of income from returning customers as a potential KPI.
The key stages in identifying KPIs are:
Having a pre-defined business process (BP).
Having requirements for the BPs.
Having a quantitative/qualitative measurement of the results and comparison with
set goals.
Investigating variances and tweaking processes or resources to achieve short-term
goals.
Key performance indicators (KPIs) are ways to periodically assess the
performances of organizations, business units, and their division, departments and
employees. Accordingly, KPIs are most commonly defined in a way that is
understandable, meaningful, and measurable. They are rarely defined in such a way such
83
that their fulfillment would be hampered by factors seen as non-controllable by the
organizations or individuals responsible. Such KPIs are usually ignored by organizations.
A KPI can follow the SMART criteria. This means the measure has a Specific purpose for
the business, it is Measurable to really get a value of the KPI, the defined norms have to
be Achievable, the improvement of a KPI has to be Relevant to the success of the
organization, and finally it must be Time phased, which means the value or outcomes are
shown for a predefined and relevant period.
In order to be evaluated, KPIs are linked to target values, so that the value of the measure
can be assessed as meeting expectations or not.
DATABASE SECURITY
All organizations-public, governmental or private, small or large-depend on
computerized information systems for carrying out their daily activity. At the heart of
each such information system, there is a database. At a very general level, we can define
a database as a persistent collection of related data, where data are facts that have an
implicit meaning. For instance, an employee's name, social security number, or date of
birth are all facts that can be recorded in a database. Typically, a database is built to store
logically interrelated data representing some aspects of the real world, which must be
collected, processed, and made accessible to a given user population. The database is
constructed according to a data model which defines the way in which data and
interrelationships between them can be represented. The collection of software
programs that provide the functionalities for defining, maintaining, and accessing data
stored in a database is called a database management system (DBMS).
A database can be seen at different abstraction levels. Typically a three-level view
is adopted (see Figure 1) containing an internal level , describing the physical storage of
the database; a conceptual (or logical level ) providing the users with a high level
description of the real world that the database represents; and an external level
describing the views that different users or applications have on the stored data. The
internal level maps the logical objects supported by the data model to the physical objects
(files) of the underlying operating system (see Figure 2).
84
Beside access and processing functionalities, each DBMS must also provide
security functionalities to ensure the secrecy, integrity, and availability of the stored data.
Providing secrecy means ensuring that data will not be disclosed to unauthorized users.
Providing integrity means ensuring that data will not be modified in an unauthorized or
improper way.
In particular, integrity ensures that the stored data correctly reflect the real world.
85
Providing availability means ensuring that the database will always be accessible by
legitimate users for the accesses they are authorized for.
Since ultimately a database is mapped to (i.e., stored as) files of the underlying
operating system, one may think that a DBMS does not need to deal with security as
security functionalities of the operating system would suffice. This is not true, however,
since at the operating system level the data interrelationships and their semantics are
lost and therefore security restrictions exploiting concepts of the data model cannot be
enforced. Some of the differences between databases and operating systems that make it
necessary for a DBMS to support security features are as follows.
Protection level: A DBMS usually needs to protect data at a fine granularity level
(e.g., a record of a file), while an operating system protects data at the file level.
Object differences: There is a greater variety of object types in a DBMS than in an
operating system. The typical object type in an operating system is a file; in a DBMS there
can be relations (tables), tuples (rows within a table), attributes (columns within a table),
indexes, metadata, and others.
Data interrelationships: A database may include many logical objects with complex
semantic interrelationships that must be protected. By contrast, the number of physical
objects that the operating system protects is less and no semantic interrelationships are
supported.
Dynamic versus static objects: Data objects in a DBMS can be obtained by
dynamically aggregating data from different physical objects in an operating system. By
contrast, files tend to be more static making their protection easier.
Lifetime of data: The lifetime and frequency of access of data in a DBMS is quite
different than the lifetime of data stored as files in an operating system.
User views of data: While in an operating system, users are either granted or
denied access to data (files), in a DBMS it is possible to give access to a portion of an object
by defining different views for different users.
Because of these differences, it is clear that some security requirements must be
supported by the DBMS itself. Of course, the DBMS can rely on basic security services
86
provided by the underlying operating system. Typical security services provided by the
operating system that can be exploited by the DBMS are physical security controls,
authentication and auditing. Physical security protects against intentional or accidental
threats, like fire or natural disasters. Physical security measures also control the physical
access to the computer system on which the database is hosted. Examples of physical
measures are the use of locks, security guards, badges, and alarms. Authentication is a
means of verifying the identity of a party to another, and is a prerequisite for DBMS
security controls to ensure that the correct identity of users is being considered (i.e., users
are who they claim to be). The simplest form of authentication is based on the use of
passwords: users state their identity with a login identifier and provide a secret
password. Finally, auditing is the post facto evaluation of a system's activities, which must
therefore be properly logged. Auditing services can be used to perform online analysis to
determine possible security violations and to recover the correct state of the database in
the case integrity has been compromised.
The overall DBMS/OS architecture is depicted in Figure 3. In this chapter, we
mainly concentrate on basic security services that are available to users in commercial
DBMSs for access control and integrity constraints enforcement. Since these controls
cannot cope with Trojan horse attacks, we include a brief description of the multilevel
secure DBMSs.
87
ACCESS CONTROL POLICIES
Access control policies define the rules according to which access to the database
objects is regulated. The most popular class of access control policies is represented by
discretionary access control (DAC) policies, where the word discretionary characterizes
the fact that users can be given the ability of passing their privileges to others.
Discretionary access control policies are based on authorizations rules. An authorization
rule states that a subject has the privilege to exercise a given action on a given object. The
kind (and granularity) of subjects, objects, and actions that can be referenced in
authorizations may be different in different systems.
Subjects: Subjects are the entities to which authorizations can be granted.
Typically, subjects are users (i.e., identifiers corresponding to human entities). User
groups can also be defined to which authorizations can be granted; authorizations
granted to a group can be enjoyed by all its members. Discretionary access control can be
extended with role-based capabilities allowing the definition of roles to which privileges
can be granted. Roles are granted to users, and users can dynamically activate and
deactivate the roles received, thereby turning on and off the corresponding privileges.
Intuitively, a role identifies a task, and corresponding privileges, that users need to
execute to perform organizational activities. While groups are set of users, roles are set
of privileges. Note the difference between groups and roles. Groups are static: users
cannot enable and disable group memberships (and corresponding privileges) at their
will. By contrast, roles are dynamic and can be activated and deactivated upon explicit
request by users.
Objects: Objects are the entities to be protected. Typically, objects correspond to
information container (tables or portion of it) or procedures. In DBMS systems, different
granularity levels can be supported spanning from the whole database to the single
element (e.g., a specific employee's salary) in it.
Actions: Actions define the specific operations that subjects can execute on
objects. Actions to be supported include the operations corresponding to the basic read,
write, delete, create, and execute, which can take on different names in relational
database systems (for instance, read operations correspond to SELECT actions).
88
Authorizations: Authorizations define which accesses are to be allowed. The
simplest form of authorization is a triple (subject, object, action) specifying that subject
is authorized to exercise action on object.
89
UNIT-4
Information Security Policies, Procedures and Audits:
Information Security Policies-Necessity-Key Elements and Characteristics, Security Policy
Implementation, Configuration, Security Standards-Guidelines and Frameworks etc.
INFORMATION SECURITY POLICIES-NECESSITY-KEY ELEMENTS AND CHARACTERISTICS
INFORMATION SECURITY POLICIES
Information Security Policy /ISP/ is a set or rules enacted by an organization to
ensure that all users or networks of the IT structure within the organization’s domain
abide by the prescriptions regarding the security of data stored digitally within the
boundaries the organization stretches its authority.
An ISP is governing the protection of information, which is one of the many assets
a corporation needs to protect. The present writing will discuss some of the most
important aspects a person should take into account when contemplates developing an
ISP. Putting to work the logical arguments of rationalization, one could say that a policy
can be as broad as the creators want it to be: Basically, everything from A to Z in terms of
IT security, and even more. For that reason, the emphasis here is placed on a few key
elements, but you should make a mental note of the liberty of thought organizations have
when they forge their own guidelines.
ELEMENTS OF INFORMATION SECURITY POLICY
PURPOSE
Institutions create ISPs for a variety of reasons:
To establish a general approach to information security
To detect and forestall the compromise of information security such as misuse of
data, networks, computer systems and applications.
To protect the reputation of the company with respect to its ethical and legal
responsibilities.
90
To observe the rights of the customers; providing effective mechanisms for
responding to complaints and queries concerning real or perceived noncompliances with the policy is one way to achieve this objective.
SCOPE
ISP should address all data, programs, systems, facilities, other tech infrastructure,
users of technology and third parties in a given organization, without exception.
The four components of security documentation are policies, standards,
procedures, and guidelines. Together, these form the complete definition of a mature
security program. The Capability Maturity Model (CMM), which measures how robust
and repeatable a business process is, is often applied to security programs. The CMM
relies heavily on documentation for defining repeatable, optimized processes. As such,
any security program considered mature by CMM standards needs to have well-defined
policies, procedures, standards, and guidelines.
• Policy is a high-level statement of requirements. A security policy is the primary way in
which management’s expectations for security are provided to the builders, installers,
maintainers, and users of an organization’s information systems.
• Standards specify how to configure devices, how to install and configure software, and
how to use computer systems and other organizational assets, to be compliant with the
intentions of the policy.
• Procedures specify the step-by-step instructions to perform various tasks in accordance
with policies and standards.
• Guidelines are advice about how to achieve the goals of the security policy, but they are
suggestions, not rules. They are an important communication tool to let people know how
to follow the policy’s guidance. They convey best practices for using technology systems
or behaving according to management’s preferences.
SECURITY POLICIES
A security policy is the essential foundation for an effective and comprehensive
security program. A good security policy should be a high-level, brief, formalized
91
statement of the security practices that management expects employees and other
stakeholders to follow. A security policy should be concise and easy to understand so that
everyone can follow the guidance set forth in it.
In its basic form, a security policy is a document that describes an organization’s
security requirements. A security policy specifies what should be done, not how; nor does
it specify technologies or specific solutions. The security policy defines a specific set of
intentions and conditions that will help protect an organization’s assets and its ability to
conduct business. It is important to plan an approach to policy development that is
consistent, repeatable, and straightforward.
A top-down approach to security policy development provides the security
practitioner with a roadmap for successful, consistent policy production. The policy
developer must take the time to understand the organization’s regulatory landscape,
business objectives, and risk management concerns, including the corporation’s general
policy statements. As a precursor to policy development, a requirements mapping effort
may be required in order to incorporate industry-specific regulation. Chapter 3 covered
several of the various regulations as well as best practice frameworks that security policy
developers may need to incorporate into their policies.
A security policy lays down specific expectations for management, technical staff,
and employees. A clear and well-documented security policy will determine what action
an organization takes when a security violation is encountered. In the absence of clear
policy, organizations put themselves at risk and often flounder in responding to a
violation.
• For managers, a security policy identifies the expectations of senior management
about roles, responsibilities, and actions that should be taken by management with
regard to security controls.
• For technical staff, a security policy clarifies which security controls should be
used on the network, in the physical facilities, and on computer systems.
• For all employees, a security policy describes how they should conduct
themselves when using the computer systems, e-mail, phones, and voice mail.
92
A security policy is effectively a contract between the business and the users of its
information systems. A common approach to ensuring that all parties are aware of the
organization’s security policy is to require employees to sign an acknowledgement
document. Human Resources should keep a copy of the security policy documentation on
file in a place where every employee can easily find it.
SECURITY POLICY DEVELOPMENT
When developing a security policy for the first time, one useful approach is to focus on
the why, who, where, and what during the policy development process:
1. Why should the policy address these particular concerns? (Purpose)
2. Who should the policy address? (Responsibilities)
3. Where should the policy be applied? (Scope)
4. What should the policy contain? (Content)
For each of these components of security policy development, a phased approach is used.
PHASED APPROACH
If you approach security policy development in the following phases, depicted in Figure
5-1, the work will be more manageable:
1. Requirements gathering
• Regulatory requirements (industry specific)
• Advisory requirements (best practices)
• Informative requirements (organization specific)
2. Project definition and proposal based on requirements
3. Policy development
4. Review and approval
5. Publication and distribution
93
6. Ongoing maintenance (and revision)
After the security policy is approved, standards and procedures must be
developed in order to ensure a smooth implementation. This will require the policy
developer to work closely with the technical staff to develop standards and procedures
relating to computers, applications, and networks.
SECURITY POLICY CONTRIBUTORS
Security policy should not be developed in a vacuum. A good security policy forms
the core of a comprehensive security awareness program for employees, and its
development shouldn’t be the sole responsibility of the IT department. Every department
that has a stake in the security policy should be involved in its development, not only
because this enables them to tailor the policy to their requirements, but also because they
will be responsible for enforcing and communicating the policies related to each of their
specialties. Different groups and individuals should participate and be represented in
order to ensure that everyone is on board, that all are willing to comply, and that the best
interests of the entire organization are represented. Figure 5-2 shows some example
contributors to the security policy.
When creating a security policy, the following groups may be represented:
94
• Human Resources The enforcement of the security policy, when it involves
employee rewards and punishments, is usually the responsibility of the HR department.
HR implements discipline up to and including termination when the organization’s
policies are violated. HR also obtains a signature from each employee certifying that they
have read and understood the policies of the organization, so there is no question of
responsibility when employees don’t comply with the policy.
• Legal Often, an organization that has an internal legal department or outside
legal representation will want to have those attorneys review and clarify legal points in
the document and advise on particular points of appropriateness and applicability, both
in the organization’s home country and overseas. All organizations are advised to have
some form of legal review and advice on their policies when those policies are applied to
individual employees.
• Information Technology Security policy tends to focus on computer systems,
and specifically on the security controls that are built into the computing infrastructure.
IT employees are generally the largest consumers of the policy information.
• Physical Security Physical Security (or Facilities) departments usually
implement the physical security controls specified in the security policy. In some cases,
the IT department may manage the information systems components of physical security.
95
SECURITY POLICY AUDIENCE
The intended audience for the security policies is all the individuals who handle
the organization’s information, such as:
• Employees
• Contractors and temporary workers
• Consultants, system integrators, and service providers
• Business partners and third-party vendors
• Employees of subsidiaries and affiliates
• Customers who use the organization’s information resources
Figure 5-3 shows a representation of some example security policy audience
members. Technology-related security policies generally apply to information resources,
including software, web browsers, e-mail, computer systems, workstations, PCs, servers,
mobile devices, entities connected on the network, software, data, telephones, voice mail,
fax machines, and any other information resources that could be considered valuable to
the business.
Organizations may also need to implement security policy contractually with
business partners and vendors. They may also need to release a security policy statement
to customers.
96
POLICY CATEGORIES
Security policies can be subdivided into three primary categories:
• Regulatory For audit and compliance purposes, it is useful to include this
specific category. The policy is generally populated with a series of legal statements
detailing what is required and why it is required. The results of a regulatory requirements
assessment can be incorporated into this type of policy.
• Advisory This policy type advises all affected parties of business-specific policy
and may include policies related to computer systems and networks, personnel, and
physical security. This type of policy is generally based on security best practices.
• Informative This type of policy exists as a catch-all to ensure that policies not
covered under Regulatory and Advisory are accounted for. These policies may apply to
specific business units, business partners, vendors, and customers who use the
organization’s information systems.
The security policy should be concise and easy to read, in order to be effective. An
incomprehensible or overly complex policy risks being ignored by its audience and left to
gather dust on a shelf, failing to influence current operational efforts. It should be a series
of simple, direct statements of senior management’s intentions.
The form and organization of security policies can be reflected in an outline format
with the following components:
• Author The policy writer
• Sponsor The Executive champion
• Authorizer The Executive signer with ultimate authority
• Effective date When the policy is effective; generally when authorized
• Review date Subject to agreement by all parties; annually at least
• Purpose Why the policy exists; regulatory, advisory, or informative
• Scope Who the policy affects and where the policy is applied
97
• Policy What the policy is about
• Exceptions Who or what is not covered by the policy
• Enforcement How the policy will be enforced, and consequences for not
following it
• Definitions Terms the reader may need to know
• References Links to other related policies and corporate documents
FRAMEWORKS
The topics included in a security policy vary from organization to organization
according to regulatory and business requirements. We refer to these topics together as
a framework.
Organizations may prefer to take a control objective–based approach to creating
a security policy framework. For instance, government agencies may take a FISMA-based
approach. The Federal Information Security Management Act of 2002 imposes a
mandatory set of processes that must follow a combination of Federal Information
Processing Standards (FIPS) documents, the NIST Special Publications 800 series, and
other legislation pertinent to federal information systems.
POLICY CATEGORIES
NIST Special Publication 800-53, Recommended Security Controls for Federal
Information Systems and Organizations, control objectives are organized into 18 major
categories.
Control objective subsets exist for each major control category and equal at least
170 control objectives. NIST SP 800-53 is a good starting point for any organization
interested in making sure that all the basic control objectives are met regardless of the
industry and whether it is regulated.
ADDITIONAL REGULATIONS AND FRAMEWORKS
An organization that must comply with HIPAA (described in Chapter 3) may map
NIST SP 800-53 control objectives to the HIPAA Security Rule. HIPAA categorizes security
98
controls (referred to as safeguards) into three major categories: Administrative, Physical,
and Technical. As an example, CFR Part 164.312 section (c)(1), which requires protection
against improper alteration or destruction of data, is a HIPAA required control that maps
to NIST 800-53 System and Information Integrity controls.
Some organizations may wish to select a framework based on COBIT (Control
Objectives for Information and related Technology). COBIT is an IT governance
framework and supporting toolset that allows managers to bridge the gap between
control requirements, technical issues, and business risks. Developing policy from a
COBIT framework may take considerable collaboration with the Finance and Audit
departments. Other organizations may need to combine COBIT with ITIL (IT
Infrastructure Library) to ensure that service management objectives are met. ITIL is a
cohesive best-practices framework drawn from the public and private sectors
internationally. It describes the organization of IT resources to deliver business value,
and documents processes, functions, and roles in IT service management.
Still other organizations may wish to follow the OCTAVE (Operationally Critical
Threat, Asset, and Vulnerability Evaluation) framework. OCTAVE is a risk-based strategic
assessment and planning technique for security from CERT (Carnegie Mellon University).
And yet others may need to incorporate the ISO Family (27001 and 27002) from the
International Standards Organization. ISO is a framework of standards that provides best
practices for information security management.
Depending on which regulated industry an organization finds itself in, it is
important to take the time to select an appropriate framework and to map out the
regulatory and business requirements in the first phase of development.
SECURITY MANAGEMENT POLICIES
Managers have responsibilities for security just as employees do. Detailing
expectations for managers is crucial to ensure compliance with senior management’s
expectations.
Employee Nondisclosure Agreements All employees must sign a nondisclosure
agreement that specifies the types of information they are prohibited from revealing
outside the organization. The agreement must be signed before the employee is allowed
99
to handle any private information belonging to the organization. Employees must be
made aware of the consequences of violating the agreement, and signing the agreement
must be a condition of employment, such that the organization may not employ anyone
who fails to sign the agreement.
Nondisclosure Agreements All business partners wishing to do business with
the organization must sign a nondisclosure agreement that specifies the types of
information they are prohibited from revealing outside the organization. The agreement
must be signed before the business partner is allowed to view, copy, or handle any private
information belonging to the organization.
System Activity Monitoring All internal information system servers must be
constantly monitored, 24×7×365, by trained security analysts. At least the following
activities must be monitored:
• Unauthorized access attempts
• Root or Administrator account usage
• Nonstandard behavior of services
• Addition of modems and peripherals to systems
• Any other relevant security events
Software Installation Monitoring All software installed on all servers and enduser systems must be inventoried periodically. The inventory must contain the following
information:
• The name of each software package installed on each system
• The software version
• The licensing status
System Vulnerability Scanning
All servers and end-user systems must be periodically scanned for known
vulnerabilities. The vulnerability scan must identify the following:
100
• Services and applications running on the system that could be exploited to
compromise security
• File permissions that could grant unauthorized access to files
• Weak passwords that could be easily guessed by people or software
Security Document Lifecycle All security documents, including the corporate
security policy, must be regularly updated and changed as necessary to keep up with
changes in the infrastructure and in the industry.
Security Audits Periodic security audits must be performed to compare existing
practices against the security policy.
Penetration Testing Penetration testing must be performed on a regular basis to
test the effectiveness of information system security.
Security Drills Regular “fire drills” (simulated security breaches, without advance
warning) must take place to test the effectiveness of security measures.
Extranet Connection Approval All extranet connections require management
approval before implementation.
Non-Employee Access to Corporate Information Non-employees (such as
spouses) are not allowed to access the organization’s information resources.
New Employee Access Approval Manager approval is required for new
employee access requests.
Employee Access Change Approval Manager approval is required for employee
access change requests.
Contractor Access Approval Manager approval is required for contractor access
requests.
Employee Responsibilities The following categories of responsibilities are
defined for corporate employees. These categories consist of groupings of
responsibilities that require differing levels of access to computer systems and networks.
101
They are used to limit access to computers and networks based on job requirements, to
implement the principles of least privilege and separation of duties.
• General User
• Operator
• System Administrator
• Customer Support Staff
• Customer Engineer
• Management
Security Personnel Responsibilities The following categories of responsibilities
are defined for security personnel. These categories consist of groupings of
responsibilities within the security organization that require differing levels of access to
security information and systems based on job function, in order to implement the
principles of least privilege and separation of duties.
• Security Architect
• Facility Security Officer
• Security Manager
• Technical Security Administrator
Employee Responsibility for Security All corporate employees are responsible
for the security of the computer systems they use and the physical environment around
them.
Sensitive HR Information Sensitive HR information (such as salaries and
employee records) must be separated and protected from the rest of the corporate
network.
Security Policy Enforcement Enforcement of this corporate security policy is the
responsibility of the corporate Human Resources department.
102
HR New Hire Reporting HR must report required information about new hires
to system administrators one week in advance of the new employee’s start date.
HR Termination Reporting HR must report required information about
terminations to system administrators one week before the termination date, if possible,
and no later than the day of termination.
Contractor Information Reporting HR is responsible for managing contractor
information and providing this information to system administrators.
Background Checks HR must perform background checks on new employee
applicants.
Reference Checks HR must perform reference checks on new employee
applicants.
SECURITY STANDARDS
A standard is somewhat more detailed than a policy. Standards describe how to
comply with the policy, and because they are associated with policies, they should be
considered mandatory. Standards are the extension of the policy into the real world—
they specify technology settings, platforms, or behaviors. Security managers responsible
for IT infrastructure will usually spend more time writing standards than they spend on
policy.
Much of the information contained in Chapter 21 and 22 of this book pertains to
settings for Unix and Windows systems. Those settings would typically be the level of
detail that is included in standards. Compare the information in those chapters against
the set of policy statements listed in the previous section of this chapter. You’ll see that
policy statements are simple, direct, and somewhat general. Standards interpret the
policy to the level of specifics needed by a subject matter expert.
SECURITY STANDARD EXAMPLE
The following is a sample of a security standard. This is part of a standard for
securing Linux servers. It is intended to establish a baseline set of configurations that
would establish common settings across all Linux platforms on the network. Notice that
103
the level of detail is very deep—only an experienced system administrator would be able
to understand some of these instructions. That is typical of a standard, as opposed to a
policy, which everyone should be able to understand regardless of their level of expertise.
1. PURPOSE
1.1. The purpose of this standard is to define the software and hardware
configurations required to secure Linux servers. It defines security settings for operating
system and software that are required by policy.
2. SCOPE
2.1. This standard is to be used by system administrators responsible for
administration of computers using the Red Hat Enterprise Linux operating system.
3. RESPONSIBILITIES
3.1. The Security Manager is responsible for defining this standard. 3.2. The Server
team is responsible for following this standard.
4. STANDARD
4.1. SERVICES
4.1.1. Specific services that are required for general operation of the
systems and resident vendor applications services are to be reviewed for security
risks and approved by the Security Manager.
4.1.2. Services that are not needed are to be disabled during boot.
4.2. INITIAL PASSWORD AND LOGIN SETTINGS
4.2.1. All accounts for system administrators are to be added as local
accounts in the /etc/passwd and /etc/shadow files. NIS is not to be used for
password verification.
4.2.2. Privileged user accounts require IT system operations and
applications manager approval before being placed on system.
4.2.3. No developer accounts are allowed on production servers.
104
4.2.4. All administration user accounts are to be set with 90 day password
aging, 7 day notification of password expiration, and 7 day password minimum.
4.2.5. All root and application administrator accounts are to be reviewed
and will have a scheduled password change by operations administrators once
every 90 days.
4.2.6. The default login setting is to be set to lock out the session after 3
failed password login attempts.
4.2.7. Default password settings must enforce a minimum of 8 characters.
4.2.8. The ability to log in directly over the network to the root account
must be disabled.
4.3. SENDMAIL
4.3.1. The sendmail service is to be disabled on all non-mail servers unless
required by an application running on the system. Applications requiring
Sendmail services must first be approved by IT system operations manager.
4.4. BANNER/NOTICE
4.4.1. Configure the login banner with the standard warning notice.
4.5. LOGGING
4.5.1. Turn on logging for Internet standard services.
4.5.2. Turn on logging for LOG_AUTHPRIV facility.
4.5.3. Log connection tracing to inetd/xinetd and messages sent to AUTH
facility. 4.5.4. Set logging for sudo activities.
4.5.5. Send all kernel authorization, debug, and daemon notices to a syslog
server for monitoring, reviewing, and archiving
SECURITY PROCEDURES
Procedures are step-by-step instructions to perform a specific task.
105
SECURITY PROCEDURE EXAMPLE
In this example, notice that the level of detail is more specific than that found in
both policies and standards. The procedure is a set of instructions that a system
administrator would perform when sitting at the keyboard of the computer being built.
Most people will not understand this information—it is very specialized, and intended
only for someone who is a system administrator. The type of specialized information
found in a security procedure is usually very job-specific.
1. PURPOSE
1.1. This procedure is intended for the security installation of Apache web servers.
It defines the steps necessary to ensure a secure installation that complies with
security policy.
2. SCOPE
2.1. This procedure is to be used by system administrators responsible for
installing the Apache HTTP server.
3. RESPONSIBILITIES
3.1. The Security Manager is responsible for defining this procedure.
3.2. Any system administrator installing Apache HTTP server on the network is
responsible for following this procedure.
4. APACHE WEB SERVER SECURITY PROCEDURE
4.1. Compile and install the server software as follows:
4.1.1. ./configure --prefix=/usr/local/apache --disable-module=all --
serveruid=apache --server-gid=apache --enable-module=access --enablemodule=log_ config --enable-module=dir --enable-module=mime --enablemodule=auth
4.1.2. make
4.1.3. su
106
4.1.4. umask 022
4.1.5. make install
4.1.6. chown -R root:sys /usr/local/apache
4.2. The next step is to limit Apache processes’ access to the filesystems. Start this
process by creating a new root directory structure under the /chroot/httpd directory:
4.2.1. mkdir -p /chroot/httpd/dev
4.2.2. mkdir -p /chroot/httpd/etc
4.2.3. mkdir -p /chroot/httpd/var/run
4.2.4. mkdir -p /chroot/httpd/usr/lib
4.2.5. mkdir -p /chroot/httpd/usr/libexec
4.2.6. mkdir -p /chroot/httpd/usr/local/apache/bin
4.2.7. mkdir -p /chroot/httpd/usr/local/apache/logs
4.2.8. mkdir -p /chroot/httpd/usr/local/apache/conf
4.2.9. mkdir -p /chroot/httpd/www
4.3. Next, create the special device file: /dev/null:
4.3.1. ls -al /dev/null
4.3.2. crw-rw-rw- 1 root wheel 2, 2 Mar 14 12:53 /dev/null
4.3.3. mknod /chroot/httpd/dev/null c 2 2
4.3.4. chown root:sys /chroot/httpd/dev/null
4.3.5. chmod 666 /chroot/httpd/dev/null
4.4. Add the following line to the /etc/rc.conf file:
4.4.1. syslogd_flags=“-l /chroot/httpd/dev/log”
4.5. Restart the system.
107
4.6. Copy the main httpd program into the new directory tree with all
necessary binaries and libraries, as follows:
4.6.1. localhost# ldd /usr/local/apache/bin/httpd
4.7. Copy the files to the new root directory structure:
4.7.1. cp /usr/local/apache/bin/httpd
/chroot/httpd/usr/local/apache/ bin/
4.7.2. cp /var/run/ld-elf.so.hints /chroot/httpd/var/run/
4.7.3. cp /usr/lib/libcrypt.so.2 /chroot/httpd/usr/lib/
4.7.4. cp /usr/lib/libc.so.4 /chroot/httpd/usr/lib/
4.7.5. cp /usr/libexec/ld-elf.so.1 /chroot/httpd/usr/libexec/
SECURITY GUIDELINES
Guidelines give advice. They are not mandatory—they are just suggestions on how
to follow the policy. Guidelines are meant to make life easier for the end user, as well as
for the security manager who wrote the policy, because they help people understand how
to meet the goals set by the security policy.
SECURITY GUIDELINE EXAMPLE
In this example, the password complexity rules of the password policy are
translated into a set of easy-to-follow suggestions. There may be other ways to select a
password to be compliant with the policy, but these guidelines are intended to simplify
the process for the end users while at the same time allowing them to make strong
passwords. Notice that unlike standards and procedures, the material is easy for
everyone to read and understand.
1. PURPOSE
1.1. These guidelines are meant to give you some ideas about how to create a good
password. Our password policy requires a certain amount of complexity, which can result
in difficult-to-remember passwords, but these guidelines should help you comply with
108
our password policy while at the same time making it easier for you to choose a
memorable password.
2. SCOPE
2.1. These guidelines are for all people who have computer accounts on our
network. 3. RESPONSIBILITIES
3.1. The Security Manager is responsible for defining, maintaining, and publishing
these guidelines.
4. PASSWORD SELECTION GUIDELINES
4.1. Do:
4.1.1. Use as many different characters as possible including numbers,
punctuation characters, and mixed upper- and lowercase letters. Choosing
characters from the largest possible range will make your password more secure.
4.1.2. Use both upper- and lowercase letters.
4.1.3. Use at least one number and one punctuation mark.
4.1.4. Select passwords that are easy to remember, so they do not have to
be written down.
4.2. Don’t use any of the following easily guessed items in your password:
4.2.1. Your name, the names of any family or friends, names of fictional
characters
4.2.2. Phone number, license or social security numbers
4.2.3. Any date
4.2.4. Any word in the dictionary
4.2.5. Passwords of all the same letter or any variation on the word
“password”
4.2.6. Simple patterns on the keyboard, like qwerty
109
4.2.7. Any word spelled backwards
4.3. Suggestions:
4.3.1. Use the first one or two letters of each word in a phrase, song, or
poem you can easily remember. Add a punctuation mark and a number.
4.3.2. Or, use intentionally misspelled words with a number or punctuation
mark in the middle.
4.3.3. You can also alternate between one consonant and one or two
vowels, and include a number and a punctuation mark. This provides a
pronounceable nonsense word that you can remember.
4.3.4. Or you can choose two short words and concatenate them together
with a punctuation character between them,
4.3.5. Or, interlace two words or a word and a number (like a year) by
alternating characters.
110
UNIT-5
Information Security Management- Roles and Responsibilities:
Security Roles and Responsibilities, Accountability, Roles and Responsibilities of Information
Security Management, Team Responding to Emergency Situation- Risk Analysis Process etc.
INTRODUCTION TO INFORMATION SECURITY MANAGEMENT SYSTEM
An information security management system (ISMS) is a set of policies
concerned with information security management or IT related risks. The governing
principle behind an ISMS is that an organization should design, implement and maintain
a coherent set of policies, processes and systems to manage risks to its information assets,
thus ensuring acceptable levels of information security risk.
As with all management processes, an ISMS must remain effective and efficient in
the long term, adapting to changes in the internal organization and external
environment. ISO/IEC 27001:2005 therefore incorporated the "Plan-Do-Check-Act"
(PDCA), or Deming cycle, approach:
The Plan phase is about designing the ISMS, assessing information security risks and
selecting appropriate controls.
The Do phase involves implementing and operating the controls.
The Check phase objective is to review and evaluate the performance (efficiency and
effectiveness) of the ISMS.
In the Act phase, changes are made where necessary to bring the ISMS back to peak
performance.
ISO/IEC 27001:2005 is a risk based information security standard, which means
that organizations need to have a risk management process in place. The risk
management process fits into the PDCA model given above.
However, the latest standard, ISO/IEC 27001:2013, does not emphasise the
Deming cycle anymore. The ISMS user is free to use any management process
(improvement) approach like PDCA or Six Sigmas DMAIC.
111
Another competing ISMS is Information Security Forum's Standard of Good
Practice (SOGP). It is more best practice-based as it comes from ISF's industry
experiences.
Some best-known ISMSs for computer security certification are the Common
Criteria (CC) international standard and its predecessors Information Technology
Security Evaluation Criteria (ITSEC) and Trusted Computer System Evaluation
Criteria (TCSEC).
Some nations publish and use their own ISMS standards, e.g. the Department of
Defense (DoD) Information Technology Security Certification and Accreditation Process
(DITSCAP) of USA, the Department of Defense Information Assurance Certification and
Accreditation Process (DIACAP) of USA, the German IT baseline protection, ISMS of Japan,
ISMS of Korea, Information Security Check Service (ISCS) of Korea.
Other frameworks such as COBIT and ITIL touch on security issues, but are mainly
geared toward creating a governance framework for information and IT more generally.
COBIT has a companion framework Risk IT dedicated to Information security.
NEED FOR ISMS
Information technology security administrators should expect to devote
approximately one-third of their time addressing technical aspects. The remaining
two-thirds should be spent developing policies and procedures, performing
security reviews and analyzing risk, addressing contingency planning and
promoting security awareness;
Security depends on people more than on technology;
Employees are a far greater threat to information security than outsiders;
Security is like a chain. It is only as strong as its weakest link;
The degree of security depends on three factors: the risk you are willing to take,
the functionality of the system and the costs you are prepared to pay;
Security is not a status or a snapshot, but a running process.
These facts inevitably lead to the conclusion that security administration is a
management issue, and not a purely technical issue.
112
The establishment, maintenance and continuous update of an ISMS provide a strong
indication that a company is using a systematic approach for the identification,
assessment and management of information security risks.
CRITICAL FACTORS OF ISMS:
Confidentiality: Protecting information from unauthorized parties.
Integrity: Protecting information from modification by unauthorized users.
Availability: Making the information available to authorized users.
The chief objective of information security management is to implement the
appropriate measurements in order to eliminate or minimize the impact that various
security related threats and vulnerabilities might have on an organization. In doing so,
information security management will enable implementing the desirable qualitative
characteristics of the services offered by the organization (i.e. availability of services,
preservation of data confidentiality and integrity etc.). By preventing and minimizing the
impacts of security incidents, ISMS ensures business continuity, customer confidence,
protect business investments and opportunities, or reduce damage to the business.
Large organizations, banks and financial institutes, telecommunication operators,
hospital and health institutes and public or governmental bodies have many reasons for
addressing information security very seriously. Legal and regulatory requirements which
aim at protecting sensitive or personal data as well as general public security
requirements impel them to devote the utmost attention and priority to information
security risks.
Under these circumstances, the development and implementation of a separate and
independent management process - namely an ISMS - is the only alternative.
The development of an ISMS framework based on ISO/IEC 27001:2005 entails the
following six steps:
1. Definition of security policy,
2. Definition of ISMS scope,
3. Risk assessment (as part of risk management),
4. Risk management,
113
5. Selection of appropriate controls
6. Statement of applicability
CRITICAL SUCCESS FACTORS OF ISMS
To be effective, the ISMS must:
have the continuous, unshakeable and visible support and commitment of the
organization’s top management;
be managed centrally, based on a common strategy and policy across the entire
organization;
be an integral part of the overall management of the organization related to and
reflecting the organization’s approach to risk management, the control objectives and
controls and the degree of assurance required;
have security objectives and activities be based on business objectives and
requirements and led by business management;
114
undertake only necessary tasks and avoiding over-control and waste of valuable
resources;
fully comply with the organization philosophy and mindset by providing a system
that instead of preventing people from doing what they are employed to do, it will
enable them to do it in control and demonstrate their fulfilled accountabilities;
be based on continuous training and awareness of staff and avoid the use of
disciplinary measures and “police” or “military” practices;
be a never ending process;
Information security is no longer simply about patch management and firewalls.
It requires a holistic risk management approach. As organizations increasingly rely on
global networks for supply chain and communications, and amass distributed data in
terabyte amounts, it has become apparent that the old models for computer security are
no longer effective. The exploitation points have correspondingly increased
exponentially. The old model of hiring a couple of security analysts or engineers and
throwing them into the Information Technology department is no longer sufficient to
address the growing needs of data and communications protection. Security can no
longer be left in the hands of the technologists. It must be acknowledged, considered,
embraced, and championed at the highest levels of the organization. In other words, it
must be aligned to the business objectives of the organization to maintain or improve its
value.
What is now required is a risk management approach to security that addresses
the organization as a whole. Risk management cannot be conducted in a silo. It requires
a coordinated and collaborative approach throughout the organization and must be
lifecycle oriented. It is not enough to form a “security department” by putting somebody
in charge, hiring a few security technologists, and calling it a day. Security risk
management must now evolve into a highly defined, quantifiable, justifiable approach to
securing the organization’s assets and reputation against loss. That “ultimate
responsibility” lands on the shoulders of top executives.
So why the change? Now that the Information Age has permeated all aspects of the
business world, the business environment and the information that drives it have become
increasingly dynamic. The information landscape changes daily, and organizations need
to adapt to that change to protect their assets—in other words, manage their risk.
115
ROLES AND RESPONSIBILITIES
At the executive level, there must be overall and/or ultimate responsibility (or
accountability, if you prefer) for risk management. The size of the risk management
organization headed by that executive will vary based on the size of the business. Large
organizations may have all the roles that are defined in this chapter, whereas smaller
organizations may employ a security organization that consists of a few individuals (who
may also share other responsibilities, as long as those responsibilities don’t conflict with
their security roles). Midsize organizations need several security positions ranging from
the technical security administrators who configure firewalls, routers, antivirus software,
and the like, to security engineers who design security controls, managed by a security
manager, director, or senior executive. Large organizations need a complete security
organization. All organizations, large or small, need an executive decision maker who has
been designated as being responsible for security risk.
In addition, the distinctions between large and small organizations and what
security positions they require vary according to what the organization does. Financial
companies typically require a larger and more robust security organization due to the
capital financial risk involved in an event or incident that negatively impacts their
integrity, confidentiality, and availability. Healthcare organizations, along with
businesses in other highly regulated sectors such as publicly traded companies that must
comply with Sarbanes-Oxley rules, and financial companies that are regulated by the
Gramm-Leach-Bliley Act, also require a substantial security organization. Technology
companies may require a midsize or smaller security organization, depending on how
exposed they are to threats, vulnerabilities, and risks from an attack and how much their
security posture is improved by aligning security to business objectives. Every
organization is different.
SECURITY POSITIONS
The following positions are recommended for security organizations. Other
positions also exist outside the formal security organization, because everyone in the
business has some level of responsibility for security. For example, every employee is
responsible for protecting their passwords, their login sessions, and any confidential
116
information they handle. General managers, department heads, and operational leads are
responsible for being familiar with security policy and keeping an eye on the security
practices of their subordinates. They are responsible for ensuring that violations are
reported, and may carry out enforcement policies.
Figure 6-1 shows an example security responsibility hierarchy, with some
descriptions of responsibilities that might pertain to each position.
CHIEF SECURITY RISK OFFICER (CSRO) OR CHIEF INFORMATION SECURITY OFFICER
(CISO)
This position is an executive staff member, with ultimate accountability for all
security efforts for the business. The CSRO oversees all aspects of risk management
across the enterprise, or in organizations without a formal risk management department,
the CISO oversees the information security function and incorporates risk management
into that function. In organizations where the CSRO is responsible for all types of risks
across the business (including financial risks, business risks, and other non-IT risks), the
person in that role will generally establish an IT risk function to oversee IT-related risks
in particular, since the management of IT risks represents a unique discipline requiring
specialized knowledge. Otherwise, the CISO performs that role. The CSRO or CISO should
report to the chief executive officer (CEO), chief operating officer (COO), or the Board of
Directors.
117
While some organizations may consider it controversial to elevate the position to
equal par with chief executives, the criticality of addressing corporate risk and legal
compliance justifies the decision. The CSRO or CISO is a champion and defender of
security and risk initiatives for the business, bearing overall responsibility for risk
assessment and risk management. The CRSO or CISO may hold certifications related to
information security, audit, risk management, and disaster recovery.
In collaboration with the executive staff, the CSRO or CISO should:
• Ensure the business has risk management skills in its human capital
• Establish an organizational structure that supports a risk management strategy
• Implement an integrated risk management framework
• Define the business’ risk appetite in terms of loss tolerance
• Ensure the business can absorb the risk in terms of human and financial
resources
• Establish risk assessment, management, response, mitigation, and audit
procedures
• Influence the business’ risk culture and provide organizational learning
opportunities
SECURITY DIRECTOR
The security director works with the executive team to accomplish business goals.
This position requires expert communication, negotiation, and leadership skills, as well
as technical knowledge of IT and security hardware. While a person who has experience
as a vice president may already possess these skills, the focus of the security director
should be security-oriented and they should be experienced in information security
decision making. The security director has responsibility to oversee and coordinate
security efforts across the business, including IT, HR, Communications, Legal, Facilities,
and other departments, to identify needed security initiatives and standards.
The security director, among other responsibilities:
118
• Coordinates the security-related strategic and visionary goals of the business
• Oversees security management and vendors who safeguard the business’ assets,
intellectual property, and computer systems, as well as the physical safety of employees
and visitors
• Identifies protection goals and objectives consistent with corporate strategic
plans
• Manages the development and implementation of global security policy (rules),
standards (minimum requirements), guidelines (recommendations), and procedures
(step-by-step instructions) to ensure ongoing maintenance of security
• Maintains relationships with local, state, and federal law enforcement and other
related government agencies
• Oversees the investigation of security breaches and assists with disciplinary and
legal matters associated with such breaches as necessary
• Works with outside consultants as appropriate for independent security audits
• Participates in the business’ change management process at the organizational
and strategic level
• Is fluent with the various aspects of the risk management framework
SECURITY MANAGER
The security manager has day-to-day responsibility for all security-related
activities and incidents. All operational security positions report to this position. The
security manager is responsible for management and distribution of the security policy,
policy adherence and coordination, and security incident coordination.
The security manager also assigns and determines ownership of data and
information systems. In addition, this person also ensures that audits take place to
determine compliance with policy. The security manager also makes sure that all levels
of management and administrative and technical staff participate during planning,
development, and implementation of policies and procedures.
119
Many of the security manager’s functions can be delegated, depending on the
staffing requirements and individual skill sets of the security organization. However, the
security manager bears accountability for ensuring that these functions take place
effectively.
Certifications that a security manager may hold include Information Assurance
Manager (IAM) or equivalent and Certified Information Security Manager (CISM) from
ISACA. In addition to other roles, the security manager:
• Develops and maintains a comprehensive security program
• Develops and maintains a business resumption plan for information resources
• Approves access and formally assigns custody of the information resources
• Ensures compliance with security controls
• Plans for contingencies and disaster recovery
• Ensures that adequate technical support is provided to define and select cost
effective security controls
SECURITY ARCHITECT
This person has ultimate responsibility for the security architecture, including
conducting product testing and keeping track of new bugs and security vulnerabilities as
they arise. The security architect produces a detailed security architecture for the
network based on identified requirements and uses this architecture specification to
drive efforts toward implementation. In addition to other roles, the security architect:
• Identifies threats and vulnerabilities
• Identifies risks to information resources through risk analysis
• Identifies critical and sensitive information resources
• Works with the data owner to assess and classify information
• Works with technical management to specify cost-effective security controls and
convey security control requirements to users and custodians
120
• Assists the security manager in evaluating the cost-effectiveness of controls
SECURITY ENGINEER
The primary role of this position is the technical implementation of the architect’s
designs. The security engineer works directly with the architect on design decisions and
with the administrator on device management decisions. Security engineers generally
have a degree in engineering or computer science, along with extensive technical training
or experience, and they often hold Certified Information Systems Security Professional
(CISSP) certification and other technical certifications in their field of expertise. A
security engineer may perform the following duties:
• Installation and configuration of networks and network devices such as web
application firewalls, network firewalls, switches, load balancers, and routers
• Security configuration of Unix, Linux, or Windows servers
• Security configuration of applications and databases
• Installation, configuration, and design of security tools, including development
and coding
• Security incident investigation, including network packet capture
• Maintenance and monitoring of network and host intrusion detection and
prevention technologies
SECURITY ADMINISTRATOR
Every security organization has security administrators, as many as needed to
implement security on a day-to-day, operational/tactical basis at the facility. The security
administrator executes all actions directed by the security architect, security engineer,
security manager, or as required by security policy or incident response procedures. The
security administrator is responsible for ensuring all appropriate security requirements
are met and maintained on all computers, networks, and network technologies, including
patch management and operating system upgrades. The security administrator is often
the first person contacted whenever there is a suspected or known security problem. This
person has the operational/tactical responsibility for ensuring that the business, its
121
reputation, and its assets are protected and has the authority to take any and all action
necessary to accomplish this goal. Among other duties, the security administrator:
• Implements the security controls specified by the security architect, security
engineer, and security manager
• Implements physical and procedural safeguards for information resources
within the facility
• Administers access to the information resources and makes provisions for timely
detection, reporting, and analysis of actual and attempted unauthorized access to
information resources
• Provides assistance to the individuals responsible for information security
• Assists with acquisition of security hardware/software
• Assists with identification of vulnerabilities and other data gathering activities
and log file analysis
• Develops and maintains access control rules
• Maintains user lists, passwords, encryption keys, and other authentication and
security-related information and databases
• Develops and follows procedures for reporting on monitored controls
SECURITY ANALYST
The primary role of this position is to support the security architect, security
engineer, security administrator, and security management in analyzing and producing
reports required for the assessment and smooth functioning of security operations. The
security analyst may hold vendor-oriented certifications such as those offered by Cisco,
Microsoft, Enterasys, Symantec, Oracle, and McAfee. Among other duties, the security
analyst:
• Monitors alerts and reports generated by security systems
122
• Reviews log files as generated by security devices and servers, making note of
anomalies
• Compiles reports as required by management or as specified by security policy
• Maintains security metrics
• Collaborates with security organization team members to assess and analyze
security operations and suggests improvement
• Manages quality control and change management initiatives for the security
organization
• Maintains security policy documentation and ensures that necessary changes are
incorporated as directed by the architect or management
SECURITY INVESTIGATOR
This position is responsible for Legal, HR, and internal investigations into security
incidents, breaches, attacks, and violations. The security investigator often works closely
with law enforcement agencies as needed. Skills required include technical expertise as
well as evidence handling and forensic procedures. The security investigator may hold
industry related certifications in forensics and incident response. Among other duties,
the security investigator:
• Responds to requests from HR, Legal, and other internal departments to
investigate incidents
• Coordinates with outside attorneys or law enforcement representatives
• Collects and preserves evidence from computer systems
• Performs e-discovery and forensic searches for keywords and patterns
• Produces detailed reports on investigations
• Provides information to the HR and Legal departments for action
• Maintains strict secrecy about ongoing investigations
123
SECURITY AWARENESS TRAINER
The primary role of this position is to develop and deliver security awareness
training to the business based on corporate security policy, standards, procedures, and
guidelines. The trainer generally has a background in security as well as in education and
training. The trainer coordinates and collaborates with the security department subject
matter experts to ensure that the training is both comprehensive and accurate. This
position may alternatively reside in another department within the business, typically
Human Resources or Communications.
An important characteristic of this position is that the skill set required for the
delivery of effective security awareness training is not often found within an IT
department, yet the position requires detailed security knowledge. Assigning security
engineers and security administrators to produce training materials can be ineffective,
due to the highly technical nature of their work and the requirement for delivering
training in “plain English.” The trainer must be skilled in interpreting technical
information for the business’ employees in a way that is understandable, fresh,
interesting, and highly relevant.
FACILITY SECURITY OFFICER
The primary role of this position is to enforce the business’ physical security policy
at each building location. Each major facility location should have a security officer
responsible for coordinating all physical security–related activities and incidents at the
facility. The person in this position is not the same person who is operationally
responsible for the computer equipment at the facility. The facility security officer has the
authority to take action without the approval of the management at the facility when
required to ensure physical security. This position also typically works within a Facilities
department rather than IT.
All physical security reports are reviewed by the facility security officer. For
example, this position reviews log files of facility access records, such as key card logs.
The facility security officer is responsible for coordinating all activities related to security
incidents at the facility and has the authority to decide what actions are to be taken as
124
directed by the incident response procedures. The facility security officer coordinates all
activities with the corporate security manager, director, or vice president.
SECURITY INCIDENT RESPONSE
Team Security incident response teams are known by several names. Some are
called SRT for security response team, some are called CIRT for computer incident
response team, and some are called IRT for incident response team (which is the term
used in the following discussion). Regardless of the specific terminology, these teams are
collections of individuals from various parts of the business who are brought together to
handle emergencies. They join the team apart from their daily responsibilities in order to
prepare, practice, and drill for potential emergencies and, in the event of an actual
emergency, handle the situation.
Examples of the types of incidents a response team might handle include
• Hostile intrusions into the network by unauthorized people
• Damaging or hostile software loose on a system or on the network
• Unauthorized access or acceptable use violations resulting in the need for
investigations of personnel
• Virus activity
• Software failures, system crashes, and network outages
• Participation in external investigations by law enforcement, government
regulators, or international watchdog and legal organizations
• Court-ordered discovery, evidentiary, or investigative legal action
• Illegal activities such as software piracy
Every business performs incident response, whether or not they have an official
IRT established. In many businesses where there is no IRT, individual employees perform
incident response by dealing with incidents in their own way. A software virus outbreak
is one example. In businesses without an IRT, employees may choose to install antivirus
software, run specialized virus cleaning software, or just live with a virus infestation. In
125
these situations, no coordination happens and virus response varies with each individual,
usually without enterprise-wide success. One advantage of an organized IRT is that it can
deal with incidents like this on a higher level, with more comprehensive success.
Members of an IRT should include technical experts who can evaluate incidents
like network intrusions, software failures, and virus outbreaks on a technical level;
administrators who can keep logs and maintain the paperwork and electronic
information associated with an incident investigation; managers who coordinate the
work of the IRT members; and, if available, IRT specialists who have served on prior IRTs.
None of these individuals necessarily needs to be assigned to the IRT as a full-time
position. Typically, businesses that establish an IRT leverage employees from many other
parts of the business and ask them to share their responsibilities between their regular
job and the IRT.
An IRT can be assigned individuals with specific technical expertise in a variety of
areas. Depending on the business and the types of technologies used in the infrastructure,
this expertise may include
• Virus management
• Hostile software detection and management
• Vulnerability analysis
• Specific hardware platforms
• Specific operating systems
• Commercial off-the-shelf or open source tools and applications
• Custom-developed or in-house-developed software and/or scripts
SECURITY COUNCIL, STEERING COMMITTEE, OR BOARD OF DIRECTORS
The security organization should be included in all efforts that involve corporate
data and resources. Many different departments handle data, not just IT. For example, the
HR department handles confidential employee information. The Legal department
handles confidential business and customer information. The Facilities department may
126
handle badging and physical access. Generally speaking, every major department in the
business has some level of interaction with business resources and data. All of these
departments should coordinate with the security organization. In most businesses, the
security team meets with almost every manager of the business, and sometimes with
most of the employees.
A security council or steering committee, whose members include representatives
from each major business department, provides a forum for information exchange that
facilitates the job of the security practitioner and identifies business requirements to
which the security organization should be privy. Each Security Council representative
provides status updates of initiatives within that representative’s organization, and each
receives information from the security organization about initiatives and practices that
impact each of them.
The Security Council can be used in a variety of ways. Information gathering is one
important opportunity. Members of the Security Council have unique visibility into the
operation of their part of the business. This visibility is important to the
comprehensiveness of the security practitioner’s focus. For example, a department that
is considering a new technology initiative may not have considered the security impact
on the rest of the network, but the security practitioner, upon hearing about the initiative,
may make conceptual connections overlooked by the individual department.
A Security Council or steering committee can also be an effective risk management
tool. The purpose of a risk analysis is to identify as many business risks as possible, and
then either accept, mitigate, or transfer those risks. Any risks that are overlooked by a
risk analysis put the business in jeopardy if any of those risks become realized. Members
of the Security Council can be polled to identify specific business risks in each of their
specialties, and this provides a risk analysis with a greater scope and better coverage.
Another advantage is that it gives a sense of participation and teamwork to
business departments that may otherwise act independently without consulting each
other, or even compete for resources or produce conflicting infrastructures.
INTERACTION WITH HUMAN RESOURCES
127
Human Resources departments need to provide required information about new
hires to security administrators before the new hires’ start date. This is an important
interaction between HR and IT, even if the security organization is not part of the hiring
procedure. Security administrators need to know at any point in time whose employment
with the business is valid, so they can properly maintain and monitor accounts on
systems and on the network. Perhaps even more important, HR also reports required
information about terminations to system administrators before the final termination
occurs. The security organization is always involved in terminations to some extent,
because employee terminations result in the revocation of trust. When trust is revoked,
assurance must be provided that all access has been revoked, and activity must be
monitored to ensure the maintenance of that revocation.
HR manages contractor information and provides this information to security
administrators. Contractors, as temporary employees, present special problems to
security administrators. They often work for only a short time and sometimes come and
go, resulting in a constant process of granting and revoking physical access and system
and network accounts. It’s hard to tell when seeing a contractor in the hallways whether
they should be there or not. The security of the network relies heavily on the timely
transfer of information from HR to the security organization. HR, in turn, requires timely
information from individual managers regarding the status of their contractors hired
directly and managed individually.
HR performs background checks, credit checks, and reference checks on new
employee applicants. Exit interviews are conducted with terminating employees to
recover portable computers, telephones, smart cards, business equipment, keys, and
identification badges and to identify morale problems if they exist. Employees discharged
for cause must be escorted from the premises immediately and prohibited from
returning, both to reduce the threat of retaliation and to forestall any questions if
unexpected activity occurs on the network or on the premises.
Monitoring the activities of employees is a matter of corporate culture—those
organizations that want to do it differ in the extent and type of response they choose.
Likewise, the treatment of confidential and private information differs from business to
business, but these are issues that should be dealt with by every organization. If an
128
organization hasn’t gotten around to a formal policy on these issues, the best time to start
is now, before a policy violation occurs when there is no clear, documented policy that
has been communicated to all employees. Communication is truly the key to successful
security management. Physical security should not be overlooked, and periodic fire drills
can be used to test security measures, help close any gaps, and avoid the danger of having
a false sense of security.
129
16. Question Bank
130
17. Discussion Topic
o Manage Your Work to Meet Requirements (NOS 9001)
o Work Effectively with Colleagues (NOS 9002)
18. References, Journals, websites and E-links if any
http://www.iso.org/iso/home/standards/managementstandards/iso27001.html
http://csrc.nist.gov/publications/nistpubs/800-55-Rev1/SP800-55-rev1.pdf
131
19. Student List
Class/ Section: CSE 3-2, C
S. No. Roll No. Student Name
1 13R11A05B5 AKKINENI SAI LAKSHMI
2 13R11A05B6 AMBAVARAPU SRI SAI JAYA MADHURI
3 13R11A05B7 ANJANI A
4 13R11A05B8 ASHISH MISRA
5 13R11A05B9 AYYAGARI VIJAYA SINDHU
6 13R11A05C0 B POOJA AISHWARYA
7 13R11A05C1 BHARATH CHANDRA KAKANI
8 13R11A05C2 BHIMA SAINATH
9 13R11A05C3 CHRISTO VIJAY
10 13R11A05C4 G APOORVA
11 13R11A05C5 G NIKITHA
12 13R11A05C6 G PRIYESH KUMAR
13 13R11A05C7 G SRIHITHA
14 13R11A05C8 GADILA AKHILA
15 13R11A05C9 GADAGONI SAI CHARAN
16 13R11A05D1 GUNTUKU GIRISH
17 13R11A05D2 JINNA SRIDHAR REDDY
18 13R11A05D4 K PAVAN KUMAR
19 13R11A05D5 KASULA SWAPNA PRIYA
20 13R11A05D7 KADIRE SATHWIKA
21 13R11A05D8 KADIYALA SRIHARSHA
22 13R11A05D9 KASHETTY MADHURI
23 13R11A05E0 KOTHAPALLY LOKESH
24 13R11A05E1 LAKSHMI INDUJA YENNISETTI
25 13R11A05E2 M SHIVA KUMAR
26 13R11A05E3 M LAKSHMI PRAVALLIKA
27 13R11A05E4 MALLARAPU MANASA
28 13R11A05E5 MERUGU SRAVAN KUMAR
29 13R11A05E8 N VAMSHI KRISHNA
30 13R11A05E9 P LAKSHMI SRUTI VEDA
31 13R11A05F0 P POOJITHA REDDY
32 13R11A05F1 P SAI KIRAN REDDY
33 13R11A05F2 PANDA SUSHMA RAJESHWARI
34 13R11A05F3 PARUCHURI DIVYA
35 13R11A05F4 PEDDI REDDY AKHILA REDDY
36 13R11A05F5 PRATYUSH SHARMA
132
37 13R11A05F6 R BHAVANI
38 13R11A05F7 RAGIRI NAVYA
39 13R11A05F8 RAMA HIMA BINDU
40 13R11A05F9 REVATHI SIMHADRI
41 13R11A05G0 RUDHARARAJU MAGADH SAI VARMA
42 13R11A05G1 SHRAVYA ACHA
43 13R11A05G2 SINGARAJU MONICA
44 13R11A05G4 TEJASWEE VEERAVALLI
45 13R11A05G5 TUNGA JAYASREE
46 13R11A05G6 VEERANKI SREE DIVYA
47 13R11A05G7 GANGJI VANDANA
48 13R11A05G8 VELAGAPUDI ANUHYA
49 13R11A05G9 VELAMARTHI RAJKOUSHIK
50 13R11A05H0 VENKATA PATHI RAJU K
51 13R11A05H1 VUCHALA PRASHANTH RAJ
52 13R11A05H2 VUNNAM TARUN SEKHAR
53 13R11A05H3 VUTHPALA ANUDEEP
54 13R11A05H4 GOLLIPALLI JITHENDAR REDDY
Total: 54 Males: 24 Females: 30
Class/ Section: CSE 3-2, D
1 13R11A05H5 A MARY PRISCILLA
2 13R11A05H6 ABHINAY T
3 13R11A05H7 ABHISHEK PAWAR
4 13R11A05H8 ANKEM LAXMI PRASANNA
5 13R11A05H9 AUSULA ANUSHA
6 13R11A05J0 BARELLA SRINIVAS REDDY
7 13R11A05J1 BANTU MUKESH RAJ
8 13R11A05J2 CH V SESHA SAI LALITHA PRIYANKA
9 13R11A05J3 CHANDRA KANTH REVOORI
10 13R11A05J4 AASHISH REDDY D
11 13R11A05J5 DATLA DEEPAK VARMA
12 13R11A05J6 DESHAM HARATHI
13 13R11A05J7 EMANI VENKATA SESHA SAI RAM
14 13R11A05J8 GADDAM ALEKHYA
15 13R11A05J9 G PRATHAM
16 13R11A05K0 GATTU KALKINATH
17 13R11A05K1 SRIKANTH R B
18 13R11A05K2 GOLLAMUDI PRANAV SURYA
133
19 13R11A05K3 GORENTA RAMYA
20 13R11A05K4 GOTETI LALITHA PRIYANKA
21 13R11A05K5 GUDURU UMESH
22 13R11A05K6 KAMBALAPALLY JAYAVARDHAN REDDY
23 13R11A05K7 KAMARAJU SAHASRA
24 13R11A05K8 K SUHAS REDDY
25 13R11A05K9 KANDADAI ABHIRAMAN
26 13R11A05L0 KOVELAMUDI RAMYASRI
27 13R11A05L1 MANVITHA REDDY DONTHI
28 13R11A05L2 MARSAKATLA SARITHA
29 13R11A05L3 N SRI CHINNA SURYA NAGA SAI MANIKAN
30 13R11A05L4 NANDAGIRI AKHILESH
31 13R11A05L5 P SREEKRISHNA KASHYAP
32 13R11A05L6 PATSA VISWA ANVESH
33 13R11A05L7 PEDDI MANASWI
34 13R11A05L8 POLEPALLI DHANUSH
35 13R11A05L9 R SRUTHI REDDY
36 13R11A05M1 SADDI RADHA
37 13R11A05M2 SAHITHI JAGARLAMUDI
38 13R11A05M3 SEELAM VAMSI ROMITH
39 13R11A05M4 SHRAVANI BAJJURI
40 13R11A05M5 SINGURI AKSHITA
41 13R11A05M6 STOTRABHASHYAM SHRUTHY
42 13R11A05M7 T JAGAN
43 13R11A05M8 T MOUNIKA
44 13R11A05M9 T RAVI THEJA
45 13R11A05N0 U SAI AARATI
46 13R11A05N1 U V SATYA SUNANDA
47 13R11A05N2 V P S PRASHANTH
48 13R11A05N3 V TRISHA
49 13R11A05N4 VODELA SAI SANKEERTH
50 13R11A05N5 PRANAV NANDURI
Total: 50 Males: 27 Females: 23
134
20. Group-Wise students list for discussion topic
Class/ Section: CSE 3-2, C
G1
13R11A05B5 AKKINENI SAI LAKSHMI
13R11A05B6 AMBAVARAPU SRI SAI JAYA MADHURI
13R11A05B7 ANJANI A
13R11A05B8 ASHISH MISRA
13R11A05B9 AYYAGARI VIJAYA SINDHU
G2
13R11A05C0 B POOJA AISHWARYA
13R11A05C1 BHARATH CHANDRA KAKANI
13R11A05C2 BHIMA SAINATH
13R11A05C3 CHRISTO VIJAY
13R11A05C4 G APOORVA
G3
13R11A05C5 G NIKITHA
13R11A05C6 G PRIYESH KUMAR
13R11A05C7 G SRIHITHA
13R11A05C8 GADILA AKHILA
13R11A05C9 GADAGONI SAI CHARAN
G4
13R11A05D1 GUNTUKU GIRISH
13R11A05D2 JINNA SRIDHAR REDDY
13R11A05D4 K PAVAN KUMAR
13R11A05D5 KASULA SWAPNA PRIYA
13R11A05D7 KADIRE SATHWIKA
G5
13R11A05D8 KADIYALA SRIHARSHA
13R11A05D9 KASHETTY MADHURI
13R11A05E0 KOTHAPALLY LOKESH
13R11A05E1 LAKSHMI INDUJA YENNISETTI
13R11A05E2 M SHIVA KUMAR
G6
13R11A05E3 M LAKSHMI PRAVALLIKA
13R11A05E4 MALLARAPU MANASA
13R11A05E5 MERUGU SRAVAN KUMAR
13R11A05E8 N VAMSHI KRISHNA
13R11A05E9 P LAKSHMI SRUTI VEDA
G7
13R11A05F0 P POOJITHA REDDY
13R11A05F1 P SAI KIRAN REDDY
13R11A05F2 PANDA SUSHMA RAJESHWARI
13R11A05F3 PARUCHURI DIVYA
13R11A05F4 PEDDI REDDY AKHILA REDDY
G8
13R11A05F5 PRATYUSH SHARMA
13R11A05F6 R BHAVANI
13R11A05F7 RAGIRI NAVYA
13R11A05F8 RAMA HIMA BINDU
13R11A05F9 REVATHI SIMHADRI
135
G9
13R11A05G0 RUDHARARAJU MAGADH SAI VARMA
13R11A05G1 SHRAVYA ACHA
13R11A05G2 SINGARAJU MONICA
13R11A05G4 TEJASWEE VEERAVALLI
13R11A05G5 TUNGA JAYASREE
G10
13R11A05G6 VEERANKI SREE DIVYA
13R11A05G7 GANGJI VANDANA
13R11A05G8 VELAGAPUDI ANUHYA
13R11A05G9 VELAMARTHI RAJKOUSHIK
13R11A05H0 VENKATA PATHI RAJU K
G11
13R11A05H1 VUCHALA PRASHANTH RAJ
13R11A05H2 VUNNAM TARUN SEKHAR
13R11A05H3 VUTHPALA ANUDEEP
13R11A05H4 GOLLIPALLI JITHENDAR REDDY
Class/ Section: CSE 3-2, D
G1
13R11A05H5 A MARY PRISCILLA
13R11A05H6 ABHINAY T
13R11A05H7 ABHISHEK PAWAR
13R11A05H8 ANKEM LAXMI PRASANNA
13R11A05H9 AUSULA ANUSHA
G2
13R11A05J0 BARELLA SRINIVAS REDDY
13R11A05J1 BANTU MUKESH RAJ
13R11A05J2 CH V SESHA SAI LALITHA PRIYANKA
13R11A05J3 CHANDRA KANTH REVOORI
13R11A05J4 AASHISH REDDY D
G3
13R11A05J5 DATLA DEEPAK VARMA
13R11A05J6 DESHAM HARATHI
13R11A05J7 EMANI VENKATA SESHA SAI RAM
13R11A05J8 GADDAM ALEKHYA
13R11A05J9 G PRATHAM
G4
13R11A05K0 GATTU KALKINATH
13R11A05K1 SRIKANTH R B
13R11A05K2 GOLLAMUDI PRANAV SURYA
13R11A05K3 GORENTA RAMYA
13R11A05K4 GOTETI LALITHA PRIYANKA
G5
13R11A05K5 GUDURU UMESH
13R11A05K6 KAMBALAPALLY JAYAVARDHAN REDDY
13R11A05K7 KAMARAJU SAHASRA
13R11A05K8 K SUHAS REDDY
13R11A05K9 KANDADAI ABHIRAMAN
136
G6
13R11A05L0 KOVELAMUDI RAMYASRI
13R11A05L1 MANVITHA REDDY DONTHI
13R11A05L2 MARSAKATLA SARITHA
13R11A05L3 N SRI CHINNA SURYA NAGA SAI MANIKAN
13R11A05L4 NANDAGIRI AKHILESH
G7
13R11A05L5 P SREEKRISHNA KASHYAP
13R11A05L6 PATSA VISWA ANVESH
13R11A05L7 PEDDI MANASWI
13R11A05L8 POLEPALLI DHANUSH
13R11A05L9 R SRUTHI REDDY
G8
13R11A05M1 SADDI RADHA
13R11A05M2 SAHITHI JAGARLAMUDI
13R11A05M3 SEELAM VAMSI ROMITH
13R11A05M4 SHRAVANI BAJJURI
13R11A05M5 SINGURI AKSHITA
G9
13R11A05M6 STOTRABHASHYAM SHRUTHY
13R11A05M7 T JAGAN
13R11A05M8 T MOUNIKA
13R11A05M9 T RAVI THEJA
13R11A05N0 U SAI AARATI
G10
13R11A05N1 U V SATYA SUNANDA
13R11A05N2 V P S PRASHANTH
13R11A05N3 V TRISHA
13R11A05N4 VODELA SAI SANKEERTH
13R11A05N5 PRANAV NANDURI
137
Or Read Directly
Reactions
Posted by MY Blog
You may like these posts
Information Security Managementism best notes | Information Security Management
Posts
Comments
0 Comments