CIT 485: Advanced Cybersecurity

Slides:



Advertisements
Similar presentations
IT Security Policy Framework
Advertisements

Surviving the PCI Self -Assessment James Placer, CISSP West Michigan Cisco Users Group Leadership Board.
Notes: Update as of 1/13/2010. Vulnerabilities are included for SQL Server 2000, SQL Server 2005, SQL Server Oracle (8i, 9i, 9iR2, 10g, 10gR2,11g),
Health Insurance Portability and Accountability Act HIPAA Education for Volunteers and Students.
Confidentiality and HIPAA
Increasing public concern about loss of privacy Broad availability of information stored and exchanged in electronic format Concerns about genetic information.
What is HIPAA? This presentation was created by The University of Arizona Privacy Office, The Office for the Responsible Conduct of Research on March 5,
1 HIPAA Education CCAC Professional Development Training September 2006 CCAC Professional Development Training September 2006.
Springfield Technical Community College Security Awareness Training.
IS3350 Security Issues in Legal Context
The Regulation Zoo: Dealing With Compliance Within The Firewall World
PCI Compliance Forrest Walsh Director, Information Technology California Chamber of Commerce.
Information Security Policies Larry Conrad September 29, 2009.
Security Controls – What Works
Insights on the Legal Landscape for Data Privacy in Higher Education Rodney Petersen, J.D. Government Relations Officer and Security Task Force Coordinator.
IT Legislation & Regulation CS5493. Information has become a valued asset for commerce and governments. … as a result of its value, information is a target.
CSE 4482, 2009 Session 21 Personal Information Protection and Electronic Documents Act Payment Card Industry standard Web Trust Sys Trust.
Chapter 9 Information Systems Controls for System Reliability— Part 2: Confidentiality and Privacy Copyright © 2012 Pearson Education, Inc. publishing.
Why Comply with PCI Security Standards?
Payment Card Industry (PCI) Data Security Standard
Payment Card Industry Data Security Standard (PCI DSS) By Roni Argetsinger
Protecting Sensitive Information PA Turnpike Commission.
An Introduction to PCI Compliance. Data Breach Trends About PCI-SSC 12 Requirements of PCI-DSS Establishing Your Validation Level PCI Basics Benefits.
Teresa Macklin Information Security Officer 27 May, 2009 Campus-wide Information Security Activities.
PCI requirements in business language What can happen with the cardholder data?
HIPAA PRIVACY AND SECURITY AWARENESS.
“ Technology Working For People” Intro to HIPAA and Small Practice Implementation.
1 General Awareness Training Security Awareness Module 1 Overview and Requirements.
Policy Review (Top-Down Methodology) Lesson 7. Policies From the Peltier Text, p. 81 “The cornerstones of effective information security programs are.
Medical Law and Ethics, Third Edition Bonnie F. Fremgen Copyright ©2009 by Pearson Education, Inc. Upper Saddle River, New Jersey All rights reserved.
© 2013 The McGraw-Hill Companies, Inc. All rights reserved. Ch 8 Privacy Law and HIPAA.
Information Security 2013 Roadshow - PCI. Roadshow Outline  What IS PCI  Why we Care about PCI  What PCI Means to You and Me.
IT Security Policy Framework ● Policies ● Standards ● Procedures ● Guidelines.
© Copyright 2010 Hemenway & Barnes LLP H&B
PCI Training for PointOS Resellers PointOS Updated September 28, 2010.
Copyright © 2015 by Saunders, an imprint of Elsevier Inc. All rights reserved. Chapter 3 Privacy, Confidentiality, and Security.
Data Security & Privacy: Fundamental Risk Mitigation Tactics 360° of IT Compliance Anthony Perkins, Shareholder Business Law Practice Group Data Security.
Information Security Measures Confidentiality IntegrityAccessibility Information cannot be available or disclosed to unauthorized persons, entities or.
Chapter 4: Laws, Regulations, and Compliance
Legal, Regulations, Investigations, and Compliance Chapter 9 Part 2 Pages 1006 to 1022.
The Health Insurance Portability and Accountability Act of 1996 “HIPAA” Public Law
By: Matt Winkeler.  PCI – Payment Card Industry  DSS – Data Security Standard  PAN – Primary Account Number.
The Medical College of Georgia HIPAA Privacy Rule Orientation.
The Payment Card Industry Data Security Standard (PCI DSS) is a proprietary information security standard for organizations that handle branded credit.
Payment Card Industry (PCI) Rules and Standards
Performing Risk Analysis and Testing: Outsource or In-house
PCI-DSS Security Awareness
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance
Regulatory Compliance
Data Security Policies
Internet Payment.
Session 11 Other Assurance Services
Data Compromises: A Tax Practitioners “Nightmare”
E&O Risk Management: Meeting the Challenge of Change
IS4680 Security Auditing for Compliance
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance
Health Advocate HIPAA Privacy Information
Payment Card Industry (PCI) Data Security Standard (DSS) Compliance
HIPAA PRIVACY AWARENESS, COMPLIANCE and ENFORCEMENT
Chapter 4 Law, Regulations, and Compliance
Disability Services Agencies Briefing On HIPAA
County HIPAA Review All Rights Reserved 2002.
CompTIA Security+ Study Guide (SY0-401)
Health Care: Privacy in a Digital Age
Contact Center Security Strategies
The Issues with Technology in education
Move this to online module slides 11-56
Introduction to the PACS Security
Presentation transcript:

