WSU IT Risk Assessment Process

Slides:



Advertisements
Similar presentations
Copyright © 2014 American Water Works Association Water Sector Approach to Process Control System Security.
Advertisements

HIPAA: FEDERAL REGULATIONS REGARDING PATIENT SECURITY.
Auditing Computer Systems
DoD Information Technology Security Certification and Accreditation Process (DITSCAP) Phase III – Validation Thomas Howard Chris Pierce.
Security Controls – What Works
Information Security Policies and Standards
Software Security Threats Threats have been an issue since computers began to be used widely by the general public.
Network Security Testing Techniques Presented By:- Sachin Vador.
ITS Offsite Workshop 2002 PolyU IT Security Policy PolyU IT/Computer Systems Security Policy (SSP) By Ken Chung Senior Computing Officer Information Technology.
COSO Framework A company should include IT in all five COSO components: –Control Environment –Risk Assessment –Control activities –Information and communication.
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Computer Security: Principles and Practice
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Stephen S. Yau CSE , Fall Security Strategies.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Session 3 – Information Security Policies
Network security policy: best practices
Website Hardening HUIT IT Security | Sep
SEC835 Database and Web application security Information Security Architecture.
Lesson 8-Information Security Process. Overview Introducing information security process. Conducting an assessment. Developing a policy. Implementing.
Network Security Policy Anna Nash MBA 737. Agenda Overview Goals Components Success Factors Common Barriers Importance Questions.
Information Systems Security Computer System Life Cycle Security.
Security Baseline. Definition A preliminary assessment of a newly implemented system Serves as a starting point to measure changes in configurations and.
Health Insurance Portability and Accountability Act of 1996 (HIPAA) Proposed Rule: Security and Electronic Signature Standards.
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.
Security Professional Services. Security Assessments Vulnerability Assessment IT Security Assessment Firewall Migration Custom Professional Security Services.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
Environment for Information Security n Distributed computing n Decentralization of IS function n Outsourcing.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Sample Security Model. Security Model Secure: Identity management & Authentication Filtering and Stateful Inspection Encryption and VPN’s Monitor: Intrusion.
April 14, A Watershed Date in HIPAA Privacy Compliance: Where Should You Be in HIPAA Security Compliance and How to Get There… John Parmigiani National.
OCTAVE-S on TradeSolution Inc.. Introduction Phase 1: Critical Assets and threats Phase 2: Critical IT Components Phase 3: Changes Required in current.
Lesson 9-Information Security Best Practices. Overview Understanding administrative security. Security project plans. Understanding technical security.
Ali Pabrai, CISSP, CSCS ecfirst, chairman & ceo Preparing for a HIPAA Security Audit.
Cloud Computing Security Keep Your Head and Other Data Secure in the Cloud Lynne Pizzini, CISSP, CISM, CIPP Information Systems Security Officer Information.
Note1 (Admi1) Overview of administering security.
Converting Policy to Reality Designing an IT Security Program for Your Campus 2 nd Annual Conference on Technology and Standards May 3, 2005 Jacqueline.
The IT Vendor: HIPAA Security Savior for Smaller Health Plans?
5/18/2006 Department of Technology Services Security Architecture.
Module 12: Responding to Security Incidents. Overview Introduction to Auditing and Incident Response Designing an Audit Policy Designing an Incident Response.
E-Commerce E-Commerce Security?? Instructor: Safaa S.Y. Dalloul E-Business Level Try to be the Best.
Dr. Mark Gaynor, Dr. Feliciano Yu, Bryan Duepner.
2015 TCPA WASHINGTON SUMMIT | SEPT. 27TH-29TH | WASHINGTON DC The Anatomy of a Breach Phillip Naples, Pritchard & Jerden, Inc. Jeremy Henley, ID Experts.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
The Payment Card Industry Data Security Standard (PCI DSS) is a proprietary information security standard for organizations that handle branded credit.
By: Mark Reed.  Protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction.
Risk Assessments in Many Flavors George J. Dolicker, CISA, CISSP.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
EECS David C. Chan1 Computer Security Management Session 1 How IT Affects Risks and Assurance.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XIV)
Incident Response Strategy and Implementation Anthony J. Scaturro University IT Security Officer September 22, 2004.
Payment Card Industry (PCI) Rules and Standards
Information Systems Security
Safeguarding CDI - compliance with DFARS
Information Security Program
INFORMATION SYSTEMS SECURITY AND CONTROL.
ISSeG Integrated Site Security for Grids WP2 - Methodology
Critical Security Controls
INDULGENCE There is no need for oversight or management direction. All staff members are superstars and act in the best interest of the company.
Secure Software Confidentiality Integrity Data Security Authentication
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
Introduction to the Federal Defense Acquisition Regulation
Security in Networking
CYB 110 Competitive Success/snaptutorial.com
CYB 110 Teaching Effectively-- snaptutorial.com
NCHER Knowledge Symposium Federal Contractor/TPS Session
Cybersecurity Special Public Meeting/Commission Workshop for Natural Gas Utilities September 27, 2018.
County HIPAA Review All Rights Reserved 2002.
Introduction to the PACS Security
Presentation transcript:

WSU IT Risk Assessment Process 5/2/2018 WSU IT Risk Assessment Process March 22, 2017 Keela Ruppenthall Information Security Analyst Template D Plain-white-dark

Background Structured Assessment of Operational Environment 5/2/2018 Background Structured Assessment of Operational Environment Evaluate adequacy of existing security controls Internal and/or external Determine Risk Level for WSU Information Systems and Services Identify Cost-Effective Security Requirements for Systems/Services Template D Plain-white-dark

Risk Assessment Types Contract Risk Assessment 5/2/2018 Risk Assessment Types Contract Risk Assessment WSU BPPM 70.24: Purchasing – Acquisition of Computer Equipment, Services, or Software Information System or Service Risk Assessment Any IT information System or Service Applications Servers Networks Any process or procedure by which systems are administered and/or maintained Contracts - POLICY Each department is responsible for complying with the computer purchasing requirements and procedures outlined in 70.24. ITS reviews certain it related purchases of equipment, software, and cloud services in coordination with WSU Purchasing Services for system compatibility, network connectivity and data security purposes. Additional forms or information may be required in order to proceed with such purchases. providers of external information system services comply with organizational information security requirements IS RA – Policy RA- 3 Conducts an assessment of risk, including the likelihood and magnitude of harm, from the unauthorized access, use, disclosure, disruption, modification, or destruction of the information system and the information it processes, stores, or transmit Documents, Reviews, and Disseminates risk assessment results Updates the risk assessment regularly or whenever there are significant changes to the information system or environment of operation (including the identification of new threats and vulnerabilities), or other conditions that may impact the security state of the system. RA- 5 Scans for vulnerabilities in the information system and hosted applications Analyzes vulnerability scan reports and results Remediates legitimate vulnerabilities Template D Plain-white-dark

Contract Risk Assessment 5/2/2018 Contract Risk Assessment WSU BPPM 70.24: Purchasing – Acquisition of Computer Equipment, Services, or Software Information Services Review Questionnaire for Technology Contracts and Purchases computer equipment, services, or software  purchases under $10,000 that require a signed contract or an agreement purchases costing in excess of $10,000 BPPM 70.25: Information Security Risk Assessment (draft) Requirement Clarification Updated Questionnaire Each department is responsible for complying with the computer purchasing requirements and procedures outlined in this policy. departments are to complete an Information Services (IS) Review Questionnaire for Technology Contracts and Purchases The department's area technology officer (ATO) or senior ITS staff member: Completes and signs the IS review questionnaire; Attaches a Department Requisition and any applicable supporting documentation to process the purchase with the vendor (see 70.10); and Submits the packet to Purchasing Services. WSU Information Technology Services (ITS) reviews purchases of equipment, software, and cloud services for system compatibility, network connectivity and data security purposes Template D Plain-white-dark

Contract Risk Level Questionnaire Responses Verify compliance with WSU information security requirements Uncover Impact/Likelihood Assign a Risk Classification Level Purchasing Services and/or Contract Office Uses rating to determine whether or not to proceed Risk Level of HIGH should be investigated further

