Risk Management-Assessing and Controlling Risks
Risk Management-Assessing and Controlling Risks
Risk Management-Assessing and Controlling Risks
Risk Management
Risk management is the process of identifying vulnerabilities in an organizations information systems and taking carefully reasoned steps to assure the confidentiality, integrity, and availability of all the components in the organizations information systems The primary deliverable from risk assessment was a list of documented vulnerabilities, ranked by criticality of impact
Slide 2
Avoidance
Avoidance attempts to prevent the exploitation of the vulnerability This is the preferred approach, as it seeks to avoid risk in its entirety rather than dealing with it after it has been realized Accomplished through countering threats, removing vulnerabilities in assets, limiting access to assets, and/or adding protective safeguards Three areas of control:
Policy Training and education Technology
Principles of Information Security - Chapter 5 Slide 4
Transference
Transference is the control approach that attempts to shift the risk to other assets, other processes, or other organizations If an organization does not already have quality security management and administration experience, it should hire individuals or firms that provide such expertise This allows the organization to transfer the risk associated with the management of these complex systems to another organization with established experience in dealing with those risks
Principles of Information Security - Chapter 5 Slide 5
Mitigation
Mitigation attempts to reduce the impact of exploitation through planning and preparation Three types of plans:
disaster recovery planning (DRP) business continuity planning (BCP) incident response planning (IRP)
The most common of the mitigation procedures is the disaster recovery plan or DRP The actions to take while the incident is in progress are defined in the incident response plan or IRP Longer term issues are handled in the business continuity plan or BCP
Principles of Information Security - Chapter 5 Slide 6
Slide 7
Acceptance
Acceptance of risk is doing nothing to close a vulnerability and to accept the outcome of its exploitation Acceptance is valid only when:
Determined the level of risk Assessed the probability of attack Estimated the potential damage Performed a thorough cost benefit analysis Evaluated controls using each appropriate feasibility Decided that the particular function, service, information, or asset did not justify the cost of protection
Risk appetite describes the degree to which an organization is willing to accept risk as a tradeoff to the expense of applying controls
Principles of Information Security - Chapter 5
Slide 8
Slide 10
Slide 11
Categories of controls
Controlling risk through avoidance, mitigation, or transference may be accomplished by implementing controls or safeguards One approach to selecting controls is by category:
Control Function Architectural Layer Strategy Layer Information Security Principles
Principles of Information Security - Chapter 5 Slide 12
Control Function
Controls or safeguards designed to defend the vulnerability are either preventive or detective Preventive controls stop attempts to exploit vulnerability by implementing enforcement of an organizational policy or a security principle, such as authentication or confidentiality Detective controls warn of violations of security principles, organizational policies, or attempts to exploit vulnerabilities Detective controls use techniques such as audit trails, intrusion detection, or configuration monitoring
Principles of Information Security - Chapter 5 Slide 13
Architectural Layer
Some controls apply to one or more layers of an organizations technical architecture Among the architectural layer designators in common use are:
organizational policy external networks extranets (or demilitarized zones) Intranets (WAN and LAN) network devices that interface network zones (switches, routers, firewalls, and hubs) systems (computers for mainframe, server or desktop use) applications
Principles of Information Security - Chapter 5 Slide 14
Strategy Layer
Controls are sometimes classified by the risk control strategy they operate within:
avoidance mitigation transference acceptance
Slide 15
The formal process to document this is called a cost benefit analysis or an economic feasibility study
Slide 18
Slide 19
CBA: Benefits
Benefit is the value that the organization recognizes by using controls to prevent losses associated with a specific vulnerability This is usually determined by valuing the information asset or assets exposed by the vulnerability and then determining how much of that value is at risk
Slide 20
Slide 21
ARO is simply how often you expect a specific type of attack to occur, per year SLE is the calculation of the value associated with the most likely loss from an attack EF is the percentage loss that would occur from a given vulnerability being exploited
Principles of Information Security - Chapter 5 Slide 23
CBA: Formula
CBA is whether or not the control alternative being evaluated is worth the associated cost incurred to control the specific vulnerability While many CBA techniques exist, for our purposes, the CBA is most easily calculated using the ALE from earlier assessments CBA = ALE(prior) ALE(post) ACS Where:
ALE prior is the Annualized Loss Expectancy of the risk before the implementation of the control ALE post is the ALE examined after the control has been in place for a period of time ACS is the Annual Cost of the Safeguard
Principles of Information Security - Chapter 5 Slide 24
Benchmarking
Rather than use the financial value of information assets, review peer institutions to determine what they are doing to protect their assets (benchmarking) When benchmarking, an organization typically uses one of two measures:
Metrics-based measures are comparisons based on numerical standards Process-based measures examine the activities performed in pursuit of its goal, rather than the specifics of how goals were attained
Slide 25
Slide 27
Problems
The biggest problem with benchmarking in information security is that organizations dont talk to each other Another problem with benchmarking is that no two organizations are identical A third problem is that best practices are a moving target One last issue to consider is that simply knowing what was going on a few years ago, as in benchmarking, doesnt necessarily tell us what to do next
Principles of Information Security - Chapter 5 Slide 30
Baselining
Baselining is the analysis of measures against established standards In information security, baselining is comparing security activities and events against the organizations future performance When baselining it is useful to have a guide to the overall process
Slide 31
Organizational Feasibility
Organizational feasibility examines how well the proposed information security alternatives will contribute to the efficiency, effectiveness, and overall operation of an organization Above and beyond the impact on the bottom line, the organization must determine how the proposed alternatives contribute to the business objectives of the organization
Slide 32
Operational Feasibility
Addresses user acceptance and support, management acceptance and support, and the overall requirements of the organizations stakeholders Sometimes known as behavioral feasibility, because it measures the behavior of users One of the fundamental principles of systems development is obtaining user buy-in on a project and one of the most common methods for obtaining user acceptance and support is through user involvement obtained through three simple steps: Communicate Educate Involve
Principles of Information Security - Chapter 5 Slide 33
Technical Feasibility
The project team must also consider the technical feasibilities associated with the design, implementation, and management of controls Examines whether or not the organization has or can acquire the technology necessary to implement and support the control alternatives
Slide 34
Political Feasibility
For some organizations, the most significant feasibility evaluated may be political Within organizations, political feasibility defines what can and cannot occur based on the consensus and relationships between the communities of interest The limits placed on an organizations actions or behaviors by the information security controls must fit within the realm of the possible before they can be effectively implemented, and that realm includes the availability of staff resources
Principles of Information Security - Chapter 5 Slide 35
Slide 36
Residual Risk
When we have controlled any given vulnerability as much as we can, there is often risk that has not been completely removed or has not been completely shifted or planned for This remainder is called residual risk To express it another way,
Residual Risk is a combined function of (1) a threat less the effect of some threat-reducing safeguards (2) a vulnerability less the effect of some vulnerability-reducing safeguards (3) an asset less the effect of some asset valuereducing safeguards.
Principles of Information Security - Chapter 5 Slide 37
Slide 38
Documenting Results
At minimum, each information assetvulnerability pair should have a documented control strategy that clearly identifies any residual risk remaining after the proposed strategy has been executed Some organizations document the outcome of the control strategy for each information assetvulnerability pair as an action plan This action plan includes concrete tasks, each with accountability assigned to an organizational unit or to an individual
Principles of Information Security - Chapter 5 Slide 39
Slide 40
Qualitative Measures
The spectrum of steps described above was performed with real numbers or best-guess estimates of real numbers - this is known as a quantitative assessment However, an organization could determine that it couldnt put specific numbers on these values Fortunately, it is possible to repeat these steps using estimates based on a qualitative assessment Instead of using specific numbers, ranges or levels of values can be developed simplifying the process
Principles of Information Security - Chapter 5 Slide 41
Delphi Technique
One technique for accurately estimating scales and values is the Delphi Technique The Delphi Technique, named for the Oracle at Delphi, is a process whereby a group of individuals rate or rank a set of information The individual responses are compiled and then returned to the individuals for another iteration This process continues until the group is satisfied with the result
Slide 42
Slide 43