IS UNIT-2 Notes - 240423 - 090216
IS UNIT-2 Notes - 240423 - 090216
UNIT-II
Syllabus:
Legal, Ethical and Professional Issues: Law and ethics in information security,
relevant U.S laws-international laws and legal bodies, Ethics, and information
security.
Risk Management: Overview, Risk Identification, risk assessment, Risk Control
strategies, selecting a risk control strategy, Quantitative versus qualitative risk
control practices, Risk management discussion points, recommended risk control
practices.
Objective: 1. Describe the functions of and relationships among laws, regulations, and
professional organizations in information security.
2. Define risk management, risk identification, and risk control, assess risk based on
probability of occurrence and likely impact, Describe the various risk mitigation strategy
options.
Outcome: Identify legal, ethical, and professional issues in information security
and drafts policies for risk management in information security implementations.
LEGAL, ETHICAL, AND PROFESSIONAL ISSUES
As a future information security professional, you must understand the scope of an
organization’s legal and ethical responsibilities.
• Managing liability for privacy and security risks are taken care by information
security professionals.
• To minimize liability and reduce risks from electronic and physical threats,
and to reduce all losses from legal action, information security practitioners
have good knowledge on the current legal environment, laws and regulations,
and watch for new and emerging issues.
• Educate the management and employees on their legal and ethical obligations
and the proper use of information technology and information security.
Types of Law
➢ Civil law
➢ Criminal law
➢ Tort law
➢ Private law
➢ Public law
Security and Freedom Use and sale of 1999 Clarifies use of encryption for
through Encryption Act of software that uses or people in the United States and
1999 enables encryption. permits all persons in the U.S. to
buy or sell any encryption product
and states that the government
cannot require the use of any kind
of key escrow system for
encryption products.
U.S.A. Patriot Act of 2001 Terrorism 2001 Defines stiffer penalties for
prosecution of terrorist crimes.
US Copyright Law
There are exceptions for information that is protected from disclosure, and the Act
does not apply to state or local government agencies or to private businesses or
individuals, although many states have their own version of the FOIA
Policy vs Law
In an organization, information security professionals maintains security by
establishing and enforcing policies.
Only when all conditions are met, does the organization have a reasonable
expectation of effective policy.
The Ten Commandments of Computer Ethics: From The Computer Ethics Institute
1. Thou shalt not use a computer to harm other people.
2. Thou shalt not interfere with other people’s computer work.
3. Thou shalt not snoop around in other people’s computer files.
4. Thou shalt not use a computer to steal.
5. Thou shalt not use a computer to bear false witness.
6. Thou shalt not copy or use proprietary software for which you have not paid.
7. Thou shalt not use other people’s computer resources without authorization or
proper compensation.
8. Thou shalt not appropriate other people’s intellectual output.
9. Thou shalt think about the social consequences of the program you are writing or
the system you are designing.
10. Thou shalt always use a computer in ways that ensure consideration and respect
for your fellow humans.
relevant laws, obtaining agreement to comply with these policies and laws from all
members of the organization.
Accident: Individuals with authorization and privileges are most likely to cause harm
or damage by accident. Careful planning and control help prevent accidental
modification to systems and data.
Intent: Criminal or unethical intent is the state of mind. It is often necessary to
establish criminal intent to successfully prosecute offenders. Protecting a system
against those people do harm or damage is best accomplished by means of technical
controls, and vigorous litigation or prosecution if these controls fail.
Whatever the cause of illegal, immoral, or unethical behaviour. It is the responsibility
of information security personnel to do everything in their power to deter these acts
and to use policy, education and training, and technology to protect information and
systems.
Laws, policies, and technical controls are all examples of deterrents Laws and policies
only deter if three conditions are present:
- Fear of penalty
- Probability of being caught
- Probability of penalty being administered
RISK MANAGEMENT
Definition: The formal process of identifying and controlling the risks facing an
organization is called risk management. It is the probability of an undesired event
causing damage to an asset.
These environments must maintain Confidentiality & Privacy and assure the integrity
of organizational data-objectives that are met through the application of the principles
of risk management.
Know Yourself
Identify, Examine & Understand the information systems.
To protect assets, you must understand what they are. How they add value to the
organization, and to which vulnerabilities they are susceptible.
The policies, Education and training programs, and technologies that protect
information must be carefully maintained and administered to ensure that they are
still effective.
Members of the information security community best understand the threats and
attacks that introduce risk into the organization, they often take a leadership role in
addressing risk. Management and users, when properly trained and kept aware of
the threats the organization faces will helps in early detection and response process.
All the communities must work together to address all levels of risk.
RISK IDENTIFICATION
➢ A risk management strategy requires that information security professionals
must identify, classify, and prioritize their organizations’ information assets.
➢ Assets are the targets of various threats and threat agents, and the goal is to
protect the assets from the threats.
➢ Once the organizational assets have been identified, a threat identification
process is undertaken.
➢ The circumstances and settings of each information asset are examined to
identify vulnerabilities.
➢ When vulnerabilities are found, controls are identified and assessed as to their
capability to limit possible losses in the eventuality of attack.
Asset Identification & Valuation Includes all the elements of an organization’s system,
such as people, procedures, data and information, software, hardware, and
networking elements. Then, you classify and categorize the assets by adding the
details of each asset.
People include employees and nonemployees. There are two categories of employees:
those who hold trusted roles and have correspondingly greater authority and
accountability, and other staff who have assignments without special privileges.
Nonemployees include contractors and consultants, members of other organizations
with which the organization has a trust relationship, and strangers.
Procedures fall into two categories: IT and business standard procedures, and IT and
business sensitive procedures. The business sensitive procedures are those that may
assist a threat agent in crafting an attack against the organization or that have some
other content or feature that may introduce risk to the organization.
Data Components have been expanded to account for the management of information
in all stages: Transmission, Processing, and Storage.
Hardware is assigned to one of two categories: the usual systems devices and their
peripherals, and the devices that are part of information security control systems.
The latter must be protected more thoroughly than the former.
Element Type: Document the function of each Element by listing its type. For
hardware, a list of possible element types, such as servers, desktops, networking
devices or test equipment.
One server might be listed as
- Device class= S (Server)
- Device OS= W2K ( Windows 2000)
- Device Capacity = AS ( Advanced Server )
Serial Number: For hardware devices, the serial number can uniquely identify a
specific device.
Manufacturer’s Model No or Part No: Record the model or part number of the element.
This record of exactly what the element is can be very useful in later analysis of
vulnerabilities because some vulnerability instances only apply to specific models of
certain devices and software components.
Software Version, Update revision, or FCO number: Document the specific software
or firmware revision number and, for hardware devices, the current field change order
(FCO) number. An FCO is an authorization issued by an organization for the repair,
modification, or update of a piece of equipment. Documenting the revision number
and FCO is particularly important for networking devices that function mainly
through the software running on them. For example, firewall devices often have three
versions: an operating system (OS) version, a software version, and a basic
input/output system ( BIOS) firmware version.
• Which information Asset is the most critical to the success of the organization.
• Which information asset generates the most revenue?
• Which information asset generates the most probability?
• Which Information asset would be the expensive to replace?
Security Clearances
The other side of the data classification scheme is the personnel security clearance
structure.
Each user of data must be assigned a single authorization level that indicates the
level of classification he or she is authorized to view.
-Eg: Data entry clerk, development Programmer, Information Security Analyst, or
even CIO.
Most organizations have a set of roles and the accompanying security clearances
associated with each role.
Overriding an employee’s security clearance is the fundamental principle of “need-to-
know”.
A clean desk policy requires that employees secure all information in appropriate
storage containers at the end of each day. When Information are no longer valuable,
proper care should be taken to destroy them by means of shredding, burning, or
transferring to a service offering authorized document destruction.
• Dumpster diving to retrieve information that could embarrass a company or
compromise information security.
Include a dimension to represent the sensitivity and security priority of the data and
the devices that store, transmit, and process the data—that is, a data classification
scheme. Data classification categories are confidential, internal, and external.
14 different threats which are danger to any organization must be examined. This
examination is known as a threat assessment. You can begin a threat assessment by
answering a few basic questions, as follows:
• Which threats present a danger to an organization’s assets in the given
environment?
• Which threats represent the most danger to the organization’s information?
• How much would it cost to recover from a successful attack?
• Which of the threats would require the greatest expenditure to prevent?
By answering these questions, you establish a framework for the discussion of threat
assessment. Above list of questions may not cover everything that affects the
information security threat assessment. If an organization has specific guidelines or
policies, based on those some additional questions can be considered.
Vulnerability Identification
Once the organization’s information assets are identified, documented some criteria
to assess the threats it faces, then review each information asset with each threat it
faces and create a list of vulnerabilities.
Vulnerabilities: Specific avenues from which threat agents can exploit to attack an
information asset are called vulnerabilities.
They are chinks in the armor: a flaw or weakness in an information asset, security
procedure, design, or control that could be exploited accidentally or on purpose to
breach security
Examine how each threat could be perpetrated and list organization’s assets and
vulnerabilities
Process works best when people with diverse backgrounds within organization work
iteratively in a series of brainstorming sessions
At end of risk identification process, list of assets and their vulnerabilities is identified
and prioritized. This list is called as the TVA Worksheet (Threats-Vulnerabilities-
Assets)
Risk Assessment
After identifying the organization’s information assets and the threats and
vulnerabilities, you can evaluate the relative risk for each of the vulnerabilities.
This process is called risk assessment. It assigns a risk rating or score to each
information asset.
• Risk assessment evaluates the relative risk for each vulnerability
• Assigns a risk rating or score to each information asset.
• This number is helpful in gauging the relative risk to each vulnerable asset and
used to find risk rating.
Steps in Risk Assessment
1. Introduction to Risk Assessment
2. Likelihood
3. Risk Determination
4. Identify Possible Controls
5. Documenting the Results of Risk Assessment
Risk = (It is the likelihood of the occurrence of a vulnerability * the value of the
information asset) – (The percentage of risk mitigated by current controls + The
uncertainty of current knowledge of the vulnerability.
Likelihood
It is the probability that a specific vulnerability will be the object of a successful
attack.
• Assign numeric value to likelihood: number between 0.1 (low) and 1.0 (high),
or a number between 1 and 100 (as per NIST recommendations).
• Zero not used since vulnerabilities with zero likelihood are removed from
asset/vulnerability list.
• Choose a rating system based on professionalism, experience and judgement.
• Use selected rating system consistently.
• Use external references for values that have been reviewed/adjusted for your
circumstances.
For example:
• The likelihood of a fire has been estimated mathematically or statistically for
each type of structure.
• The likelihood that any given e-mail contains a virus or worm has been
researched.
• The number of network attacks can be forecast based on how many assigned
network addresses the organization has.
Risk Determination
To determine the relative risk assessment:
Risk EQUALS Likelihood of vulnerability occurrence TIMES value (or impact) MINUS
percentage risk already controlled PLUS an element of uncertainty
Example: 1) Information asset A has a value score of 50 and has one vulnerability.
Vulnerability 1 has a likelihood of 1.0 with no current controls. You estimate that
assumptions and data are 90 percent accurate.
Risk rating factor of Asset A: Vulnerability 1
Risk =(50 X 1.0)- 0% +10% where
Risk =(50 X 1. 0) –((50 X 1.0)X 0.0)+ ((50X1.0)X0.1)
Risk =55
2) Information asset B has a value score of 100 and has two vulnerabilities:
Vulnerability 2 has a likelihood of 0.5 with a current control that addresses 50
percent of its risk; vulnerability 3 has a likelihood of 0.1 with no current controls.
You estimate that assumptions and data are 80 percent accurate.
Risk rating factor of Asset B: Vulnerability 2
Risk = (100X0.5) – 50%+ 20%
Risk = (100X0.5) –((100X0.5)X0.5)+ ((100X0.5)X0.2)
Risk = 35
Asset B Vulnerability 3: Risk = (100X0.1) – 0%+ (100X0.1)20% =12
2. Transfer:
The transfer control strategy attempts to shift risk to other assets, other processes,
or other organizations.
Accomplished by rethinking how services are offered, revising deployment models,
outsourcing to other organizations, purchasing insurance, or implementing service
contracts with providers.
One of the eight characteristics of excellent organizations is that they “stick to their
knitting … i.e., stay reasonably close to the business they know.”
3. Mitigate
The mitigate control strategy attempts to reduce the impact caused by the
exploitation of vulnerability through planning and preparation. It requires the
creation of three types of plans
1. the incident response plan,
2. the disaster recovery plan, and
3. the business continuity plan.
DR plan includes the entire set of activities used to recover from an incident.
To limit losses before and during the disaster.
The DR plan focuses more on preparations before the incident and actions to be taken
after the incident.
Business Continuity plan (BC)
This plan is the most strategic and long term of the three plans.
It concentrates on the continuation of business activities if a catastrophic event
occurs, such as the loss of an entire database, building, or operations center.
The BC plan includes planning the steps necessary to ensure the continuation of the
organization when the scope or scale of a disaster exceeds the ability of the DR plan
to restore operations. This can include preparation steps for activation of secondary
data centers, hot sites, or business recovery sites.
4. Accept:
The accept control strategy is the choice to do nothing to protect a vulnerability and
to accept the outcome of its exploitation.
Organization can accept any risk after performing the following:
• Determined the level of risk
• Assessed the probability of attack
• Estimated the potential damage that could occur from attacks
• Performed a thorough cost benefit analysis
• Evaluated controls using each appropriate type of feasibility
• Decided that the function, service, information, or asset did not justify the Cost
of protection.
5. Terminate:
The terminate control strategy directs the organization to avoid those business
activities that introduce uncontrollable risks.
Organization may seek an alternate mechanism to meet customer needs
Each of these plans depends on the ability to detect and respond to an attack as
quickly as possible and relies on the quality of the other plans.
Single Loss Expectancy is the value associated with the most likely loss from an
attack
SLE = asset value × exposure factor (EF)
EF = Percentage of loss that would occur from a given vulnerability being exploited
Expected loss per risk stated in the following equation:
Annualized loss expectancy (ALE) = single loss expectancy (SLE) ×
annualized rate of occurrence (ARO)
CBA determines whether implementing a control is worth of its cost
CBA most easily calculated using ALE from earlier assessments, before
implementation of proposed control:
CBA = ALE(prior) – ALE(post) – ACS
• ALE(prior) is annualized loss expectancy of risk before implementation of
control
• ALE(post) is estimated ALE based on control is in place for a period
• ACS is the annualized cost of the safeguard
Baselining
Residual risk
Developing strong justifications for specific action plans and providing concrete
estimates to implement a control strategy by convince the budget authorities to spend
up to a value to protect the asset from an identified threat.
Another factor to consider is that each control or safeguard affects more than one
asset-threat pair.
Look for a way to implement controls that doesn’t involve such complex, inexact, and
dynamic calculations.