CIT 485: Advanced Cybersecurity Policy, Legal, and Compliance Issues

Topics Policy, Standards, and Procedures US Government Security Policies (FISMA) Laws and Compliance PCI Data Security Standard (DSS) Bring Your Own Device (BYOD)

Policy, Standards, and Procedures Policy provides a statement of intent. Employees must use strong passwords on all accounts. Standard provides specifics to help organization members comply with policy. Passwords must be at least 10 characters long. They must not be stored on unencrypted media. Procedures To change your password, following the following steps: Login using your current password. Type passwd Enter your current password. Enter your new password twice.

Compliance Information security policies must secure compliance with applicable laws and regulations. Organizations must demonstrate due care, measures taken to ensure every employee knows what is acceptable and what is not. Organizations must also demonstrate due diligence, reasonable steps taken to meet the obligations imposed by laws and regulations.

Data Handling Policies Organizations must have data handling policies to ensure compliance with appropriate laws and regulations. Individual IT workers are responsible for following those policies to protect the data of customers and employees.

Enforcing Policies Enforceable policies must meet 5 criteria: Dissemination. Policy must be readily available. Review. Organization must demonstrate policy is accessible to all employees, regardless of language ability. Comprehension. Organization must demonstrate employees understand policies. Online tests and other assessments can be used to ensure comprehension. Compliance. Organization must demonstrate employees agreed to policy through signatures or another specific action. Uniform enforcement. Organization must enforce policy equally on all employees.

Computer Security Act (1987) Mandated baseline security standards for fed agencies. Assigned National Institute & Standards Technologies (NIST) responsibility for developing computer security standards and guidelines for federal government. NSA assigned responsibility for classified systems. Required security policies be created by agencies for computer systems with sensitive data. Mandated security awareness training for federal employees that use computers with sensitive data.

FISMA (2002) Federal Information Security Management Act Repealed Computer Security Act of 1987. Mandates federal agencies establish infosec programs. Risk assessments. Policies and procedures. Security awareness training. Incident response. Periodic security assessments.

FIPS Federal Information Processing Standards Notable FIPS Available on NIST web site. Some used only by federal government. Others used widely by private organizations. Notable FIPS 140-2: Standards for cryptography. Much cryptographic software comes with a FIPS version to meet 140-2. 800-53: Security controls for federal government systems.

Sarbanes-Oxley (SOX) (2002) Goal: reliability and accuracy of financial reporting Requires that corporate IT certify confidentiality and integrity of systems involved in financial reporting. Section 302 Requires corporate executives to personally certify the accuracy and completeness of their financial reports, Report on the effectiveness of internal controls for their financial reporting. Section 404 Mandates security assessment reports must be audited by an external firm.

