Assessing Current Network Concerns Lesson 5. CERT/CC Stats.

Slides:



Advertisements
Similar presentations
Information Risk Management Key Component for HIPAA Security Compliance Ann Geyer Tunitas Group
Advertisements

Project Management Gaafar 2007 / 1 This Presentation is uses information from PMBOK Guide 2000 Project Management Risk Management* Dr. Lotfi Gaafar.
Chapter 10 Ranking and Value Management of Computer System Performance.
Introducing Computer and Network Security
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
By: Ashwin Vignesh Madhu
Planning for Contingencies
Computer Security: Principles and Practice
Sanjay Goel, School of Business/Center for Information Forensics and Assurance University at Albany Proprietary Information 1 Unit Outline Information.
Risk Assessment Frameworks
Introduction to Network Defense
1 BUSINESS CONTINUITY AND DISASTER RECOVERY PLANNING Reducing your Risk Profile MIDWEST DATA RECOVERY INC.
CERN IT Department CH-1211 Genève 23 Switzerland t ITIL and Business Continuity (Service Perspective) Hepix 2012 Conference Prague,
Visual 3. 1 Lesson 3 Risk Assessment and Risk Mitigation.
Project Risk Management. The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding.
An Educational Computer Based Training Program CBTCBT.
What if you suspect a security incident or software vulnerability? What if you suspect a security incident at your site? DON’T PANIC Immediately inform:
1 Introduction to Security Chapter 5 Risk Management: The Foundation of Private Security.
Audit objectives, Planning The Audit
Introducing Computer and Network Security. Computer Security Basics What is computer security? –Answer depends on the perspective of the person you’re.
Presented to President’s Cabinet. INTERNAL CONTROLS are the integration of the activities, plans, attitudes, policies and efforts of the people of an.
PATCH MANAGEMENT: Issues and Practical Solutions Presented by: ISSA Vancouver Chapter March 4, 2004.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
Policy Review (Top-Down Methodology) Lesson 7. Policies From the Peltier Text, p. 81 “The cornerstones of effective information security programs are.
INFORMATION SECURITY & RISK MANAGEMENT SZABIST – Spring 2012.
Private & Confidential1 (SIA) 13 Enterprise Risk Management The Standard should be read in the conjunction with the "Preface to the Standards on Internal.
MODULE 12 Control Audit And Security Of Information System 12.1 Controls in Information systems 12.2 Need and methods of auditing Information systems 12.3.
Management & Development of Complex Projects Course Code MS Project Management Perform Qualitative Risk Analysis Lecture # 25.
Security Standards and Threat Evaluation. Main Topic of Discussion  Methodologies  Standards  Frameworks  Measuring threats –Threat evaluation –Certification.
Security Policies and Procedures. cs490ns-cotter2 Objectives Define the security policy cycle Explain risk identification Design a security policy –Define.
Audit Planning Process
IT 499 Bachelor Capstone Week 4. Adgenda Administrative Review UNIT Four UNIT Five Project UNIT Six Preview Project Status Summary.
INFORMATION SECURITY MANAGEMENT L ECTURE 3: P LANNING FOR C ONTINGENCIES You got to be careful if you don’t know where you’re going, because you might.
Introducing Project Management Update December 2011.
IT Risks and Controls Revised on Content Internal Control  What is internal control?  Objectives of internal controls  Types of internal controls.
Introduction to Information Security
Presented to Managers. INTERNAL CONTROLS are the integration of the activities, plans, attitudes, policies and efforts of the people of an organization.
SecSDLC Chapter 2.
karRKb;RKghaniP½yrbs;KMerag Project Risks Management
Session 2.02: Achieving an Adequate Level of Security Without Hindering Patient Care Jody S. Hawkins, ISO Dallas, Texas.
Chap 8: Administering Security.  Security is a combination Technical – covered in chap 1 Administrative Physical controls SE571 Security in Computing.
Slide 1 Security Engineering. Slide 2 Objectives l To introduce issues that must be considered in the specification and design of secure software l To.
(c) 2007 Charles G. Gray1 IT Risk Management, Planning and Mitigation TCOM 5253 / MSIS 4253 Detailed Risk Analysis 18 October 2007 Charles G. Gray.
1 Certification and Accreditation CS Unit 4:RISK MANAGEMENT Jesus Gonzalez Kalpana Bahunoothula Jocelyne Farah.
E-Commerce E-Commerce Security?? Instructor: Safaa S.Y. Dalloul E-Business Level Try to be the Best.
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.
Assessing Current Network Concerns Lesson 5. The Assessment Two important elements you will need to determine in order to produce a valuable assessment.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Dr. Mark Gaynor, Dr. Feliciano Yu, Bryan Duepner.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 16 – IT Security.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
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.
Chapter 3 “A Case Study of Effectively Implemented Information Systems Security Policy[1]” John Doran, CST554, Spring 2008.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-VI)
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.
Risk Controls in IA Zachary Rensko COSC 481. Outline Definition Risk Control Strategies Risk Control Categories The Human Firewall Project OCTAVE.
Principles of Information Security, Fourth Edition Risk Management Ch4 Part I.
Objectives We’ll answer the following: What is a FRAP? Why a FRAP?
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Managing Project Risk – A simplified approach Presented by : Damian Leonard.
MANAGEMENT of INFORMATION SECURITY, Fifth Edition.
An Overview on Risk Management
COMP3357 Managing Cyber Risk
Here are some top tips to help you bake responsible data into your project design:.
IS4550 Security Policies and Implementation
Cybersecurity Threat Assessment
TECHNOLOGY ASSESSMENT
Information Security Risks; All-in-One Terminology
HIPAA Security Risk Assessment (SRA)
MANAGEMENT of INFORMATION SECURITY, Fifth Edition
Presentation transcript:

