13.07.2015 Views

HS 9453-D Remote Access - Office of Compliance Services - UCLA ...

HS 9453-D Remote Access - Office of Compliance Services - UCLA ...

HS 9453-D Remote Access - Office of Compliance Services - UCLA ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Remote</strong> <strong>Access</strong> Policy<strong>HS</strong> <strong>9453</strong>-DREMOTE ACCESSPURPOSEThe purpose <strong>of</strong> this policy is to set forth the procedures for obtaining remote access intothe networks <strong>of</strong> the <strong>UCLA</strong> Health System and David Geffen School <strong>of</strong> Medicine at<strong>UCLA</strong> (hereafter referred to as “<strong>UCLA</strong> Health”).DEFINITIONS“Protected health information” or “PHI” is any individually identifiable healthinformation, in any format, including verbal communications, regarding a patient createdas a consequence <strong>of</strong> the provision <strong>of</strong> health care. “Individually identifiable” means thatthe health or medical information includes or contains any element <strong>of</strong> personalidentifying information sufficient to allow identification <strong>of</strong> the individual, such as thepatient’s name, address, electronic mail address, telephone number, or social securitynumber, or other information that, alone or in combination with other publicly availableinformation, reveals the individual’s identity. PHI includes patient billing and healthinsurance information and applies to a patient’s past, current or future physical ormental health or treatment.“Electronic Protected Health Information” or “ePHI” is PHI that is transmitted byelectronic media or is maintained in electronic media. For example, ePHI includes alldata that may be transmitted over the Internet, or stored on a computer, a CD, a disk,magnetic tape or other media.“Personal Information (PI)” as used in this policy is an individual’s first name or firstinitial and last name combined with any one <strong>of</strong> the following:(1) social security number,(2) driver’s license number or California identification card number,(3) account number, credit, or debit card number, in combination with anyrequired security code, access code, or password that would permitaccess to an individual’s financial account,(4) medical information, or(5) health insurance information.“Medical information” means any information, in either electronic or physical form,regarding an individual's medical history, mental or physical condition, or medicaltreatment or diagnosis by a health care pr<strong>of</strong>essional, and which may be in thepossession <strong>of</strong> or derived from a health care provider, health care service plan,pharmaceutical company or contractor. “Health insurance information” means anindividual's health insurance policy number or subscriber identification number, anyunique identifier used by a health insurer to identify the individual, or any information inan individual's application and claims history, including any appeals records. Medical1 <strong>of</strong> 5 <strong>UCLA</strong> Health<strong>Compliance</strong> Policies and ProceduresPrivacy and Information Security Policies


<strong>Remote</strong> <strong>Access</strong> Policy<strong>HS</strong> <strong>9453</strong>-Dinformation and health insurance information for patients are also considered to be PHI.“Restricted Information” (as defined by UC Policy IS-3, Electronic InformationSecurity) describes any confidential or Personal Information that is protected by law orpolicy and that requires the highest level <strong>of</strong> access control and security protection,whether in storage or in transit. This includes Personal Information, PHI and ePHI asdefined in this section but could also include other types <strong>of</strong> information such as researchdata.“Authorized Personnel” means the designated IT support person or group for an area.For hospital areas, this would be Medical Information Technology <strong>Services</strong> (MITS); fordepartments within the David Geffen School <strong>of</strong> Medicine at <strong>UCLA</strong> (“School <strong>of</strong>Medicine”), it would be the departmental Computer Support Coordinator (CSC); forareas supported by the School <strong>of</strong> Medicine IT <strong>Services</strong> (SOMITS), it would be SOMITS.“Device” refers to a networked device (e.g., PC, server, medical equipment).“MedNet” is the data network connecting the <strong>UCLA</strong> Medical Centers, the School <strong>of</strong>Medicine and the <strong>UCLA</strong> Community Physician Network.“Virtual Private Network” or “VPN” is a method to allow secure remote access acrossthe Internet by using encryption and other security mechanisms to ensure that onlyauthorized users can access the network and that data cannot be intercepted.“Workforce” means employees, volunteers, and other persons whose conduct, in theperformance <strong>of</strong> their work for <strong>UCLA</strong> Health, is under the direct control <strong>of</strong> <strong>UCLA</strong> Healthor the Regents <strong>of</strong> the University <strong>of</strong> California, whether or not <strong>UCLA</strong> Health pays them.The Workforce includes employees, medical staff, and other health care pr<strong>of</strong>essionals,agency, temporary and registry personnel, and trainees, housestaff, students andinterns, regardless <strong>of</strong> whether they are <strong>UCLA</strong> trainees or rotating through <strong>UCLA</strong> Healthfacilities from another institution.POLICYI. All remote access into <strong>UCLA</strong> Health networks across the Internet must useapproved VPN technology, and the remote access must be approved in advanceby the Department Authorizer.II.Devices that will be used for remote access that are not <strong>UCLA</strong> Health ownedequipment must be configured to comply with the provisions <strong>of</strong> this policy.2 <strong>of</strong> 5 <strong>UCLA</strong> Health<strong>Compliance</strong> Policies and ProceduresPrivacy and Information Security Policies


