Dr. Gerry Firmansyah CID 610 - Business Continuity and Disaster Recovery Planning for IT (W-XIV)

Slides:



Advertisements
Similar presentations
Museum Presentation Intermuseum Conservation Association.
Advertisements

Risk Analysis Fundamentals and Application Robert L. Griffin International Plant Protection Convention Food and Agriculture Organization of the UN.
Information Risk Management Key Component for HIPAA Security Compliance Ann Geyer Tunitas Group
National Protection and Programs Directorate Department of Homeland Security The Office of Infrastructure Protection Cybersecurity Brief [Date of presentation]
Smart Grid - Cyber Security Small Rural Electric George Gamble Black & Veatch
Service Design – Section 4.5 Service Continuity Management.
CST 481/598 Many thanks to Jeni Li.  Potential negative impact to an asset  Probability of a loss  A function of three variables  The probability.
Weakness is a better teacher than strength.
Introducing Computer and Network Security
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Stephen S. Yau CSE , Fall Risk Management.
Principles of Information Security, 2nd Edition1 Risk Management.
Computer Security: Principles and Practice
Lecture 8: Risk Management Controlling Risk
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Risk Management Vs Risk avoidance William Gillette.
Risk Management Chapter 4.
Risk Analysis COEN 250.
Introduction to Network Defense
1 BUSINESS CONTINUITY AND DISASTER RECOVERY PLANNING Reducing your Risk Profile MIDWEST DATA RECOVERY INC.
SEC835 Database and Web application security Information Security Architecture.
Project Risk Management. The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding.
TEL2813/IS2820 Security Management
EQAA 11th Session Jamil Kalat-Malho Jong Ho Lee
1 Introduction to Security Chapter 5 Risk Management: The Foundation of Private Security.
How Hospitals Protect Your Health Information. Your Health Information Privacy Rights You can ask to see or get a copy of your medical record and other.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Project Management By: Dr Madhu Fernando Project Risk Management
Risk Assessment and Management. Objective To enable an organisation mission accomplishment, by better securing the IT systems that store, process, or.
Eliza de Guzman HTM 520 Health Information Exchange.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Alaa Mubaied Risk Management Alaa Mubaied
NFPA 1600 Disaster/Emergency Management and Business Continuity Programs.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Introduction and Overview of Information Security and Policy By: Hashem Alaidaros 4/10/2015 Lecture 1 IS 332.
High Assurance Products in IT Security Rayford B. Vaughn, Mississippi State University Presented by: Nithin Premachandran.
INFORMATION SECURITY MANAGEMENT L ECTURE 8: R ISK M ANAGEMENT C ONTROLLING R ISK You got to be careful if you don’t know where you’re going, because you.
Dr. Mark Gaynor, Dr. Feliciano Yu, Bryan Duepner.
The NIST Special Publications for Security Management By: Waylon Coulter.
RISK MANAGEMENT: CONTROLLING RISK IN INFORMATION SECURITY By Collin Donaldson.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
Principles of Information Security, Fourth Edition Risk Management Ch4 Part II.
INFORMATION SECURITY MANAGEMENT L ECTURE 8: R ISK M ANAGEMENT C ONTROLLING R ISK You got to be careful if you don’t know where you’re going, because you.
INFORMATION ASSURANCE POLICY. Information Assurance Information operations that protect and defend information and information systems by ensuring their.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-I)
Computer Science / Risk Management and Risk Assessment Nathan Singleton.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Headquarters U.S. Air Force
Cybersecurity: Risk Management
Information Systems Security
Risk management «Once we know our weaknesses, they cease to do us any harm.» G.C. Lichtenberg.
MANAGEMENT of INFORMATION SECURITY, Fifth Edition
Risk management.
INFORMATION RISK MANAGEMENT
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
8 Managing Risk (Premium).
Air Carrier Continuing Analysis and Surveillance System (CASS)
Cyber defense management
Unit 7 – Organisational Systems Security
RISK ASSESSMENT TOOL PREVIEW
The Importance of Project Risk Management
Information Security Risk Management
Chapter 7: RISK ASSESSMENT, SECURITY SURVEYS, AND PLANNING
Effective Risk Management in Decision Making Process
PFMEA Summary Process Steps
MANAGEMENT of INFORMATION SECURITY, Fifth Edition
RISK MANAGEMENT.
Presentation transcript:

Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XIV)