Information System/Service Risk Assessment 5/2/2018 Information System/Service Risk Assessment Repeat Template D Plain-white-dark

Step 1: Prepare for Assessment 5/2/2018 Step 1: Prepare for Assessment Risk Assessment Team Determine System/Service Scope Rules Of Engagement Members Departmental Managers Departmental Technical Managers Information Security Services (ISS) ISS Generates Risk Assessment Report Package Risk Assessment Results Living Artifact Updated periodically Begin Data Collection Nature of the Risk Assessment Risk Assessments help WSU determine the appropriate level of security required for the system to support the development of a System Security Plan for proposed and existing WSU IT Systems and Services. Required security controls will be selected based on the IT System or Service data confidentiality, integrity, and availability requirements. Rules of Engagement Rules of Engagement (ROE) are designed to describe proper notifications and disclosures between the owner of a tested system and the Risk Assessment team. In particular, a ROE includes information about targets of automated scans and IP address origination information of automated scans (and other testing tools). ROE’s must be established, with Departmental Manager signature approval, prior to testing. Data Collection The data collection phase will include identifying and interviewing key personnel within the organization and conducting document reviews. Interviews will be focused on the operating environment. Document reviews provide the risk assessment team with the basis on which to evaluate compliance with policy and procedure. Template D Plain-white-dark

Documentation Request 5/2/2018 Documentation Request Documentation Request Acceptable Use System Maintenance System Security Operations System Security Monitoring Technical Documents Data Flow Diagram Network Diagram Disaster Recovery/ Business Continuity Acceptable Use - Documentation that informs Users of their responsibility, informs users of prohibited activities, data retention policy, etc. System Maintenance – Documentation that supports operating system maintenance, application maintenance, configuration management, etc. System Security Operations – Documents that outline the auditing and audit log review processes, data backup process, virus protection, etc. System Security Monitoring – Documents that outline how the system or service is monitored the system for vulnerabilities, incident response actions, and periodic risk assessments, etc. Disaster Recovery / Business Continuity – Documented recovery strategy, recovery procedures, continuity strategy, emergency response procedures, plan testing, etc. Technical Documents - Network diagram / map, IP addressing scheme, security architecture, previous risk assessments, audit reports, manuals, etc. Template D Plain-white-dark

Step 2: Conduct Assessment

Identify Threat Sources/Events Discussion/Interview Review/Inspect Collected Data ISS Vulnerability Discovery Process NIST SP 800-53A, Rev 4 Controls Compliance Specific Requirements (HIPAA, PCI) WSU’s Enterprise Threat Vectors Testing will not include: Changes to assigned user passwords Attempted logins or other use of systems, with any account name/password Modification of user files or system files Attempted SQL injection and other forms of input parameter testing Telephone modem probes and scans (active and passive) Use of exploit code for leveraging discovered vulnerabilities Intentional viewing of Enrollment Information Technology and Enterprise Computing Services staff email, Internet caches, and/or personnel cookie files Adding user accounts Denial of Service attacks Spoofing or deceiving servers regarding network traffic Exploits that will introduce new weaknesses to the system Altering running system configuration except where denial of service would result Intentional introduction of malicious code (viruses, Trojans, worms, etc.) Password cracking via capture and scanning of authentication databases

Vulnerability Identification 5/2/2018 Vulnerability Identification Template D Plain-white-dark

Determine Likelihood/Impact Each Vulnerability/Threat Pair will be Evaluated Likelihood of Occurrence Magnitude of Impact Risk Level Assigned

Step 3: Communicate Results 5/2/2018 Step 3: Communicate Results Risk Assessment Report List of recommended controls Reduce level of risk to the IT system or service and its data to an acceptable level Risk Mitigation and Tracking POA & M - Plan of Action and Milestones Template D Plain-white-dark

Sample POA & M

Step 4: Maintain Assessment Enables Information Security Continuous Monitoring Ongoing awareness of information security, vulnerabilities, and threats to support organizational risk management decisions Assessment Results Periodically Updated Results Maintained as Compliance Evidence

Continuous Monitoring 5/2/2018 Continuous Monitoring Repeat Template D Plain-white-dark

5/2/2018 Questions? Template D Plain-white-dark