Gramm-Leach-Bliley (1999) Financial Services Modernization Act Requires financial institutions to disclose privacy policies on the sharing of PII. Requires due notice to customers so that they can request information not to be shared. Requires notification of customers about privacy policies annually.

FERPA (1974) Family Educational Rights and Privacy Act Gives parents access to child educational records, but Requires permission of students age 18 or older. Restricts access to educational records Determines who can access PII, grades, and for which purposes. PII and grades can only be sent over secure channels. Student medical records governed by FERPA, not HIPAA.

HIPAA (1996) Health Insurance Portability and Accountability Act Affects almost all organizings doing health care. Privacy requirements for sharing health care records without patient consent. Requires providers give patients access to records. Establishes standards for digital health record exchange. Discussed in more detail in other classes like PHI 310.

COPPA (1998) Children's Online Privacy Protection Act Protects collection of data on children under age 13. Specifies requirements for website privacy policies. Defines consent requirements for websites. Restricts marketing to those under age 13. Enforced by the Federal Trade Commission (FTC).

PCI DSS Payment Card Industry (PCI) requires that organizations that accept payments must follow their Data Security Standard (DSS). Version 1.0 released in December 2004. Requires securing data at all systems and links: point-of-sale devices; mobile devices, personal computers or servers; wireless hotspots; web shopping applications; paper-based storage systems; the transmission of cardholder data to service providers; in remote access connections.

PCI DSS: 12 Requirements Installi and maintain a firewall configuration to protect cardholder data. Do not use vendor-supplied defaults for system passwords and other security parameters. Protect stored cardholder data. Encrypt transmission of cardholder data across open, public networks. Protect all systems against malware and regularly update anti-virus software or programs. Develop and maintain secure systems and applications.

PCI DSS: 12 Requirements Restrict access to cardholder data by business need-to-know. Identify and authenticate access to system components. Restrict physical access to cardholder data. Track and monitor all access to network resources and cardholder data. Regularly test security systems and processes. Maintain a policy that addresses information security for all personnel.

Bring Your Own Device (BYOD) BYOD Policy Employees bring own mobile device to work. Same device contains both work and personal data. Risks to Employers Work data travels with device, not protected by firewall. Device may bring malware from outside inside firewall. Work data may remain on device after employment is terminated. Risks to Employees Makes devices subject to legal discovery. Mobile device management software can wipe device.

References Seth Hammon. Intro to Cyber Law and Ethics Module. CLARK. 2018. Michael E. Whitman, Herbert J. Mattord. Principles of Information Security, 6th Edition. Cengage Learning. 2017. PCI Security Standards Council. PCI DSS Quick Reference Guide: Understanding the Payment Card Industry Data Security Standard version 3.2.1. 2018. Richard Spinello. Cyberethics: Morality and Law in Cyberspace, 6th Edition. Jones & Bartlett. 2016.

Released under CC BY-SA 3.0 This presentation is released under the Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license You are free: to Share — to copy and redistribute the material in any medium to Adapt— to remix, build, and transform upon the material to use part or all of this presentation in your own classes Under the following conditions: Attribution — You must attribute the work to James Walden, but cannot do so in a way that suggests that he endorses you or your use of these materials. Share Alike — If you remix, transform, or build upon this material, you must distribute the resulting work under this or a similar open license. Details and full text of the license can be found at https://creativecommons.org/licenses/by-nc-sa/3.0/

Discuss: Aaron Schwartz Computer Fraud and Abuse Act (CFAA) written in 1986 to amend existing computer fraud law. Makes knowingly accessing a “protected computer” without authorization or exceeding authorized access a crime. Any computer with Internet access is likely a “protected computer”. Controversy: Aaron Schwartz case Aaron Schwartz created a script to automatically download many articles from JSTOR, violating their Terms of Service. Federal prosecutors charged him with 11 violations of CFAA with maximum penalty of 35 years, $1 million fine. CIT 485: Advanced Cybersecurity