Assessing Current Network Concerns Lesson 5

CERT/CC Stats

CERT/CC

The Assessment Two important elements you will need to determine in order to produce a valuable assessment Determine the value of the information and resources that are to be protected Determine the threats that may exist which jeopardize the confidentiality, integrity, or availability of the information and resources

Asset Valuation Can be qualitative or quantitative Business Impact Assessment/Analysis (BIA): used to determine what is important for inclusion in a BCP/DRP (check to see if they have accomplished one already). Will assess how unavailability of each system/process would affect the organization. Business Continuity Plan (BCP) and Disaster Recovery Plans: Desire is to protect the operations of the organization, not just the computing systems. May/ Should have done a BIA as part of one of these and you can possibly use the results to save some time.

Goals of a BIA Identification of the processes that are critical to the profitability and continued viability of the organization Quantification of the financial and operational impact of an outage over time A determination of the recovery priority, recovery time, and recovery point for each application that supports a critical business process. For our purposes we want to use the BIA to help us determine what needs to be protected and how valuable these assets are.

Asset Valuation So, either using the BIA or the BIA process, we should know: What the essential processes are for the organization. What the process consists of/requires (in terms of information and resources). What the value is of these processes (or more appropriately, what the impact is on the organization should they be lost). Knowing what the assets are can help us better determine what the threat might be to the organization. May also be used later when we start evaluating acceptable residual risks.

Threats to the systems “To control the risks of operating an information system, managers and users must know the vulnerabilities of the system and the threats that might exploit them.” “Knowledge of the threat environment allows management to implement the most cost- effective security measures.” “In some cases, managers may find it most cost-effective to simply tolerate the expected loss.”

Types of Threats Computer Viruses Computer Hackers Denial of Service Attacks Mistakes Abuse of can become public affecting image of organization Disgruntled Employees Industrial Spying Which one of these is most likely to occur? Which will have the greatest impact? Which will be the hardest to protect against?

Prioritizing Risks and Threats According to the text: “Once the possible threats have been identified, it is necessary to prioritize those risks so that the NVA can focus on those of highest concern. To accomplish this task as quickly as possible, it is necessary to assemble a team of interested employees. This team will determine the probability that the identified risk might occur and what its impact would be if it did occur.” What’s the chance that a “team of interested employees” will be able to “determine the probability that the identified risk might occur and what its impact would be if it did occur”? Thus, the reason to obtain the BIA if available.

Prioritizing Risks and Threats To simplify things a bit, try these definitions: Impact: a measure of the magnitude of loss or harm on the value of an asset Low impact: when the business objective or mission of enterprise is not significantly affected. Medium impact: when the event is limited to a business objective or a business unit is affected High impact: when the entire business or mission of the enterprise is affected Probability: the chance that an event will occur or that a specific loss value will be incurred should the event occur Low probability: highly unlikely that the risk will occur during the next year Medium probability: possible that the risk will occur during the next year High probability: very likely that the risk will occur within the next year (don’t like the term “risk” being used in the above)

What to look at Text discusses how to prioritize what to look at during the assessment. Impact LowMediumHigh Low147 Prob.Medium258 High369 Concentrate first on items of level 6 or higher. If time permits continue with levels 5 then 4. Impact is one thing, how do you (or the team) determine the probability of an event occurring?

Checklists Lots of checklists available out there, can prove very useful. Do not rely solely on checklists – use them as a guide or a starting point. 3 included as appendices in text: ISO Self Assessment Questionnaire Lots of good information covering a variety of areas. Look at and adapt to specific environment. Network Vulnerability Assessment Checklist Again, some good, useful information. Look at and adapt. Windows Server Checklists/Security Guides Focused checklists such as this often very useful – can contain very valuable data. This one a bit light, others available on line (check NIST)

Problems with checklists What do you do with the results? Great, so I have 20-Y’s, 32-N’s, and 4-N/A’s, now what? Does this mean that I’m in good shape, bad shape, or somewhere in between? Are all questions of equal importance? Do you need to add some sort of weighting system to help identify the most critical? Checklists might overlook key components of your security plan, may also include unimportant aspects. Checklists need to be tailored.

Composition of the Assessment Team So, who should be part of an assessment team? Need to cover all of the areas of concern Information protection Operations Telecommunications Systems support Network management Desktop deployment Account administration Auditing Physical Security Ideally, you’d have an “expert” in each of these areas. In practice, you may not have that many folks to draw on so a SME you can ask questions of may be all you can hope for.

Assessment Timeline How long should an assessment take? Book mentions that one can take as long as 12 weeks. In reality the real answer is “it depends”. Assessment can take considerably longer than 12 weeks or can be as short as only a few weeks. Depends on scope (especially size). In establishing the timeline, pay attention to: Activities that must be accomplished before others Activities that you can conduct in parallel Make sure you allow sufficient time to write, and review the final report. Might include a preliminary “outbrief” for organization upon completion of the assessment, to be followed by official report at a later date.

Timeline for class assessments For us, driven by academic calendar A bit artificial but a constraint we must live with Final report to be presented during finals week External to be performed before internal, why? Internal and review of policies etc. can be done concurrently Need approximately two weeks for each part Public presence review, if requested, can be done quickly and should be accomplished before external begins How will you use Spring Break

Summary What is the importance and significance of this material? How does this topic fit into the subject of “Security Risk Analysis”?