<strong>Remote</strong> <strong>Access</strong> Policy<strong>HS</strong> <strong>9453</strong>-DPROCEDUREI. <strong>Remote</strong> Use <strong>of</strong> <strong>UCLA</strong> Health Electronic Information ResourcesAll <strong>of</strong> the following requirements apply when connecting into MedNet from anexternal device:A. The only permitted remote access into MedNet is that which is directedthrough the MedNet VPN Concentrator, the MedNet SSL VPN client or theMedNet reverse proxy.i. Only approved Mednet VPN s<strong>of</strong>tware may be used.ii. Only approved Mednet VPN devices may be used and they mustbe installed by Authorized Personnel (for example, firewall/vpnboxes for remote locations).B. Individual VPN users must be authorized for VPN access by their homedepartments and must be registered. Possession <strong>of</strong> a VPN configurationfile (.PCF) does not confer authorization or permission for VPN access.Generic accounts (such as those assigned for classroom calendars) maynot be used for VPN access.C. Business-to-Business VPN connections from external third parties mustbe approved by the business owner <strong>of</strong> the application requiring remoteaccess and must comply with the MITS Business-to-Business VPN policy.D. <strong>Remote</strong> access users are responsible for selecting an Internet ServiceProvider (ISP), coordinating installation, installing any required s<strong>of</strong>tware,and paying any associated fees.E. It is the responsibility <strong>of</strong> individuals with these privileges to ensure thatunauthorized users are not allowed access to MedNet. This includesensuring that:i. At no time should any <strong>UCLA</strong> Health computer account user providehis/her login password to anyone, including family members.ii. Users may not redistribute any VPN configuration files (.PCFs) thathave been entrusted to them.F. VPN <strong>Access</strong> and Use.i. VPN users will be automatically disconnected from MedNet after 2hours <strong>of</strong> inactivity. The user must then logon again to reconnect tothe network. Pings or other artificial network processes are not tobe used to keep the connection open.3 <strong>of</strong> 5 <strong>UCLA</strong> Health<strong>Compliance</strong> Policies and ProceduresPrivacy and Information Security Policies


<strong>Remote</strong> <strong>Access</strong> Policyii.iii.iv.The maximum VPN concentrator session length is 15 hours.<strong>HS</strong> <strong>9453</strong>-DNo Device connected to MedNet via VPN is allowed to serve as aproxy to forward traffic from other devices.When using VPN technology with personal equipment, users mustunderstand that they must comply with all <strong>UCLA</strong> and <strong>UCLA</strong> Healthpolicies applicable to devices connected to <strong>UCLA</strong> networks.Requirements include, but are not limited toa. Operating systems must be kept up to date on patches.b. Anti-virus s<strong>of</strong>tware must be running and the virus definitionskept up to date.c. If there is a native host-based firewall, it must be enabled.d. Restricted Information must be encrypted.For more information, see the following policies:<strong>HS</strong> Policy No. 9421, “Workforce <strong>Access</strong> to and use <strong>of</strong> PHI(Minimum Necessary)”<strong>HS</strong> Policy No. 9451, “Use <strong>of</strong> Electronic Information”<strong>HS</strong> Policy No. <strong>9453</strong>-C, “Storage <strong>of</strong> Restricted Information onMobile Devices and Removable Media”<strong>HS</strong> Policy No. 9457, “Minimum Standards for NetworkDevices”<strong>UCLA</strong> Policy No. 401, “Minimum Standards for NetworkDevices”<strong>UCLA</strong> Policy No. 404, “Protection <strong>of</strong> Electronically StoredPersonal Information”II.III.IV.EnforcementFailure to follow any provisions <strong>of</strong> this policy may result in disciplinary action, upto and including termination.QuestionsWorkforce members should consult their IT support group or the InformationSecurity <strong>Office</strong> (InfoSecAll@mednet.ucla.edu) if they have any questions on thispolicy.Exceptions to PolicyAny exceptions to these policies must be for a valid patient care or businessreason and must be approved by the Information Security <strong>Office</strong>r working inconsultation with the appropriate IT groups prior to any remote access.4 <strong>of</strong> 5 <strong>UCLA</strong> Health<strong>Compliance</strong> Policies and ProceduresPrivacy and Information Security Policies


<strong>Remote</strong> <strong>Access</strong> Policy<strong>HS</strong> <strong>9453</strong>-DREFERENCESHealth Insurance Portability and Accountability Act, 45 CFR 160-164California Medical Information Act, California Civil Code Section 56 et seq.Information Practices Act <strong>of</strong> 1977, California Civil Code Sections 1798.29 and 1798.82California Health and Safety Code Sections 1280.15 and 130203University <strong>of</strong> California Business and Finance Bulletin IS-3, Electronic InformationSecurityUniversity <strong>of</strong> California Electronic Communications Policy (ECP)CONTACTChief Privacy <strong>Office</strong>r, <strong>Compliance</strong> <strong>Office</strong>Chief Information Security <strong>Office</strong>r, <strong>Compliance</strong> <strong>Office</strong>REVISION HISTORYApproved: February 22, 2006Effective Date: April 20, 2005Revised Date: November 2005; June 21, 2007; May 30, 2008, March 31, 2011APPROVALHealth Sciences Enterprise <strong>Compliance</strong> Oversight BoardApproved 12/11/2010David Feinberg, MDCEO and Associate Vice Chancellor<strong>UCLA</strong> Hospital SystemRandolph Steadman, MDChief <strong>of</strong> StaffRonald Reagan <strong>UCLA</strong> Medical CenterDenise Sur, MDChief <strong>of</strong> StaffSanta Monica-<strong>UCLA</strong> Medical Center and Orthopaedic hospitalJames J. McGough, MDChief <strong>of</strong> StaffResnick Neuropsychiatric Hospital at <strong>UCLA</strong>5 <strong>of</strong> 5 <strong>UCLA</strong> Health<strong>Compliance</strong> Policies and ProceduresPrivacy and Information Security Policies

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!