Ohio Supercomputer Center
|
|
|
- Piers Richard
- 10 years ago
- Views:
Transcription
1 Ohio Supercomputer Center Portable Security Computing No: Effective: OSC-09 05/27/09 Issued By: Kevin Wohlever Director of Supercomputer Operations Published By: Ohio Supercomputer Center Original Publication Date: TBD 1. Purpose This policy addresses information technology (IT) security concerns with portable computing devices and provides direction for their use, management and control. This policy includes security concerns with the physical device itself, as well as its applications and data. 2. Scope Pursuant to Ohio IT Policy ITP-A.1, Authority of the State Chief Information Officer to Establish Policy Regarding the Acquisition and Use of Computer and Telecommunications Products and Services, this policy applies to all systems under the control of the Ohio Supercomputer Center. The scope of this information technology policy includes OSC computer and telecommunications systems and the employees, contractors, temporary personnel and other agents of the state who use and administer such systems. 3. Background A deliberate decision needs to be made on whether or not portable computing devices should be allowed and, if so, to what degree the devices would be supported. It is essential to address the use and maintenance of state-owned and privately-owned portable devices, protection of sensitive data, adherence to legal requirements, and the safeguarding of system assets. Portable computing devices are increasingly becoming an integral tool for government agencies and businesses. Through the use of portable computing devices, users are able to access university computer and telecommunications systems so that they can work remotely outside of traditional business hours and while traveling. One consequence of this ability has been the co-mingling of business and personal computing assets, particularly portable computing devices such as notebook computers and personal digital assistants. Government agencies need to ensure that the appropriate
2 safeguards are in place to protect against the intentional or inadvertent corruption or destruction of system assets. 4. References This Policy is based on the following State of Ohio Policies: 4.1. Ohio IT Policy ITP-A.1, Authority of the State Chief Information Officer to Establish Policy Regarding the Acquisition and Use of Computer and Telecommunications Products and Services, defines the authority of the state chief information officer to establish State of Ohio IT policies as they relate to state agencies acquisition and use of information technology, including, but not limited to, hardware, software, technology services and security Ohio IT Policy ITP-B.1, Information Security Framework, is the overarching security policy for state information and services. Ohio IT Policy ITP-B.9, Portable Computing Security, is one of several subpolicies. These security policies should be considered collectively rather than as separate or unrelated policies. Attachment 1 illustrates the interrelationship of state technology security policies Ohio IT Policy ITP-B.2, Boundary Security, requires that state agencies implement and operate a robust network perimeter defense capability. Users of state electronic services must be provided with secure and reliable access to resources and communications. Unauthorized users must be detected and denied access Ohio IT Policy ITP-B.3, Password and Personal Identification Number Security, establishes minimum requirements regarding the proper selection, use and management of passwords and personal identification numbers Ohio IT Policy ITP-B.4, Malicious Code, requires state agencies to implement and operate a malicious code security program. The program should help to ensure that adequate protective measures are in place against introduction of malicious code into state-controlled information systems and that computer system users are able to maintain a high degree of malicious code awareness Ohio IT Policy ITP-B.5, Remote Access, requires state agencies to implement and operate security measures wherever a remote access capability is provided to state systems so that inherent vulnerabilities in such services may be compensated Ohio IT Policy ITP-B.6, Internet Security, requires agencies to implement and operate security protections for Internet, extranet and intranet use, and provide Internet security awareness training to employees, contractors, temporary personnel and other agents of the state Ohio IT Policy ITP-B.8, Security Education and Awareness, requires state agencies to provide information technology security education and awareness to employees and other agents of the state. OSC-9 Page 2 of 9
3 4.9. Ohio IT Policy ITP-E.1, Disposal, Servicing and Transfer of IT Equipment, establishes agency requirements for the disposal, servicing or transfer of state agency IT equipment with regard to state data, licensed software and intellectual property, and rechargeable batteries and other hazardous materials Ohio IT Bulletin ITB , Data Encryption and Securing Sensitive Data, effective July 25, 2007, outlines the requirements for the encryption of sensitive data as well as requirements for securing portable devices and media, backups, sensitive data in transmission, and sensitive data at rest. The bulletin also outlines restrictions for sensitive data, physical security considerations, public servant acknowledgement requirements, and incident response. 5. Policy This policy is not intended to address the use of portable devices by the general population to access electronic OSC services. In addition to state-owned portable computing devices, the policy shall address privatelyowned and contractor-owned portable computing devices authorized for university use by the agency or as an agent of the university. OSC policy shall address the following: 5.1. Physical Security. OSC and users shall protect university-owned and universityauthorized portable computing devices, removable storage components and removable computer media from unauthorized access. Physical security measures shall incorporate at a minimum the practices listed below in through Portable computing devices, computer media and removable components, such as disk drives and network cards, shall be stored in a secure environment. Devices shall not be left unattended without employing adequate safeguards, such as cable locks, restricted access environments or lockable cabinets When possible, portable computing devices, computer media and removable components shall remain under visual control while traveling. If visual control cannot be maintained, then necessary safeguards shall be employed to protect the physical device, computer media and removable components Safeguards shall be taken in public or common areas to avoid unauthorized viewing of sensitive or confidential data OSC will maintain an inventory for all university, privately-owned and contractorowned portable devices authorized for work use with university systems. The inventory shall include the device make, model, serial number, date introduced into service and party responsible for the device Operation and Maintenance. OSC shall establishes and implements IT security procedures for the secure operation and maintenance of portable computing devices. OSC-9 Page 3 of 9
4 Anti-virus software. Portable computing devices shall be equipped with anti-virus software in accordance with OSC Policy OSC-4, Malicious Code Security System configuration. Mandatory system configurations, settings and software for either university-owned or authorized non-university owned devices shall not be modified without prior authorization by designated OSC personnel. Device operating systems shall be maintained with appropriate vendor security patches and updates Portable computing devices shall not be equipped with remote system or application administrator privileges unless authorized. Portable computing devices equipped with remote system administrator capabilities shall be assigned higher levels of security in accordance with the increased risk of an IT security breach or loss of the device, pursuant to OSC Policy OSC-3, Information Security Framework OSC or university data, applications and other system resources stored on portable computing devices shall be secured in accordance with the OSC risk assessment as defined in OSC Policy OSC-3, Information Security Framework. Methods for securing information maintained on portable devices may include as applicable, but not be limited to: Personal firewalls BIOS passwords Data/application encryption Hard drive encryption Screen locking Screen timeout Security tokens The transmission of university data via infrared, bluetooth, x or other wireless technologies shall be in compliance with OSC Policy OSC-5, Remote Access Security Regular system and data back-ups will be preformed as frequently as needed based on the risk assessment of the information maintained on the portable device, in accordance with OSC Policy OSC-3, Information Security Framework. Backups shall be safeguarded and retained for a period commensurate with the value and criticality of the information University-owned Devices. OSC will provide designated personnel a computer to assist in the completion of their duties. At the end of their employment or association with OSC, or no longer need the equipment to carry out their duty, all equipment will be returned to the supervisor or designate Personal software and data is allowed on the computer system, as long as the software or data is legally owned or controlled by the user. OSC-9 Page 4 of 9
5 When a device is removed from service, OSC shall sanitize the IT equipment to remove information Privately-owned Devices. All OSC owned or licensed data or software on a personal owned or contractor-owned portable computing devices shall be removed, or recovered when no longer used or when the user s employment or contract terminates or when the portable computing device is no longer authorized for official OSC business Data Synchronization (Syncing). OSC has no legal liability for the loss of non- OSC data or the confidentially of data synchronized (synced) to university-owned or operated devices Identification and Authentication (I&A) Control. Portable computing devices shall accommodate I&A controls in accordance with OSC Policy OSC-8, Password and PIN. If available, I&A controls shall be used to prevent unauthorized modifications of system settings Internet Connectivity. Portable computing devices connected to the Internet shall be in compliance with Ohio IT Policy ITP-B.6, Internet Security, and OSC Policy, OSC-5, Remote Access Security. At a minimum, users shall not establish a separate Internet connection while simultaneously connected to an agency network through the use of multiple network cards, modems or other access techniques Inventory and Audit. OSC shall conduct inventory and security audits of portable computing devices on a regular and random basis Lost and Stolen Devices. In the event of a lost or stolen device, the person responsible for the equipment, including contractor and personal owned equipment with state software or data, shall notify their immediate supervisor or contract manager, and the OSC IT security contact within 1 business day. Information required in the report includes: Date of loss, OSC data on the device and its sensitivity level, security on the device (encrpption levels) and other details relevant to the loss Privately-Owned and Contractor-Owned Portable Computing Devices. Privately-owned or contractor-owned devices are authorized for official university use. A privately-owned or contractor-owned portable computing device is used, the device shall meet the following additional requirements: The device owner or contractor is responsible for obtaining, installing and maintaining malicious code security software in compliance with OSC Policy, OSC - 4, Malicious Code Security The device owner or contractor is responsible for obtaining, installing and maintaining personal firewalls in compliance with Ohio IT Policy ITP-B.2, Boundary Security. OSC-9 Page 5 of 9
6 OSC accepts no liability for the safeguarding or maintenance of nonuniversity or non-osc data on portable computing devices used in support of official OSC business or while acting as an agent of OSC. The users of privatelyowned devices used for OSC work shall not have any expectation of personal privacy regarding the device and that such devices may be confiscated as evidence in civil or criminal proceedings No network access certification is needed. 6. References 6.1. Ohio IT Policy ITP-A.1, Authority of the State Chief Information Officer to Establish Policy Regarding the Acquisition and Use of Computer and Telecommunications Products and Services, defines the authority of the state chief information officer to establish State of Ohio IT policies as they relate to state agencies acquisition and use of information technology, including, but not limited to, hardware, software, technology services and security Ohio IT Policy ITP-B.1, Information Security Framework, is the overarching security policy for state information and services. Ohio IT Policy ITP-B.9, Portable Computing Security, is one of several subpolicies. These security policies should be considered collectively rather than as separate or unrelated policies. Attachment 1 illustrates the interrelationship of state technology security policies Ohio IT Policy ITP-B.2, Boundary Security, requires that state agencies implement and operate a robust network perimeter defense capability. Users of state electronic services must be provided with secure and reliable access to resources and communications. Unauthorized users must be detected and denied access Ohio IT Policy ITP-B.3, Password and Personal Identification Number Security, establishes minimum requirements regarding the proper selection, use and management of passwords and personal identification numbers Ohio IT Policy ITP-B.4, Malicious Code, requires state agencies to implement and operate a malicious code security program. The program should help to ensure that adequate protective measures are in place against introduction of malicious code into state-controlled information systems and that computer system users are able to maintain a high degree of malicious code awareness Ohio IT Policy ITP-B.5, Remote Access, requires state agencies to implement and operate security measures wherever a remote access capability is provided to state systems so that inherent vulnerabilities in such services may be compensated Ohio IT Policy ITP-B.6, Internet Security, requires agencies to implement and operate security protections for Internet, extranet and intranet use, and provide Internet security awareness training to employees, contractors, temporary personnel and other agents of the state. OSC-9 Page 6 of 9
7 6.8. Ohio IT Policy ITP-B.8, Security Education and Awareness, requires state agencies to provide information technology security education and awareness to employees and other agents of the state Ohio IT Policy ITP-E.1, Disposal, Servicing and Transfer of IT Equipment, establishes agency requirements for the disposal, servicing or transfer of state agency IT equipment with regard to state data, licensed software and intellectual property, and rechargeable batteries and other hazardous materials Ohio IT Bulletin ITB , Data Encryption and Securing Sensitive Data, effective July 25, 2007, outlines the requirements for the encryption of sensitive data as well as requirements for securing portable devices and media, backups, sensitive data in transmission, and sensitive data at rest. The bulletin also outlines restrictions for sensitive data, physical security considerations, public servant acknowledgement requirements, and incident response. 7. Procedures None. 8. Implementation This policy is effective immediately. 9. Revision History 10. Definitions Date Description of Change 6/1/2009 Original policy. Administrator Privileges. Ability to modify computer system settings, including access permissions associated with computer resources and data. Computer Media. Computer readable or writeable permanent or temporary storage, such as CDs, DVDs, flash memory cards and diskettes. Data. Coded representation of quantities, objects and actions. The word, data, is often used interchangeably with the word, information, in common usage and in this policy. Data Synchronization (Syncing). The practice of updating data on two systems so that the data sets are identical. Disk Drives. Magnetic and optical devices used by a computer to store and obtain data. Examples include hard drives, floppy disks, diskettes, CDs and DVDs. OSC-9 Page 7 of 9
8 Firewall. Either software or a combination of hardware and software, that implements security policy governing traffic between two or more networks or network segments. Firewalls are used to protect internal networks, servers and workstations from unauthorized users or processes. Firewalls have various configurations, from standalone servers to software on a notebook computer, and must be configured properly to enable protection. Identification and Authentication (I&A). The verification of the identity of a requesting entity (a person, computer, system or process). Once it is determined who may have access to a system, the identification and authentication (I&A) process helps to enforce access control to the system by verifying the identity of the requesting entity. Systems may use a variety of techniques or combinations of techniques, such as user ID, password, personal identification number, digital certificates, security tokens or biometrics, to enforce I&A, depending upon the level of access control required to protect a particular system. Internet. A worldwide system of computer networks a network of networks in which computer users can get information and access services from other computers. The Internet is generally considered to be public, untrusted and outside the boundary of the state of Ohio enterprise network. Portable Computing Device. Computer or device designed for mobile use. Examples include laptops, personal digital assistants and mobile data collection devices. Screen Locking. Mechanism to hide data on a visual display while the computer continues to operate. A screen lock requires authentication to access the data. Screen locks can be activated manually or in response to rules. Screen Timeout. Mechanism to turn off a device or end a session when the device has not been used for a specified time period. Security Tokens. A portable, physical device that enables pre-approved access to data or systems. An example is a security-enabled key fob. Service Level Agreement. De f i n e s t h e s e r v i c e s t o b e d e l i v e r e d, t e c h n i c a l s u p p o r t a n d o t h e r p a r a m e t e r s t h a t, b y c o n t r a c t, a b u s i n e s s o r s u p p o r t i n g a c t i v i t y i s r e q u i r e d t o d e l i v e r. T h e s e r v i c e l e v e l a g r e e m e n t s h o u l d d e s c r i b e p e r f o r m a n c e m e a s u r e s a s w e l l a s p e n a l t i e s f o r f a i l u r e t o p e r f o r m i n OSC-9 Page 8 of 9
9 a c c o r d a n c e w i t h t h e s e r v i c e l e v e l a g r e e m e n t. System Assets. Information, hardware, software and services required to support the business of the agency, and identified during the risk assessment process as assets that need to be protected in accordance with Ohio IT Policy ITP-B.1, Information Security Framework. Terms and Conditions. Language included in a contract that describes limits and expectations related to performance under the contract. Users. For the purposes of this policy, users are defined as employees, contractors, temporary personnel and other agents of the state who administer or use privatelyowned (if authorized) or state-owned computer and telecommunication systems on behalf of the state. Wireless. Use of various electromagnetic spectrum frequencies, such as radio and infrared, to communicate services, such as data and voice, without relying on a hardwired connection, such as twisted pair, coaxial or fiber optic cable. 11. Related Resources 12. Inquiries Direct inquiries about this policy to: Director of Supercomputer Operations 1224 Kinnear Rd. Columbus, OH Telephone: OSC IT Policies can be found on the Internet at: OSC-9 Page 9 of 9
Ohio Supercomputer Center
Ohio Supercomputer Center Security Education and Awareness No: Effective: OSC-6 06/02/2009 Issued By: Kevin Wohlever Director of Supercomputer Operations Published By: Ohio Supercomputer Center Original
Ohio Supercomputer Center
Ohio Supercomputer Center IT Business Continuity Planning No: Effective: OSC-13 06/02/2009 Issued By: Kevin Wohlever Director of Supercomputer Operations Published By: Ohio Supercomputer Center Original
HIPAA Security Alert
Shipman & Goodwin LLP HIPAA Security Alert July 2008 EXECUTIVE GUIDANCE HIPAA SECURITY COMPLIANCE How would your organization s senior management respond to CMS or OIG inquiries about health information
This policy applies to all DRC employees, contractors, volunteers, interns and other agents of the state.
STATE OF OHIO SUBJECT: PAGE 1 OF 9 DRC Sensitive Data Security Requirements NUMBER: 05-OIT-23 DEPARTMENT OF REHABILITATION AND CORRECTION RULE/CODE REFERENCE: RELATED ACA STANDARDS: SUPERSEDES: 05-OIT-23
IT Best Practices Audit TCS offers a wide range of IT Best Practices Audit content covering 15 subjects and over 2200 topics, including:
IT Best Practices Audit TCS offers a wide range of IT Best Practices Audit content covering 15 subjects and over 2200 topics, including: 1. IT Cost Containment 84 topics 2. Cloud Computing Readiness 225
State of Ohio IT Policy
Ohio Office of Information Technology Ted Strickland, Governor R. Steve Edmonson, Director / State Chief Information Officer Statewide IT Policy Investment and Governance Division 30 East Broad Street,
MONTSERRAT COLLEGE OF ART WRITTEN INFORMATION SECURITY POLICY (WISP)
MONTSERRAT COLLEGE OF ART WRITTEN INFORMATION SECURITY POLICY (WISP) 201 CMR 17.00 Standards for the Protection of Personal Information Of Residents of the Commonwealth of Massachusetts Revised April 28,
SUBJECT: Effective Date Policy Number Security of Mobile Computing, Data Storage, and Communication Devices
SUBJECT: Effective Date Policy Number Security of Mobile Computing, Data Storage, and Communication Devices 8-27-2015 4-007.1 Supersedes 4-007 Page Of 1 5 Responsible Authority Vice Provost for Information
SUBJECT: SECURITY OF ELECTRONIC MEDICAL RECORDS COMPLIANCE WITH THE HEALTH INSURANCE PORTABILITY AND ACCOUNTABILITY ACT OF 1996 (HIPAA)
UNIVERSITY OF PITTSBURGH POLICY SUBJECT: SECURITY OF ELECTRONIC MEDICAL RECORDS COMPLIANCE WITH THE HEALTH INSURANCE PORTABILITY AND ACCOUNTABILITY ACT OF 1996 (HIPAA) DATE: March 18, 2005 I. SCOPE This
INITIAL APPROVAL DATE INITIAL EFFECTIVE DATE
TITLE AND INFORMATION TECHNOLOGY RESOURCES DOCUMENT # 1107 APPROVAL LEVEL Alberta Health Services Executive Committee SPONSOR Legal & Privacy / Information Technology CATEGORY Information and Technology
UF IT Risk Assessment Standard
UF IT Risk Assessment Standard Authority This standard was enacted by the UF Senior Vice President for Administration and the UF Interim Chief Information Officer on July 10, 2008 [7]. It was approved
Information Security Program Management Standard
State of California California Information Security Office Information Security Program Management Standard SIMM 5305-A September 2013 REVISION HISTORY REVISION DATE OF RELEASE OWNER SUMMARY OF CHANGES
Responsible Access and Use of Information Technology Resources and Services Policy
Responsible Access and Use of Information Technology Resources and Services Policy Functional Area: Information Technology Services (IT Services) Applies To: All users and service providers of Armstrong
FINAL May 2005. Guideline on Security Systems for Safeguarding Customer Information
FINAL May 2005 Guideline on Security Systems for Safeguarding Customer Information Table of Contents 1 Introduction 1 1.1 Purpose of Guideline 1 2 Definitions 2 3 Internal Controls and Procedures 2 3.1
TASK -040. TDSP Web Portal Project Cyber Security Standards Best Practices
Page 1 of 10 TSK- 040 Determine what PCI, NERC CIP cyber security standards are, which are applicable, and what requirements are around them. Find out what TRE thinks about the NERC CIP cyber security
micros MICROS Systems, Inc. Enterprise Information Security Policy (MEIP) August, 2013 Revision 8.0 MICROS Systems, Inc. Version 8.
micros MICROS Systems, Inc. Enterprise Information Security Policy (MEIP) Revision 8.0 August, 2013 1 Table of Contents Overview /Standards: I. Information Security Policy/Standards Preface...5 I.1 Purpose....5
LAMAR STATE COLLEGE - ORANGE INFORMATION RESOURCES SECURITY MANUAL. for INFORMATION RESOURCES
LAMAR STATE COLLEGE - ORANGE INFORMATION RESOURCES SECURITY MANUAL for INFORMATION RESOURCES Updated: June 2007 Information Resources Security Manual 1. Purpose of Security Manual 2. Audience 3. Acceptable
Newcastle University Information Security Procedures Version 3
Newcastle University Information Security Procedures Version 3 A Information Security Procedures 2 B Business Continuity 3 C Compliance 4 D Outsourcing and Third Party Access 5 E Personnel 6 F Operations
ADM:49 DPS POLICY MANUAL Page 1 of 5
DEPARTMENT OF PUBLIC SAFETY POLICIES & PROCEDURES SUBJECT: IT OPERATIONS MANAGEMENT POLICY NUMBER EFFECTIVE DATE: 09/09/2008 ADM: 49 REVISION NO: ORIGINAL ORIGINAL ISSUED ON: 09/09/2008 1.0 PURPOSE The
Information Security and Electronic Communications Acceptable Use Policy (AUP)
Policy No.: AUP v2.0 Effective Date: August 16, 2004 Revision Date: January 17, 2013 Revision No.: 1 Approval jwv / mkb Information Security and Electronic Communications (AUP) 1. INTRODUCTION Southwestern
INFORMATION TECHNOLOGY SECURITY STANDARDS
INFORMATION TECHNOLOGY SECURITY STANDARDS Version 2.0 December 2013 Table of Contents 1 OVERVIEW 3 2 SCOPE 4 3 STRUCTURE 5 4 ASSET MANAGEMENT 6 5 HUMAN RESOURCES SECURITY 7 6 PHYSICAL AND ENVIRONMENTAL
Supplier Information Security Addendum for GE Restricted Data
Supplier Information Security Addendum for GE Restricted Data This Supplier Information Security Addendum lists the security controls that GE Suppliers are required to adopt when accessing, processing,
Miami University. Payment Card Data Security Policy
Miami University Payment Card Data Security Policy IT Policy IT Standard IT Guideline IT Procedure IT Informative Issued by: IT Services SCOPE: This policy covers all units within Miami University that
Information Resources Security Guidelines
Information Resources Security Guidelines 1. General These guidelines, under the authority of South Texas College Policy #4712- Information Resources Security, set forth the framework for a comprehensive
Information Technology Branch Access Control Technical Standard
Information Technology Branch Access Control Technical Standard Information Management, Administrative Directive A1461 Cyber Security Technical Standard # 5 November 20, 2014 Approved: Date: November 20,
SERVER, DESKTOP AND PORTABLE SECURITY. September 2014. Version 3.0
SERVER, DESKTOP AND PORTABLE SECURITY September 2014 Version 3.0 Western Health and Social Care Trust Page 1 of 6 Server, Desktop and Portable Policy Title SERVER, DESKTOP AND PORTABLE SECURITY POLICY
TEMPLE UNIVERSITY POLICIES AND PROCEDURES MANUAL
TEMPLE UNIVERSITY POLICIES AND PROCEDURES MANUAL Title: Computer and Network Security Policy Policy Number: 04.72.12 Effective Date: November 4, 2003 Issuing Authority: Office of the Vice President for
Central Agency for Information Technology
Central Agency for Information Technology Kuwait National IT Governance Framework Information Security Agenda 1 Manage security policy 2 Information security management system procedure Agenda 3 Manage
HIPAA Compliance (DSHS and HCA) Preamble: This section of the Contract is the Business Associate Agreement as
HIPAA Compliance (DSHS and HCA) Preamble: This section of the Contract is the Business Associate Agreement as required by HIPAA. 1. Definitions. a. Business Associate, as used in this Contract, means the
Estate Agents Authority
INFORMATION SECURITY AND PRIVACY PROTECTION POLICY AND GUIDELINES FOR ESTATE AGENTS Estate Agents Authority The contents of this document remain the property of, and may not be reproduced in whole or in
Supplier Security Assessment Questionnaire
HALKYN CONSULTING LTD Supplier Security Assessment Questionnaire Security Self-Assessment and Reporting This questionnaire is provided to assist organisations in conducting supplier security assessments.
COVER SHEET OF POLICY DOCUMENT Code Number Policy Document Name
COVER SHEET OF POLICY DOCUMENT Code Number Policy Document Name Introduction Removable Media and Mobile Device Policy Removable media and mobile devices are increasingly used to enable information access
Information Technology Security Procedures
Information Technology Security Procedures Prepared By: Paul Athaide Date Prepared: Dec 1, 2010 Revised By: Paul Athaide Date Revised: September 20, 2012 Version 1.2 Contents 1. Policy Procedures... 3
PCI Data Security and Classification Standards Summary
PCI Data Security and Classification Standards Summary Data security should be a key component of all system policies and practices related to payment acceptance and transaction processing. As customers
State of South Carolina Policy Guidance and Training
State of South Carolina Policy Guidance and Training Policy Workshop All Agency Mobile Security July 2014 Agenda Questions & Follow-Up Policy Workshop Overview & Timeline Policy Overview: Mobile Security
System Security Plan University of Texas Health Science Center School of Public Health
System Security Plan University of Texas Health Science Center School of Public Health Note: This is simply a template for a NIH System Security Plan. You will need to complete, or add content, to many
ISO 27001 Controls and Objectives
ISO 27001 s and Objectives A.5 Security policy A.5.1 Information security policy Objective: To provide management direction and support for information security in accordance with business requirements
HIPAA Security. assistance with implementation of the. security standards. This series aims to
HIPAA Security SERIES Security Topics 1. Security 101 for Covered Entities 2. Security Standards - Administrative Safeguards 3. Security Standards - Physical Safeguards 4. Security Standards - Technical
Client Security Risk Assessment Questionnaire
Select the appropriate answer from the drop down in the column, and provide a brief description in the section. 1 Do you have a member of your organization with dedicated information security duties? 2
Draft Information Technology Policy
Draft Information Technology Policy Version 3.0 Draft Date June 2014 Status Draft Approved By: Table of Contents 1.0 Introduction... 6 Background... 6 Purpose... 6 Scope... 6 Legal Framework... 6 2.0 Software
BEFORE THE BOARD OF COUNTY COMMISSIONERS FOR MULTNOMAH COUNTY, OREGON RESOLUTION NO. 05-050
BEFORE THE BOARD OF COUNTY COMMISSIONERS FOR MULTNOMAH COUNTY, OREGON RESOLUTION NO. 05-050 Adopting Multnomah County HIPAA Security Policies and Directing the Appointment of Information System Security
Course: Information Security Management in e-governance
Course: Information Security Management in e-governance Day 2 Session 2: Security in end user environment Agenda Introduction to IT Infrastructure elements in end user environment Information security
Information Security Plan effective March 1, 2010
Information Security Plan effective March 1, 2010 Section Coverage pages I. Objective 1 II. Purpose 1 III. Action Plans 1 IV. Action Steps 1-5 Internal threats 3 External threats 3-4 Addenda A. Document
Cyber Self Assessment
Cyber Self Assessment According to Protecting Personal Information A Guide for Business 1 a sound data security plan is built on five key principles: 1. Take stock. Know what personal information you have
Montclair State University. HIPAA Security Policy
Montclair State University HIPAA Security Policy Effective: June 25, 2015 HIPAA Security Policy and Procedures Montclair State University is a hybrid entity and has designated Healthcare Components that
Rule 4-004G Payment Card Industry (PCI) Remote and Mobile Access Security (proposed)
Version: Modified By: Date: Approved By: Date: 1.0 Michael Hawkins October 29, 2013 Dan Bowden November 2013 Rule 4-004G Payment Card Industry (PCI) Remote and Mobile Access Security (proposed) 01.1 Purpose
PII Compliance Guidelines
Personally Identifiable Information (PII): Individually identifiable information from or about an individual customer including, but not limited to: (a) a first and last name or first initial and last
COLUMBUS STATE COMMUNITY COLLEGE POLICY AND PROCEDURES MANUAL
PAYMENT CARD INDUSTRY COMPLIANCE (PCI) Effective June 1, 2011 Page 1 of 6 (1) Definitions a. Payment Card Industry Data Security Standards (PCI-DSS): A set of standards established by the Payment Card
Chapter 84. Information Security Rules for Street Hail Livery Technology System Providers. Table of Contents
Chapter 84 Information Security Rules for Street Hail Livery Technology System Providers Table of Contents 84-01 Scope of the Chapter... 2 84-02 Definitions Specific to this Chapter... 2 83-03 Information
MOBILE DEVICE SECURITY POLICY
State of Illinois Department of Central Management Services MOBILE DEVICE SECURITY Effective: October 01, 2009 State of Illinois Department of Central Management Services Bureau of Communication and Computer
How To Protect Decd Information From Harm
Policy ICT Security Please note this policy is mandatory and staff are required to adhere to the content Summary DECD is committed to ensuring its information is appropriately managed according to the
Tameside Metropolitan Borough Council ICT Security Policy for Schools. Adopted by:
Tameside Metropolitan Borough Council ICT Security Policy for Schools Adopted by: 1. Introduction 1.1. The purpose of the Policy is to protect the institution s information assets from all threats, whether
Ixion Group Policy & Procedure. Remote Working
Ixion Group Policy & Procedure Remote Working Policy Statement The Ixion Group (Ixion) provide laptops and other mobile technology to employees who have a business requirement to work away from Ixion premises
ICANWK406A Install, configure and test network security
ICANWK406A Install, configure and test network security Release: 1 ICANWK406A Install, configure and test network security Modification History Release Release 1 Comments This Unit first released with
Information Security Risk Assessment Checklist. A High-Level Tool to Assist USG Institutions with Risk Analysis
Information Security Risk Assessment Checklist A High-Level Tool to Assist USG Institutions with Risk Analysis Updated Oct 2008 Introduction Information security is an important issue for the University
WEST LOTHIAN COUNCIL INFORMATION SECURITY POLICY
WEST LOTHIAN COUNCIL INFORMATION SECURITY POLICY DATA LABEL: PUBLIC INFORMATION SECURITY POLICY CONTENTS 1. INTRODUCTION... 3 2. MAIN OBJECTIVES... 3 3. LEGISLATION... 4 4. SCOPE... 4 5. STANDARDS... 4
Information Security Policy and Handbook Overview. ITSS Information Security June 2015
Information Security Policy and Handbook Overview ITSS Information Security June 2015 Information Security Policy Control Hierarchy System and Campus Information Security Policies UNT System Information
PCI DSS FAQ. The twelve requirements of the PCI DSS are defined as follows:
What is PCI DSS? PCI DSS is an acronym for Payment Card Industry Data Security Standards. PCI DSS is a global initiative intent on securing credit and banking transactions by merchants & service providers
MCOLES Information and Tracking Network. Security Policy. Version 2.0
MCOLES Information and Tracking Network Security Policy Version 2.0 Adopted: September 11, 2003 Effective: September 11, 2003 Amended: September 12, 2007 1.0 POLICY STATEMENT The Michigan Commission on
Information Security Policy September 2009 Newman University IT Services. Information Security Policy
Contents 1. Statement 1.1 Introduction 1.2 Objectives 1.3 Scope and Policy Structure 1.4 Risk Assessment and Management 1.5 Responsibilities for Information Security 2. Compliance 3. HR Security 3.1 Terms
PCI DSS Requirements - Security Controls and Processes
1. Build and maintain a secure network 1.1 Establish firewall and router configuration standards that formalize testing whenever configurations change; that identify all connections to cardholder data
Information Security Awareness Training Gramm-Leach-Bliley Act (GLB Act)
Information Security Awareness Training Gramm-Leach-Bliley Act (GLB Act) The GLB Act training packet is part of the Information Security Awareness Training that must be completed by employees. Please visit
University of Illinois at Chicago Health Sciences Colleges Information Technology Group Security Policies Summary
University of Illinois at Chicago Health Sciences Colleges Information Technology Group Security Policies Summary This Summary was prepared March 2009 by Ian Huggins prior to HSC adoption of the most recent
University of Cincinnati Limited HIPAA Glossary
University of Cincinnati Limited HIPAA Glossary ephi System A system that creates accesses, transmits or receives: 1) primary source ephi, 2) ephi critical for treatment, payment or health care operations
Written Information Security Plan (WISP) for. HR Knowledge, Inc. This document has been approved for general distribution.
Written Information Security Plan (WISP) for HR Knowledge, Inc. This document has been approved for general distribution. Last modified January 01, 2014 Written Information Security Policy (WISP) for HR
Network Security Policy
Network Security Policy I. PURPOSE Attacks and security incidents constitute a risk to the University's academic mission. The loss or corruption of data or unauthorized disclosure of information on campus
Data Management Policies. Sage ERP Online
Sage ERP Online Sage ERP Online Table of Contents 1.0 Server Backup and Restore Policy... 3 1.1 Objectives... 3 1.2 Scope... 3 1.3 Responsibilities... 3 1.4 Policy... 4 1.5 Policy Violation... 5 1.6 Communication...
INFORMATION SECURITY MANAGEMENT SYSTEM. Version 1c
INFORMATION SECURITY MANAGEMENT SYSTEM Version 1c Revised April 2011 CONTENTS Introduction... 5 1 Security Policy... 7 1.1 Information Security Policy... 7 1.2 Scope 2 Security Organisation... 8 2.1 Information
LSE PCI-DSS Cardholder Data Environments Information Security Policy
LSE PCI-DSS Cardholder Data Environments Information Security Policy Written By: Jethro Perkins, Information Security Manager Reviewed By: Ali Lindsley, PCI-DSS Project Manager Endorsed By: PCI DSS project
Approved 12/14/11. FIREWALL POLICY INTERNAL USE ONLY Page 2
Texas Wesleyan Firewall Policy Purpose... 1 Scope... 1 Specific Requirements... 1 PURPOSE Firewalls are an essential component of the Texas Wesleyan information systems security infrastructure. Firewalls
U.S. Department of the Interior's Federal Information Systems Security Awareness Online Course
U.S. Department of the Interior's Federal Information Systems Security Awareness Online Course Rules of Behavior Before you print your certificate of completion, please read the following Rules of Behavior
HMIS SECURITY PLAN of the PHILADELPHIA CONTINUUM OF CARE
HMIS SECURITY PLAN of the PHILADELPHIA CONTINUUM OF CARE This plan describes the standards for the security of all data contained in the Philadelphia Continuum of Care Homeless Management Information System
security policy Purpose The purpose of this paper is to outline the steps required for developing and maintaining a corporate security policy.
Abstract This paper addresses the methods and methodologies required to develop a corporate security policy that will effectively protect a company's assets. Date: January 1, 2000 Authors: J.D. Smith,
Payment Cardholder Data Handling Procedures (required to accept any credit card payments)
Payment Cardholder Data Handling Procedures (required to accept any credit card payments) Introduction: The Procedures that follow will allow the University to be in compliance with the Payment Card Industry
MIT s Information Security Program for Protecting Personal Information Requiring Notification. (Revision date: 2/26/10)
MIT s Information Security Program for Protecting Personal Information Requiring Notification (Revision date: 2/26/10) Table of Contents 1. Program Summary... 3 2. Definitions... 4 2.1 Identity Theft...
STATE OF OHIO I. AUTHORITY
STATE OF OHIO SUBJECT: PAGE 1 OF 8. Telecommunication Services SECTION: 05-OIT-12 RULE/CODE REFERENCE: SUPERSEDES: Ohio IT Policy ITP H.2 05-OIT-12 dated 08/19/14 RELATED ACA STANDARDS: EFFECTIVE DATE:
University of Cincinnati HIPAA Administrative, Physical and Technical Safeguards
HIPAA Administrative, Physical and Technical Safeguards Your information security role in protecting HIPAA information Effective Date: 7/1/2014 Prior Effective Date: 10/1/2013 HIPAA Administrative, Physical
CITY OF SAN DIEGO ADMINISTRATIVE REGULATION Number 95.51 PAYMENT CARD INDUSTRY (PCI) COMPLIANCE POLICY. Page 1 of 9.
95.5 of 9. PURPOSE.. To establish a policy that outlines the requirements for compliance to the Payment Card Industry Data Security Standards (PCI-DSS). Compliance with this standard is a condition of
PCI DSS Policies Outline. PCI DSS Policies. All Rights Reserved. ecfirst. 2010. Page 1 of 7 www.ecfirst.com
Policy/Procedure Description PCI DSS Policies Install and Maintain a Firewall Configuration to Protect Cardholder Data Establish Firewall and Router Configuration Standards Build a Firewall Configuration
Department of Homeland Security Management Directive System MD Number: 4900 INDIVIDUAL USE AND OPERATION OF DHS INFORMATION SYSTEMS/ COMPUTERS
Department of Homeland Security Management Directive System MD Number: 4900 INDIVIDUAL USE AND OPERATION OF DHS INFORMATION SYSTEMS/ COMPUTERS 1. Purpose This directive establishes the Department of Homeland
6-8065 Payment Card Industry Compliance
0 0 0 Yosemite Community College District Policies and Administrative Procedures No. -0 Policy -0 Payment Card Industry Compliance Yosemite Community College District will comply with the Payment Card
HIPAA Security Training Manual
HIPAA Security Training Manual The final HIPAA Security Rule for Montrose Memorial Hospital went into effect in February 2005. The Security Rule includes 3 categories of compliance; Administrative Safeguards,
R345, Information Technology Resource Security 1
R345, Information Technology Resource Security 1 R345-1. Purpose: To provide policy to secure the private sensitive information of faculty, staff, patients, students, and others affiliated with USHE institutions,
EAA Policy for Accepting and Handling Credit and Debit Card Payments ( Policy )
EAA Policy for Accepting and Handling Credit and Debit Card Payments ( Policy ) Background Due to increased threat of identity theft, fraudulent credit card activity and other instances where cardholder
Music Recording Studio Security Program Security Assessment Version 1.1
Music Recording Studio Security Program Security Assessment Version 1.1 DOCUMENTATION, RISK MANAGEMENT AND COMPLIANCE PERSONNEL AND RESOURCES ASSET MANAGEMENT PHYSICAL SECURITY IT SECURITY TRAINING AND
NHSnet SyOP 9.2 NHSnet Portable Security Policy V1. NHSnet : PORTABLE COMPUTER SECURITY POLICY. 9.2 Introduction
NHSnet : PORTABLE COMPUTER SECURITY POLICY 9.2 Introduction This document comprises the IT Security policy for Portable Computer systems as described below. For the sake of this document Portable Computers
Payment Card Industry (PCI) Policy Manual. Network and Computer Services
Payment Card Industry (PCI) Policy Manual Network and Computer Services Forward This policy manual outlines acceptable use Black Hills State University (BHSU) or University herein, Information Technology
DHHS Information Technology (IT) Access Control Standard
DHHS Information Technology (IT) Access Control Standard Issue Date: October 1, 2013 Effective Date: October 1,2013 Revised Date: Number: DHHS-2013-001-B 1.0 Purpose and Objectives With the diversity of
1B1 SECURITY RESPONSIBILITY
(ITSP-1) SECURITY MANAGEMENT 1A. Policy Statement District management and IT staff will plan, deploy and monitor IT security mechanisms, policies, procedures, and technologies necessary to prevent disclosure,
Department of Information Technology Remote Access Audit Final Report. January 2010. promoting efficient & effective local government
Department of Information Technology Remote Access Audit Final Report January 2010 promoting efficient & effective local government Background Remote access is a service provided by the county to the Fairfax
Procedure Title: TennDent HIPAA Security Awareness and Training
Procedure Title: TennDent HIPAA Security Awareness and Training Number: TD-QMP-P-7011 Subject: Security Awareness and Training Primary Department: TennDent Effective Date of Procedure: 9/23/2011 Secondary
Protecting Personal Information: The Massachusetts Data Security Regulation (201 CMR 17.00)
Protecting Personal Information: The Massachusetts Data Security Regulation (201 CMR 17.00) May 15, 2009 LLP US Information Security Framework Historically industry-specific HIPAA Fair Credit Reporting