RISK MITIGATION RISK MITIGATION OPTIONS RISK MITIGATION STRATEGY APPROACH FOR CONTROL IMPLEMENTATION CONTROL CATEGORIES COST-BENEFIT ANALYSIS RESIDUAL RISK

RISK MITIGATION OPTIONS Risk mitigation, the second process of risk management, involves prioritizing, evaluating, and implementing the appropriate risk-reducing controls recommended from the risk assessment process. to use the least-cost approach and implement the most appropriate controls to decrease mission risk to an acceptable level, with minimal adverse impact on the organization’s resources and mission. Risk Mitigation Options : Risk Assumption. To accept the potential risk and continue operating the IT system or to implement controls to lower the risk to an acceptable level Risk Avoidance. To avoid the risk by eliminating the risk cause and/or consequence (e.g., forgo certain functions of the system or shut down the system when risks are identified) Risk Limitation. To limit the risk by implementing controls that minimize the adverse impact of a threat’s exercising a vulnerability (e.g., use of supporting, preventive, detective controls) Risk Planning. To manage risk by developing a risk mitigation plan that prioritizes, implements, and maintains controls Research and Acknowledgment. To lower the risk of loss by acknowledging the vulnerability or flaw and researching controls to correct the vulnerability Risk Transference. To transfer the risk by using other options to compensate for the loss, such as purchasing insurance.

RISK MITIGATION STRATEGY When vulnerability (or flaw, weakness) exists ➞ implement assurance techniques to reduce the likelihood of a vulnerability’s being exercised. When a vulnerability can be exercised ➞ apply layered protections, architectural designs, and administrative controls to minimize the risk of or prevent this occurrence. When the attacker’s cost is less than the potential gain ➞ apply protections to decrease an attacker’s motivation by increasing the attacker’s cost (e.g., use of system controls such as limiting what a system user can access and do can significantly reduce an attacker’s gain). When loss is too great ➞ apply design principles, architectural designs, and technical and nontechnical protections to limit the extent of the attack, thereby reducing the potential for loss.

APPROACH FOR CONTROL IMPLEMENTATION Address the greatest risks and strive for sufficient risk mitigation at the lowest cost, with minimal impact on other mission capabilities. Step 1Prioritize Actions : Actions ranking from High to Low Step 2Evaluate Recommended Control Options : List of feasible controls Step 3Conduct Cost-Benefit Analysis : Cost-benefit analysis describing the cost and benefits of implementing or not implementing the controls Step 4Select Control : Selected control(s) Step 5Assign Responsibility : List of responsible persons Step 6Develop a Safeguard Implementation Plan : Safeguard implementation plan Step 7Implement Selected Control(s) : Residual risk

CONTROL CATEGORIES Technical Security Controls

COST-BENEFIT ANALYSIS A cost-benefit analysis for proposed new controls or enhanced controls encompasses the following: Determining the impact of implementing the new or enhanced controls Determining the impact of not implementing the new or enhanced controls Estimating the costs of the implementation. These may include, but are not limited to, the following: – Hardware and software purchases – Reduced operational effectiveness if system performance or functionality is reduced for increased security – Cost of implementing additional policies and procedures – Cost of hiring additional personnel to implement proposed policies, procedures, or services – Training costs – Maintenance costs Assessing the implementation costs and benefits against system and data criticality to determine the importance to the organization of implementing the new controls, given their costs and relative impact.

RESIDUAL RISK Organizations can analyze the extent of the risk reduction generated by the new or enhanced controls in terms of the reduced threat likelihood or impact, the two parameters that define the mitigated level of risk to the organizational mission. Eliminating some of the system’s vulnerabilities (flaws and weakness), thereby reducing the number of possible threat-source/vulnerability pairs Adding a targeted control to reduce the capacity and motivation of a threat-source For example, a department determines that the cost for installing and maintaining add-on security software for the stand-alone PC that stores its sensitive files is not justifiable, but that administrative and physical controls should be implemented to make physical access to that PC more difficult (e.g., store the PC in a locked room, with the key kept by the manager). Reducing the magnitude of the adverse impact (for example, limiting the extent of a vulnerability or modifying the nature of the relationship between the IT system and the organization’s mission).