Guide to good practice: micro data handling and security
|
|
|
- Josephine Perkins
- 10 years ago
- Views:
Transcription
1 The work is licensed under the Creative Commons Attribution-Non-Commercial-Share Alike 2.0 UK: England and Wales Licence. To view a copy of this licence, visit creativecommons.org/licenses/by-nc-sa/2.0/uk/ Guide to good practice: micro data handling and security PUBLIC VERSION 31 AUGUST T +44 (0) E [email protected] UK DATA ARCHIVE UNIVERSITY OF ESSEX WIVENHOE PARK COLCHESTER ESSEX, CO4 3SQ... WE ARE SUPPORTED BY THE UNIVERSITY OF ESSEX, THE ECONOMIC AND SOCIAL RESEARCH COUNCIL, AND THE JOINT INFORMATION SYSTEMS COMMITTEE
2 Document Control Created by: Maintained by: Karen Dennison Karen Dennison Version: Controlled document: Not applicable Last reviewed: 31 AUGUST 2010 Review due date: 31 AUGUST 2011 Contents 1. Licence framework End User Licence data Special conditions Accessing data Re-use of data Research projects and teams Teaching purposes Security Data storage security End User Licence data Special Licence data Secure Data Service data Passwords and pass-phrases Audit of confidentiality and security procedures Statistical disclosure Direct disclosure Indirect disclosure Reporting publications When research is complete Guidelines on destroying Special Licence data Institutional responsibilities Special Licence and Secure Data Service data Breach procedures Help and feedback Page 2 of 12
3 Introduction This guide is for users of micro data accessed from the UK Data Archive (the Archive) through its Economic and Social Data Service (ESDS). In particular, all users who obtain Special Licence or Secure Data Service (SDS) data, including data that require Accreditation as an Approved Researcher, are required to read it under the terms of access. 1. Licence framework The Archive is the guardian of data for the data owners. The conditions under which data may be accessed are specified under licence with the data owners. These conditions include providing the data only to users who have registered with the ESDS and agreed to an End User Licence (EUL). Researchers accessing the data have responsibilities to preserve data confidentiality and to observe the ethical and legal obligations pertaining to the data. In particular, researchers must maintain the commitments made to survey respondents to preserve the confidentiality of the data provided End User Licence data Use of the data is governed by a legally-binding EUL which forms part of the registration process. Each individual who requires access to data has to register and will need a UK Federation login. Users who have no way of obtaining a UK Federation login can apply to the Archive. Under the terms of the EUL, users agree: not to use the data for any commercial purpose (except with prior permission/under an appropriate commercial licence agreement); to preserve the confidentiality of, and not attempt to identify, individuals, households or organisations in the data; to use the recommended methods of citation and acknowledgement in publications; to supply the bibliographic details of any published work based on the data collections; to ensure that the means of access to the data (such as passwords) are kept secure and not disclosed to anyone else; to abide by any further special conditions Special conditions Additional legally-binding conditions to those of the EUL may be specified by the data owners for particular data collections. Where data pose a higher risk of disclosure, special conditions may take the form of a Special Licence that requires the completion of an additional application form, the signature(s) of the researcher(s), and the explicit permission of the data owners to release the data to the researcher(s). Access to Special Licence data may be restricted to certain users (for example, to UK applicants only). Access to download ONS Special Licence data via the Archive is available through the legal framework set out in the Statistics and Registration Service Act which came into force 1 April Any registered user wanting to download ONS Special Licence data will have to be Page 3 of 12
4 accredited by the UK Statistics Authority as an Approved Researcher. To apply for accreditation a user will complete (i) forms that will require evidence that he/she is a fit and proper person and details about the purpose of the research (ii) an online order for the data and (iii) a signed declaration that he/she understands the confidentiality obligations owed to those data including its physical security. Data considered to be more disclosive than Special Licence data may be available through a virtual secure environment to UK academics via the ESRC-funded UK Data Archive Secure Data Service. Any registered user requiring access to SDS will have to (i) be accredited as an ESRC and/or UK Statistics Authority Approved Researcher (ii) complete SDS Training and (iii) agree to an SDS Service Agreement. 2. Accessing data Data can only be accessed under certain conditions: under the EUL, data can only be accessed by registered users; data supplied under special conditions can only be accessed by those who have accepted these conditions; Special Licence and Secure Data Service data can only be accessed by approved individuals for a specified usage; Secure Data Service data can only be analysed remotely within the SDS virtual secure environment and outputs are only released to researchers subject to statistical disclosure control by SDS staff Re-use of data To re-use data already supplied, but for a different purpose, it is necessary to re-apply for access. For example, if depositor permission is required, this will need to be obtained again Research projects and teams Users are required to register all usages of data, and to add other users working on the same usage to the usage details in their online account. Each usage is given a period of access that cannot exceed two years for EUL data and three years for Special Licence and Secure Data Service data. Users should contact the help desk to extend the expiry date of a project. Where a researcher joins a research team that is using Special Licence or Secure Data Service data: the new researcher must place an online order for the data and complete the necessary forms; permission must be sought and gained before the new researcher can access the data; the researcher must complete SDS training to access Secure Data Service data; the Archive will provide advice on the process to be followed. Page 4 of 12
5 2.3. Teaching purposes microdatahandlingandsecurity.doc When using data for teaching all students must be registered or have signed an access agreement for teaching, which should be returned to the Archive. Special Licence and Secure Data Service data cannot be used for teaching Security Passwords and pass-phrases should never be disclosed to anyone else. Data should not be left on a computer that might enable unauthorised access. 3. Data storage security 3.1. End User Licence data All data provided by the Archive needs to be stored under conditions that meet the undertakings given in the EUL (see section 7 for institutional responsibilities): access to PCs on which data are held should require personal authentication (secure username and password/pass-phrase); if data are placed in a shared directory or on a Local Area Network (LAN), access should only be available, via personal authentication, to those permitted to use the data; means of access to the data (such as passwords or pass-phrases) should be kept secure; data must be stored securely with data on portable media (e.g. a back-up on CD) protected using a secure password/pass-phrase; users should be aware of, and follow, any additional information security guidelines provided by their institution/organisation Special Licence data Special Licence data should additionally: be protected, where possible, using pass-phrases instead of passwords; be stored in physically secure conditions (e.g. any portable or printed copies should be stored in a locked cabinet with restricted access); be stored on a PC in a room which is NOT accessible to the general public; be stored on a PC in a locked office when unattended; be protected by a screen-saver with an interval of five minutes and that requires a secure password/pass-phrase to unlock it; only be accessed, in an institutional setting, via a stand-alone PC or a closely controlled LAN Page 5 of 12
6 with restricted access - data must not be accessed at a private residence; must not have live internet links while the data are unencrypted on the machine unless access is through a secure organisational provider, such as JANET: (If there is any uncertainty as to whether an organisational provider is secure users should contact the help desk with details of the system in place.) - stand-alone PCs and LANs, which have internet access via broadband (and not through a secure organisational provider e.g. JANET) must be disconnected from the Internet and the broadband cable must be physically disconnected from the PC; - stand-alone PCs and LANs, which have internet access via dial-up telephone connection (and not through a secure organisational provider e.g. JANET), must not have live internet links while the data are unencrypted on the machine; be accessed on a site which has security standards that meet the guidelines in this guide; be auditable; be accessed at a site within the UK as Special Licence data will not be provided to licence holders who are sited at, and thus would intend to access data, at an institution that is not within the UK; be deleted upon project completion: - this must be confirmed by the licence holder; - copies of data (including derived datasets) must be deleted from all PCs used; - any printed or electronic copies, including back-ups, temporary or intermediate files, must be destroyed; - any portable copies (e.g. CDs) must be destroyed or returned to the Archive; - Section 6.1 has detailed guidelines Secure Data Service data Secure Data Service data will: only be accessed remotely via the SDS virtual secure environment; only be accessed in an institutional setting and within the UK - data must not be accessed at a private residence; be accessed on a site which has security standards that meet the guidelines in this guide; only be accessed in a room which is NOT accessible to the general public and that is locked when unattended; (depending upon the data owner requirements and the disclosiveness of the data) be accessed using one of the following: o o o the researcher s desktop PC; secure machine provided by the SDS; a designated SDS safe room; Page 6 of 12
7 be protected by a screen-saver with an interval of five minutes and that requires a secure password/pass-phrase to unlock it. Data may not be removed from the SDS virtual secure environment under any circumstances and outputs will only be released to the researcher subject to statistical disclosure control checks by SDS staff. Under no circumstances should users attempt to take away/copy outputs that have not been checked and released to them by the SDS. SDS data and unauthorised outputs should not be printed or be seen on the user s computer screen by unauthorised individuals Researchers who have been approved to work together on the same project may only share unchecked outputs from that project with each other in the relevant shared project area of the SDS virtual secure environment. Temporary or duplicate files and disclosive outputs should be deleted by the researcher(s) from the SDS virtual secure environment. Use of the SDS virtual secure environment will be monitored including any suspicious activity and keystrokes Passwords and pass-phrases Pass-phrases differ from passwords in format and in length. Pass-phrases are usually much longer - up to 100 characters or more and contain spaces. The greater length and format of pass-phrases makes them more secure. A password should contain a combination of at least eight alphanumeric and symbolic characters. Quotes should not be used as pass-phrase characters. Passwords and pass-phrases should: not be disclosed to anyone else; not be written down; be changed at least every three months; not be easily guessable; The Secure Data Service will provide users with personal logins. Passwords will be renewed every three months and logins will expire at the end of the project Audit of confidentiality and security procedures The depositor of Special Licence or Secure Data Service data may reserve the right to conduct an onsite audit of the licence holder's confidentiality and security procedures and practices, or to require a report of such an audit. For the purpose of conducting an audit, the depositor may reserve the right of entry to the premises where the data are stored and/or accessed. (Also see section 7.1). 4. Statistical disclosure 4.1. Direct disclosure Page 7 of 12
8 The EUL requires an undertaking not to attempt to identify any individual, household or organisation or claim to have done so. Where EUL data are matched with external data sources this must not be for the purposes of identification. For Special Licence data, it is forbidden to attempt to match individual, household, or organisation records to any other data, including data from other Special Licence data series, at the level of individual, household or organisation. Only area-level descriptors or other group-level classifications may be matched for analysis purposes. Whilst the Secure Data Service provides a secure environment in which data could be linked (for example with another dataset in the SDS collection or with the researcher s own data) this is strictly subject to the approval of the data owners. Users will only be able to access those datasets approved for a particular research project it will not be possible to subsequently add new data without a new application and approval. Where a user is approved to link data not in the SDS collection, the data will be uploaded to the user s area subject to checks by SDS. ONS business data may be linked using the anonymised reference numbers (known as IDBR references). A user may be able to produce a larger combined dataset, with many variables providing characteristics that will directly identify an organisation. While this is an acceptable risk within the confines of the SDS virtual secure environment, users should be aware that output requests containing information that will identify an organisation, will be rejected Indirect disclosure Special Licence data Outputs from Special Licence data must be subjected to disclosure control. The guidance below is general advice but users should also refer to the full details of the procedures to be used in the Government Statistical Service (GSS) guidance available from the Office for National Statistics Access Arrangements web page. Tables that contain very small numbers in some cells may be disclosive. Tables should not report numbers or percentages in cells based on only one or two cases. Cells based on one or two cases should be combined with other cells or, where this is not appropriate, reported as zero per cent. Tables and other outputs must not be published in a form where the level of geography would threaten the confidentiality of the data. To guarantee safety, outputs from Special Licence data should not be published if the geography is lower than UK Government Office Region (GOR). If there is a requirement to publish outputs from Special Licence data with a lower level of geography i.e. between GOR and local authority, then the licence holder must consider whether there is a risk of disclosure. Where there is any doubt, the licence holder must contact the help desk to gain confirmation of the confidentiality of any outputs for publication with geography below GOR. No outputs may be published with a geography below local authority. Although most outputs from models or other statistical analysis will not be disclosive, care should be taken to ensure that individuals, households or organisations cannot be identified. In particular, results based on very small numbers should be avoided. Any output that refers to unit records, e.g. a maximum or minimum value, should be avoided. Models should not report actual values for residuals. Graphical outputs should be based on non-disclosive data. Particular care should be taken not to report extreme outliers. Graphical outputs should respect all the rules specified in the GSS Disclosure Control Policy. Page 8 of 12
9 Secure Data Service data Access to data held in the SDS may only be accessed within the SDS virtual secure environment. Users must conduct all their analysis, and produce outputs (such as papers, presentations etc) within this area. Hence data may not be released from the SDS under any circumstance. Outputs may be returned to researchers subject to a full manual statistical disclosure control (SDC) by a member of the SDS team. The SDC requirements for these data differ from those mentioned above for the Special Licence files. There are two reasons for this difference: first, the data are more sensitive, and contain variables that directly identify survey respondents; and secondly, the SDS will make available business data, for which a large number of additional methods (other than social science techniques) may be adopted by researchers, and present additional disclosure concerns that should be considered. For example, Herfindahl/concentration indices are routinely calculated by industrial economists using business data. Such measures generate additional disclosure concerns which are not addressed by the guidelines for Special Licence data above. Users should remain wary of producing outputs containing low cell counts. However, there are also other techniques which users should be vigilant about when producing their outputs. Details of the relevant SDC guidelines for outputs generated in the SDS may be found in the ESSnet Guidelines for the checking of output based on microdata research and we recommend that users consult these guidelines. All users who wish to access data in the SDS will be required to attend a training course where these ESSnet SDC guidelines will be explained. If users are unsure about SDC when they produce outputs, we recommend that they speak to an SDS support officer as soon as possible, and certainly before they intend to request their outputs. For example, a researcher will be disappointed if they write an entire paper within the SDS, only to find that it is not released to them due to SDC problems. 5. Reporting publications All users of data are required to report publications arising from their research to the Archive. It is good practice to inform the Archive of any publications at the time of publication. The Archive will provide annual reports to ONS on publications arising from the use of ONS Special Licence and Secure Data Service data. ONS reserves the right to ask to see drafts of publications based on ONS Special Licence data for the purpose of commenting regarding compliance with the conditions for disclosure protection. If this condition is imposed, users will be notified when their application is processed. Secure Data Service users are not permitted to publish outputs unless they have been checked and released to them by the SDS When research is complete It is recommended that researchers always retain a well-documented copy of the syntax used to prepare a paper or report. Derived data should be offered for deposit at the Archive. Page 9 of 12
10 When a project has been completed it is good practice for researchers to remove all copies of the data, including derived datasets, back-ups, paper copies, portable copies (including CDs), and all electronic copies from every PC used. Researchers using SDS data should ensure that any unnecessary or duplicate files are removed from the SDS secure virtual environment at the end of the project. It is essential that all copies of Special Licence data held by researchers are destroyed or, where held on portable media, returned to the Archive at the end of the specified time period. Special Licence derived data can also be returned to the Archive and the Archive can maintain the data on behalf of the user in a secure area for a five-year period. To re-access the data, the researcher should contact the Archive. Syntax files can be removed from the Secure Data Service virtual secure environment subject to clearance checks by SDS staff. Alternatively the SDS can maintain syntax files on behalf of the user for a five-year period Guidelines on destroying Special Licence data The following are guidelines for destroying data: data should be deleted from the system on which it has been stored using a secure erasure programme, such as Disk Sanitizer ( or similar - which repeatedly overwrites files a number of times, until such time as the original data could not be retrieved forensically; the recycle/trash bin should be emptied, preferably to be immediately followed by running a secure erasure programme to erase the unused areas of the disk; CDs and portable media should be returned to the Archive or cut into many pieces or shredded using a disk shredder and then securely disposed of; backup tapes should either be completely overwritten and degaussed (demagnetised) before being re-used or disposed of; paper copies should be destroyed by shredding, preferably using a cross-cut shredder; before the PC leaves the possession of the organisation (for destruction or second hand sale, etc.) the hard disk should be completely erased using a secure erasure programme; destruction of Special Licence data must be confirmed to the Archive by the licence holder. 7. Institutional responsibilities Institutes of UK higher or further education (HE/FE), are bound by JANET policies ( including the JANET Security Policy that places responsibilities on every person and organisation involved in the use or operation of JANET to protect the network against security breaches. UK HE/FE should also follow JISC guidance on information security, including handling information legally ( There is a requirement that all central government departments must meet internationally recognised information and security management standards (e.g. ISO/IEC and BS 7799) for their systems. Local authorities are also obliged, by 2005, to comply with the BS 7799 security standard as part of their Implementing Electronic Government (IEG) requirements. Page 10 of 12
11 7.1. Special Licence and Secure Data Service data Where access to data requires an institutional signature: in Universities, the application should be signed by the Head of Department or School, Head of Research Centre, or the chair of the University Ethics Committee; in Government departments, or local authorities, the licence should be signed by the statistician with responsibility to represent the organisation or to enter it into a contractual relationship; in all cases an institution is required to accept legal responsibility for the user. For a user accessing ONS Special Licence data through the Approved Researcher mechanism, it is the user s responsibility to ensure that they can store and access the data in a suitably secure physical and electronic environment. Users of Special Licence and Secure Data Service data undertake to allow the depositor access to the premises where the data are stored and/or accessed for the purpose of conducting an audit, without notice and at any reasonable time. (Also see Section 3.4). Access to Special Licence and Secure Data Service data may require the user to provide the contact details of a senior member of staff at their institution who can vouch for their suitability for access to the data. The Archive and ONS reserve the right to contact the senior member of staff to ask for a reference. 8. Breach procedures The licence holder is required to report promptly a breach of any of the terms of the EUL, including the terms of any data supplied under special conditions. Failure to disclose details of a breach constitutes a breach of the licence. Breach of the terms of the EUL, including any special conditions, may result in the following actions: immediate termination of access to all services provided by the Archive and ESDS either permanently or temporarily; legal action being taken against the individual who has breached the terms of the EUL; withdrawal of access to all Archive and ESDS services either permanently or temporarily to the licence holder s institution. Additionally, any breach in the terms of access for Special Licence or Secure Data Service data: will result in the immediate termination of the licence holder's access to the data and the termination of the licence - depending upon the seriousness of the breach, the termination of access may be permanent; may result in sanctions being sought against the licence holder by the data owner; for ONS Special Licence and ONS Secure Data Service data, under the Statistics and Registration Services Act 2007, will incur penalties as specified in S39 of the Act - this may include a fine and/or imprisonment; Page 11 of 12
12 for Secure Data Service data penalties could also include individual or institutional sanction from ESRC funding and institutional suspension from all ESRC data services. Researchers will be provided with detailed guidance on breaches and penalties in the SDS training. 9. Help and feedback This guide will be regularly updated. For further advice on any of the issues raised, or to provide suggestions or comments, contact the ESDS or SDS help desk. ESDS help desk telephone: +44 (0) SDS help desk telephone: +44 (0) Page 12 of 12
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
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
Information Circular
Information Circular Enquiries to: Brooke Smith Senior Policy Officer IC number: 0177/14 Phone number: 9222 0268 Date: March 2014 Supersedes: File No: F-AA-23386 Subject: Practice Code for the Use of Personal
Scottish Rowing Data Protection Policy
Revision Approved by the Board August 2010 1. Introduction As individuals, we want to know that personal information about ourselves is handled properly, and we and others have specific rights in this
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
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
Human Resources Policy documents. Data Protection Policy
Policy documents Aims of the Policy apetito is committed to meeting its obligations under data protection law. As a business, apetito handles a range of Personal Data relating to its customers, staff and
The Manitowoc Company, Inc.
The Manitowoc Company, Inc. DATA PROTECTION POLICY 11FitzPatrick & Associates 4/5/04 1 Proprietary Material Version 4.0 CONTENTS PART 1 - Policy Statement PART 2 - Processing Personal Data PART 3 - Organisational
Merthyr Tydfil County Borough Council. Data Protection Policy
Merthyr Tydfil County Borough Council Data Protection Policy 2014 Cyfarthfa High School is a Rights Respecting School, we recognise the importance of ensuring that the United Nations Convention of the
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
Protection of Computer Data and Software
April 2011 Country of Origin: United Kingdom Protection of Computer Data and Software Introduction... 1 Responsibilities...2 User Control... 2 Storage of Data and Software... 3 Printed Data... 4 Personal
Secure Storage, Communication & Transportation of Personal Information Policy Disclaimer:
Secure Storage, Communication & Transportation of Personal Information Policy Version No: 3.0 Prepared By: Information Governance, IT Security & Health Records Effective From: 20/12/2010 Review Date: 20/12/2011
IT ACCESS CONTROL POLICY
Reference number Approved by Information Management and Technology Board Date approved 30 April 2013 Version 1.0 Last revised Review date March 2014 Category Owner Target audience Information Assurance
Corporate Information Security Policy
Corporate Information Security Policy. A guide to the Council s approach to safeguarding information resources. September 2015 Contents Page 1. Introduction 1 2. Information Security Framework 2 3. Objectives
White Paper: NCBI Database of Genotypes and Phenotypes (dbgap) Security Best Practices Compliance Overview for the New DNAnexus Platform
White Paper: NCBI Database of Genotypes and Phenotypes (dbgap) Security Best Practices Compliance Overview for the New DNAnexus Platform April 18, 2013 Overview This White Paper summarizes how the new
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
Information Security Policy
Information Security Policy The purpose of this Policy is to describe the procedures and processes in place to ensure the secure and safe use of the federation s network and its resources and to protect
Rotherham CCG Network Security Policy V2.0
Title: Rotherham CCG Network Security Policy V2.0 Reference No: Owner: Author: Andrew Clayton - Head of IT Robin Carlisle Deputy - Chief Officer D Stowe ICT Security Manager First Issued On: 17 th October
www.neelb.org.uk Web Site Download Carol Johnston
What I need to know about data protection and information security when purchasing a service that requires access to my information by a third party. www.neelb.org.uk Web Site Download Carol Johnston Corporate
2.0 Emended due to the change to academy status Review Date. ICT Network Security Policy Berwick Academy
Version History Author Approved Committee Version Status date Eddie Jefferson 09/15/2009 Full Governing 1.0 Final Version Body Eddie Jefferson 18/08/2012 Full Governing Body 2.0 Emended due to the change
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
INFORMATION SECURITY POLICY
INFORMATION SECURITY POLICY Rev Date Purpose of Issue/ Description of Change Equality Impact Assessment Completed 1. June 2011 Initial Issue 2. 29 th March 2012 Second Version 3. 15 th April 2013 Third
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
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
ICT SECURITY POLICY. Strategic Aim To continue to develop and ensure effective leadership, governance and management throughout the organisation
ICT SECURITY POLICY Strategic Aim To continue to develop and ensure effective leadership, governance and management throughout the organisation Responsibility Assistant Principal, Learner Services Jannette
Policy Document. IT Infrastructure Security Policy
Policy Document IT Infrastructure Security Policy [23/08/2011] Page 1 of 10 Document Control Organisation Redditch Borough Council Title IT Infrastructure Security Policy Author Mark Hanwell Filename IT
ABERDARE COMMUNITY SCHOOL
ABERDARE COMMUNITY SCHOOL IT Security Policy Drafted June 2014 Revised on....... Mrs. S. Davies (Headteacher) Mr. A. Maddox (Chair of Interim Governing Body) IT SECURITY POLICY Review This policy has been
ARCHIVING YOUR DATA: PLANNING AND MANAGING THE PROCESS
ARCHIVING YOUR DATA: PLANNING AND MANAGING THE PROCESS LIBBY BISHOP. RESEARCHER LIAISON UNIVERSITY OF ESSEX TCRU/NOVELLA SPECIAL SEMINAR - LONDON 29 MAY 2012 THE & ESDS QUALIDATA forty years experience
University of Liverpool
University of Liverpool Information Security Policy Reference Number Title CSD-003 Information Security Policy Version Number 3.0 Document Status Document Classification Active Open Effective Date 01 October
Network Security Policy
IGMT/15/036 Network Security Policy Date Approved: 24/02/15 Approved by: HSB Date of review: 20/02/16 Policy Ref: TSM.POL-07-12-0100 Issue: 2 Division/Department: Nottinghamshire Health Informatics Service
Caldwell Community College and Technical Institute
Caldwell Community College and Technical Institute Employee Computer Usage Policies and Procedures I. PURPOSE: The purpose of this section is to define the policies and procedures for using the administrative
Information Security
Information Security A staff guide to the University's Information Systems Security Policy Issued by the IT Security Group on behalf of the University. Information Systems Security Guidelines for Staff
Network and Workstation Acceptable Use Policy
CONTENT: Introduction Purpose Policy / Procedure References INTRODUCTION Information Technology services including, staff, workstations, peripherals and network infrastructures are an integral part of
Information Technology Acceptable Usage Policy
Information Technology Acceptable Usage Policy Version 3.0 This policy maybe updated at anytime (without notice) to ensure changes to the HSE s organisation structure and/or business practices are properly
How To Protect A Hampden County Hmis From Being Hacked
Hampden County HMIS Springfield Office of Housing SECURITY PLAN Security Officers The Springfield Office of Housing has designated an HMIS Security Officer whose duties include: Review of the Security
HIPAA Training for Hospice Staff and Volunteers
HIPAA Training for Hospice Staff and Volunteers Hospice Education Network Objectives Explain the purpose of the HIPAA privacy and security regulations Name three patient privacy rights Discuss what you
Computing Services Information Security Office. Security 101
Computing Services Information Security Office Security 101 Definition of Information Security Information security is the protection of information and systems from unauthorized access, disclosure, modification,
The guidance applies to all records, regardless of the medium in which they are held, including e-mail, spreadsheets, databases and paper files.
Best Practice in Disposing of Records For whom is this guidance intended? This guidance is intended for all University staff that need to dispose of records, on an occasional or regular basis. It is likely
POLICY FOR PRESERVATION / ARCHIVAL OF DOCUMENTS
POLICY FOR PRESERVATION / ARCHIVAL OF DOCUMENTS (As approved by the board at its meeting held on 27 th October 2015) 1. Introduction Securities and Exchange Board of India (SEBI) has introduced SEBI (Listing
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
IT Data Security Policy
IT Data Security Policy Contents 1. Purpose...2 2. Scope...2 3. Policy...2 Access to the University computer network... 3 Security of computer network... 3 Data backup... 3 Secure destruction of data...
SECURITY POLICIES AND PROCEDURES
2014 WorldEscrow N.V./S.A. SECURITY POLICIES AND PROCEDURES This document describes internal security rules within the WorldEscrow N.V./S.A. organization. Content 1) Employee Responsibilities... 1 2) Use
Policies and Procedures for Electronic Protected Health Information (ephi) and Personally Identifiable Information (PII)
Policies and Procedures for Electronic Protected Health Information (ephi) and Personally Identifiable Information (PII) Effective Date: April 10, 2012 Prepared by: Joe Raschke (IT) Table of Contents Purpose
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,
Protection. Code of Practice. of Personal Data RPC001147_EN_WB_L_1
Protection of Personal Data RPC001147_EN_WB_L_1 Table of Contents Data Protection Rules Foreword From the Data Protection Commissioner Introduction From the Chairman Data Protection Responsibility of Employees
Service Agreement SURE Project Workspace
Service Agreement SURE Project Workspace Applicant Information Project Name Research Organisation ABN Number Contract number of SURE Head Agreement: This is an agreement to acquire a SURE Project Workspace
Information Security Policy. Policy and Procedures
Information Security Policy Policy and Procedures Issue Date February 2013 Revision Date February 2014 Responsibility/ Main Point of Contact Neil Smedley Approved by/date Associated Documents Acceptable
Angard Acceptable Use Policy
Angard Acceptable Use Policy Angard Staffing employees who are placed on assignments with Royal Mail will have access to a range of IT systems and mobile devices such as laptops and personal digital assistants
Purpose: To comply with the Payment Card Industry Data Security Standards (PCI DSS)
Procedure Credit Card Handling and Security for Departments/Divisions and Elected/Appointed Offices Last Update: January 19, 2016 References: Credit Card Payments Policy Purpose: To comply with the Payment
Working Together Aiming High!
Poplar Street Primary School ICT Security and Acceptable Use Policy E-Safety policy 2013/14 Working Together Aiming High! 1 Contents 1. Introduction... 3 2. Policy Objectives... 3 3. Application... 3 4.
ITU-10002 Computer Network, Internet Access & Email policy ( Network Access Policy )
ITU-10002 Computer Network, Internet Access & Email policy South Norfolk Council IT Unit Documentation www.south-norfolk.gov.uk Page : 2 of 8 Summary This policy informs all users about acceptable use
Secure Mobile Shredding and. Solutions
Secure Mobile Shredding and Data Erasure Solutions SECURE MOBILE SHREDDING & DATA ERASURE SERVICES... NCE s mobile shredding and data erasure service permanently destroys your data in a secure and controlled
Information Technology Security Policies
Information Technology Security Policies Randolph College 2500 Rivermont Ave. Lynchburg, VA 24503 434-947- 8700 Revised 01/10 Page 1 Introduction Computer information systems and networks are an integral
Sure Unlimited and Pro Broadband Service
Sure Unlimited and Pro Broadband Service SURE UNLIMITED AND PRO BROADBAND PRODUCT DESCRIPTION The Sure Unlimited and Pro Broadband services from Sure Jersey Limited are always-on Internet connections.
Scotland s Commissioner for Children and Young People Records Management Policy
Scotland s Commissioner for Children and Young People Records Management Policy 1 RECORDS MANAGEMENT POLICY OVERVIEW 2 Policy Statement 2 Scope 2 Relevant Legislation and Regulations 2 Policy Objectives
INTERNATIONAL SOS. Data Retention, Archiving and Destruction Policy. Version 1.07
INTERNATIONAL SOS Data Retention, Archiving and Destruction Policy Document Owner: LCIS Division Document Manager: Group General Counsel Effective: January 2009 Revised: 2015 All copyright in these materials
ACRONYMS: HIPAA: Health Insurance Portability and Accountability Act PHI: Protected Health Information
NAMI EASTSIDE - 13 POLICY: Privacy and Security of Protected Health Information (HIPAA Policies and Procedures) DATE APPROVED: Pending INTENT: (At present, none of the activities that NAMI Eastside provides
REMOTE WORKING POLICY
Reference number Approved by Information Management and Technology Board Date approved 30 April 2013 Version 1.0 Last revised Review date March 2014 Category Owner Target audience Information Assurance
Information Security Policies. Version 6.1
Information Security Policies Version 6.1 Information Security Policies Contents: 1. Information Security page 3 2. Business Continuity page 5 3. Compliance page 6 4. Outsourcing and Third Party Access
Remote Access Policy
BASINGSTOKE AND NORTH HAMPSHIRE NHS FOUNDATION TRUST Remote Access Policy Summary This is a new document which sets out the policy for remote access to the Trust s network and systems. Remote access is
HERTSMERE BOROUGH COUNCIL
HERTSMERE BOROUGH COUNCIL DATA PROTECTION POLICY October 2007 1 1. Introduction Hertsmere Borough Council ( the Council ) is fully committed to compliance with the requirements of the Data Protection Act
Protection. Code of Practice. of Personal Data RPC001147_EN_D_19
Protection of Personal Data RPC001147_EN_D_19 Table of Contents Data Protection Rules Foreword From the Data Protection Commissioner Introduction From the Chairman Data Protection Rules Responsibility
Access Control Policy
Version 3.0 This policy maybe updated at anytime (without notice) to ensure changes to the HSE s organisation structure and/or business practices are properly reflected in the policy. Please ensure you
Acceptable Use Guidelines
Attachment to the Computer and Information Security and Information Management Policies Acceptable Use Guidelines NZQA Quality Management System Supporting Document Purpose These Acceptable Use Guidelines
Conditions of Use. Communications and IT Facilities
Conditions of Use of Communications and IT Facilities For the purposes of these conditions of use, the IT Facilities are [any of the University s IT facilities, including email, the internet and other
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
Information Technology (IT) Security Guidelines for External Companies
Information Technology (IT) Security Guidelines for External Companies Document History: Version Name Org.-Unit Date Comments 1.1 Froehlich, Hafner Audi I/GO VW K-DOK 25.05.2004 Table of Contents: 1. Goal...3
A Guide to Information Technology Security in Trinity College Dublin
A Guide to Information Technology Security in Trinity College Dublin Produced by The IT Security Officer & Training and Publications 2003 Web Address: www.tcd.ie/itsecurity Email: [email protected] 1 2
Caedmon College Whitby
Caedmon College Whitby Data Protection and Information Security Policy College Governance Status This policy was re-issued in June 2014 and was adopted by the Governing Body on 26 June 2014. It will be
So the security measures you put in place should seek to ensure that:
Guidelines This guideline offers an overview of what the Data Protection Act requires in terms of information security and aims to help you decide how to manage the security of the personal data you hold.
Terms and Conditions of Use - Connectivity to MAGNET
I, as the Client, declare to have read and accepted the terms and conditions set out below for the use of the network connectivity to the Malta Government Network (MAGNET) provided by the Malta Information
Research Data Management Procedures
Research Data Management Procedures pro-123 To be read in conjunction with: Research Data Management Policy Version: 2.00 Last amendment: Oct 2014 Next Review: Oct 2016 Approved By: Academic Board Date:
How To Destroy Data From A Hard Drive
Safe, Secure and Certified Data Destruction Solutions to meet your individual needs Whether you require data destruction supplementary or exclusively to our IT disposal solution, our fully security screened
DATA PROTECTION IT S EVERYONE S RESPONSIBILITY. An Introductory Guide for Health Service Staff
DATA PROTECTION IT S EVERYONE S RESPONSIBILITY An Introductory Guide for Health Service Staff 1 Message from Director General Dear Colleagues The safeguarding of and access to personal information has
DEALERSHIP IDENTITY THEFT RED FLAGS AND NOTICES OF ADDRESS DISCREPANCY POLICY
DEALERSHIP IDENTITY THEFT RED FLAGS AND NOTICES OF ADDRESS DISCREPANCY POLICY This Plan we adopted by member, partner, etc.) on Our Program Coordinator (date). (Board of Directors, owner, We have appointed
Data Protection Policy
1. Introduction 1.1 The College needs to keep certain information about its employees, students and other stakeholders, for example to allow it to monitor performance, achievements and health and safety.
