FISMA 101.

Slides:



Advertisements
Similar presentations
HIPAA Security Presentation to The American Hospital Association Dianne Faup Office of HIPAA Standards November 5, 2003.
Advertisements

HIPAA: FEDERAL REGULATIONS REGARDING PATIENT SECURITY.
NIH Security, FISMA and EPLC Lots of Updates! Where do we start? Kay Coupe NIH FISMA Program Coordinator Office of the Chief Information Officer Project.
2010 Region II Conference Corporate Compliance Panel June 3, 2010
Security Controls – What Works
Information Security Policies and Standards
August 9, 2005 UCCSC IT Security at the University of California A New Initiative Jacqueline Craig. Director of Policy Information Resources and.
ITS Offsite Workshop 2002 PolyU IT Security Policy PolyU IT/Computer Systems Security Policy (SSP) By Ken Chung Senior Computing Officer Information Technology.
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
Computer Security: Principles and Practice
Payment Card Industry (PCI) Data Security Standard
Session 3 – Information Security Policies
Network security policy: best practices
Presented by Manager, MIS.  GRIDCo’s intentions for publishing an Acceptable Use Policy are not to impose restrictions that are contrary to GRIDCo’s.
Complying With The Federal Information Security Act (FISMA)
Information Security Compliance System Owner Training Richard Gadsden Information Security Office Office of the CIO – Information Services Sharon Knowles.
NUAGA May 22,  IT Specialist, Utah Department of Technology Services (DTS)  Assigned to Department of Alcoholic Beverage Control  PCI Professional.
Information Security Technological Security Implementation and Privacy Protection.
SEC835 Database and Web application security Information Security Architecture.
General Awareness Training
Network Security Policy Anna Nash MBA 737. Agenda Overview Goals Components Success Factors Common Barriers Importance Questions.
HIPAA PRIVACY AND SECURITY AWARENESS.
Information Systems Security Computer System Life Cycle Security.
HIPAA COMPLIANCE WITH DELL
“ Technology Working For People” Intro to HIPAA and Small Practice Implementation.
Applied Technology Services, Inc. Your Partner in Technology Applied Technology Services, Inc. Your Partner in Technology.
Security Baseline. Definition A preliminary assessment of a newly implemented system Serves as a starting point to measure changes in configurations and.
NIST Special Publication Revision 1
Thomas Levy. Agenda 1.Aims: Reducing Cyber Risk 2.Information Risk Management 3.Secure Configuration 4.Network Security 5.Managing User Access 6.Education.
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.
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.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
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.
LeToia Crozier, Esq., CHC Vice President, Compliance & Regulatory Affairs Corey Wilson Director of Technical Services & Security Officer Interactive Think.
Disaster Recover Planning & Federal Information Systems Management Act Requirements December 2007 Central Maryland ISACA Chapter.
1 © Material United States Department of the Interior Federal Information Security Management Act (FISMA) April 2008 Larry Ruffin & Joe Seger.
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.
The Culture of Healthcare Privacy, Confidentiality, and Security Lecture d This material (Comp2_Unit9d) was developed by Oregon Health and Science University,
Federal Information Security Management Act (FISMA) By K. Brenner OCIO Internship Summer 2013.
Working with HIT Systems
Chapter 2 Securing Network Server and User Workstations.
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?
Frontline Enterprise Security
ISO/IEC 27001:2013 Annex A.8 Asset management
Privacy Act United States Army (Managerial Training)
1 Information Security Compliance System Owner Training Module 3 Supplement: Analysis of Policy Compliance Checklist Issues Richard Gadsden Information.
1 Information Governance (For Dental Practices) Norman Pottinger Information Governance Manager NHS Suffolk.
By: Matt Winkeler.  PCI – Payment Card Industry  DSS – Data Security Standard  PAN – Primary Account Number.
HHS Security and Improvement Recommendations Insert Name CSIA 412 Final Project Final Project.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
Contingency Management Indiana University of Pennsylvania John P. Draganosky.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
 December 2010 US Chief Information Officer Vivek Kundra released the Federal Cloud Computing Strategy. This became to be what is known as “Cloud First”
Cybersecurity - What’s Next? June 2017
Understanding HIPAA Dr. Jennifer Lu.
Introduction to the Federal Defense Acquisition Regulation
Matthew Christian Dave Maddox Tim Toennies
Red Flags Rule An Introduction County College of Morris
NCHER Knowledge Symposium Federal Contractor/TPS Session
Final HIPAA Security Rule
County HIPAA Review All Rights Reserved 2002.
Information Security Awareness
HIPAA Privacy and Security Summit 2018 HIPAA Privacy Rule: Compliance Plans, Training, Internal Audits and Patient Rights Widener University Delaware.
HIPAA Security Standards Final Rule
Introduction to the PACS Security
Presentation transcript:

FISMA 101

AGENDA FISMA Project Overview The Basics: FISMA and NIST RMF The Details: Six specific processes Portable Computing Devices and Media Getting Help Next Steps: Timeline, Rules of Behavior, HIPAA

FISMA PROJECT OVERVIEW The UF contract with the State of Texas requires compliance with FISMA and NIST standards for work supporting this project In response to the contract requirements: UFIT sponsored and invested in a significant project to support this contract ($1.5M/70-80 UFIT employees) On-track to complete the initial build-out by June 30th, 2015 The new FISMA environment replaces the current SAS and SQL environments used for Texas contract deliverables and research

FISMA @ UF Enables $40M State of Texas Contract UF will be eligible for additional contracts and grants via the FISMA-compliant, multi- tenant environment Requires End-users/Researchers: Heightened security requirements Office of Research: Revised contract /negotiation process UFIT: Additional compliance requirements

THE BASICS FISMA AND NIST RMF

WHAT IS FISMA? Federal Information Security Management Act (FISMA) of 2002 Included by Congress as part of the E-Government Act of 2002 Establishes security guidelines for federal agencies or those providing services to federal agencies Sets forth: Specific requirements for security programs Specific documentation, policies and procedures Defined processes required to be in place in accordance with NIST 800-53 – a national security standard Brings standardization to security control selection and assessment by providing a/an: Consistent framework for protecting information Effective management of risks to information security Development of adequate controls to protect information and systems Mechanism for effective oversight of security programs Essentially, every federal agency “did security differently or not at all” and Congress decided to enforce minimum standards.

NIST RISK MANAGEMENT FRAMEWORK (RMF) Prepare the POA&M Submit Security Authorization Package (Security Plan, SAR, and POA&M) to AO AO conducts final risk determination AO makes authorization decision Ultimately, NIST wants an organization to intelligently address the entire lifecycle of an information system to ensure security is “baked into” all components. This process has created a framework, titled “Risk Management Framework” (RMF) NIST guidance includes: Standards for categorizing information Standards for minimum security requirements Guidance for selecting appropriate security controls Guidance for assessing security controls and systems Guidance for “assess and authorize” information systems Basically, detailed documents that explain the entire security lifecycle: the who, what, when, and why of implementing secure environments to federal standards

RMF ALIGNED WITH INFORMATION SYSTEM Risk Management Framework Authorization Package SECURITY PLAN including updated Risk Assessment SECURITY ASSESSMENT REPORT PLAN OF ACTION AND MILESTONES INFORMATION SYSTEM CATEGORIZE Information System ASSESS Security Controls AUTHORIZE IMPLEMENT MONITOR Security State SELECT

SIX SPECIFIC PROCESSES THE DETAILS SIX SPECIFIC PROCESSES

1. GETTING AN ACCOUNT Non-FISMA Accounts were provided on an ad hoc basis (phone, email, etc.): accounts maintained as necessary FISMA Accounts have to be formally authorized and approved by management: processes need to ensure account list is current and appropriate Why Additional controls implement appropriate accountability and assurance of minimum necessary access rights

2. REMOTE ACCESS & LOGGING IN Non-FISMA Access was available through a variety of means and mechanisms simply requiring a user name and password (RDP, telnet, SSH, web portals, etc.) FISMA Remote access into the environment has to be secured with both something you know (a password) and something you have (a token) Why Passwords are easily stolen (Target, Home Depot, Anthem, Premera, etc.), so best practices and compliance require additional verification

3. DATA TRANSFERS Non-FISMA Systems allow whatever means for data transfer most convenient or available to users FISMA Sensitive data are regulated and therefore must have controlled mechanisms to allow data in and out Why Complexity and lack of control provide opportunities for loss or misuse

4. CHANGE MANAGEMENT Non-FISMA Changes are made on an ad hoc basis, not formally tracked or reviewed for security impact (updates to applications, databases, etc.) FISMA Changes must be formally reviewed, approved and tracked Why Oversight is necessary to ensure changes do not impact the integrity of the system’s security and tracking is necessary for audit purposes

5. LOGGING AND MONITORING Non-FISMA Logs and review of logs are performed on an ad hoc basis FISMA All systems enforce required logging measures to ensure they remain secure Why Logs are necessary to both detect adverse events (breaches, misuse of data, etc.) and for audit purposes

6. SECURITY ASSESSMENTS Non-FISMA No formal security assessments are performed FISMA Regular security assessments for vulnerabilities and compliance are conducted Why To ensure ongoing security of the environment

PORTABLE COMPUTING DEVICES AND MEDIA DATA PROTECTION AND PRIVACY

PORTABLE COMPUTING DEVICES Must comply with current UF policy which requires full disk encryption to protect the confidentiality and integrity of systems and data The FISMA environment is designed such that data is contained fully within the protected environment Users traveling to areas deemed as high risk are advised not to access the FISMA environment from those locations Portable devices taken to high risk areas will be completely erased and restored to the baseline configuration upon return and before being allowed to access the FISMA environment again

MEDIA ACCESS No ability is provided for users to use or access data on removable media as part of the ResShield system Privileged users are authorized to use removable media for the purpose of system installation and maintenance activities, as approved by the Change Advisory Board (CAB) No restricted data is stored on removable media, and media is scanned for malware before use with the ResShield system

MEDIA LABELING External labels are affixed to all removable media used with the ResShield system. Labels identify the data or software included and the note “Not for use with Restricted Data” If Restricted Data is stored on removable media, it is labeled as “UF ResShield” and “UF Restricted Data”

MEDIA STORAGE Privileged users store removable media used for system installation and maintenance in locked and controlled office facilities when not in use to prevent tampering See ResShield Standard Operating Procedures MP-4

MEDIA TRANSPORT Privileged users keep all removable media in their possession during transport to locked and controlled office facilities and the data center Transport of removable media that does not contain Restricted Data does not need to be documented and logged If Restricted Data is stored on removable media, the FISMA Operations Manager will individually authorize and document transport of such media outside of locked and controlled office facilities See ResShield Standard Operating Procedures MP-5

MEDIA ENCRYPTION UF Policy allows the use of unencrypted removable media only when encryption interferes with the media’s essential function As removable media is only used with ResShield for system installation and maintenance (which is usually not possible with encrypted media) encryption is not required for removable media If Restricted Data is stored on removable media, the media will be fully encrypted with FIPS 140-2 compliant products See ResShield Standard Operating Procedures

OUTPUT DEVICE PHYSICAL SECURITY UFIT staff with privileged access work in physically secured areas without public access Screen guards must be used with any monitors removed from the secure office area See ResShield Standard Operating Procedures PE-5

INSIDER THREATS

INSIDER THREATS What is an Insider Threat? An insider threat is a malicious threat to an organization that comes from people within the organization, such as employees, former employees, contractors or business associates, who have inside information concerning the organization’s security practices, data and computer systems What are some signs of this type of behavior and/or activities that you may encounter? Job dissatisfaction that may be in the form of verbal complaints against the university Harassment of fellow co-workers (which should be reported immediately) Violations of other university policies What should you do if you suspect Insider Threat Activity? Report it!! Call the Privacy Hotline – 866-876-HIPA Use the web form: http://privacy.ufl.edu/uf-health- privacy/report-an-incident

GETTING HELP

WHAT IF I NEED HELP? Nothing changes with your workstation support Contact UFHealth AHC-IT as you normally do UFHealth AHC-IT will route FISMA support requests to the FISMA team Additionally, for a few weeks after go-live, UFIT FISMA staff will rotate at 3 locations for user support services: CTRB 1329 Bldg. 2020 Bldg. (HOP Modular)

NEXT STEPS

NEXT STEPS Timeline: 6-8-15 to 6-30-15 3rd Party Assessment Organization (3PAO), Excentium is performing their Independent Verification and Validation (IV&V) 6-15-15 to 6-26-15 TX EQRO testing 6-30-15 TX Data is inside the FISMA bubble, TX FISMA is LIVE 7-1-15 to 8-15-15  45 day parallel validation period Rules of Behavior Verify HIPAA is up-to-date

APPENDIX

NIST REFERENCES FIPS Publication 199 (Security Categorization) FIPS Publication 200 (Minimum Security Requirements) NIST Special Publication 800-18 (Security Planning) NIST Special Publication 800-30 (Risk Assessment) NIST Special Publication 800-39 (Risk Management) NIST Special Publication 800-37 (Certification & Accreditation) NIST Special Publication 800-53 (Recommended Security Controls) NIST Special Publication 800-53A (Security Control Assessment) NIST Special Publication 800-60 (Information Types Mapping)

INFORMATION SECURITY PROGRAMS 1 of 2 The information security programs are centered around the security control families: Access Control Awareness and Training Audit and Accountability Certification, Accreditation, & Security Assessments Configuration Management Contingency Planning Identification & Authentication Incident Response

INFORMATION SECURITY PROGRAMS 2 of 2 The information security programs are centered around the security control families: System Maintenance Media Protection Security Planning Risk Assessment System & Services Acquisition System & Communication System & Information Integrity