My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
DDA and KCPHD Service Agreement
>
Meetings
>
2021
>
08. August
>
2021-08-03 10:00 AM - Commissioners' Agenda
>
DDA and KCPHD Service Agreement
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/5/2023 3:25:09 PM
Creation date
10/5/2023 3:24:46 PM
Metadata
Fields
Template:
Meeting
Date
8/3/2021
Meeting title
Commissioners' Agenda
Location
Commissioners' Auditorium
Address
205 West 5th Room 109 - Ellensburg
Meeting type
Regular
Meeting document type
Fully Executed Version
Supplemental fields
Item
Request to Approve County Program Agreement with the Department of Social and Health Services for DDA County Services
Order
11
Placement
Consent Agenda
Row ID
79309
Type
Agreement
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
28
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
6 <br />Special Terms and Gonditions <br />(3) lf the Data includes protected health information covered by the Health lnsurance Portability and <br />Accountability Act (HIPAA), the Cloud provider must sign a Business Associate Agreement prior <br />to Data being stored in their Cloud solution. <br />System Protection. To prevent compromise of systems which contain DSHS Data or through which <br />that Data passes: <br />a. Systems containing DSHS Data must have all security patches or hotfixes applied within 3 months <br />of being made available. <br />b. The Contractor will have a method of ensuring that the requisite patches and hotfixes have been <br />applied within the required timeframes. <br />c. Systems containing DSHS Data shall have an Anti-Malware application, if available, installed. <br />d. Anti-Malware software shall be kept up to date. The product, its anti-virus engine, and any malware <br />database the system uses, will be no more than one update behind current. <br />7. Data Segregation. <br />a. DSHS category 4 data must be segregated or otherwise distinguishable from non-DSHS data. This <br />is to ensure that when no longer needed by the Contractor, all DSHS Data can be identified for <br />return or destruction. lt also aids in determining whether DSHS Data has or may have been <br />compromised in the event of a security breach. As such, one or more of the following methods will <br />be used for data segregation <br />(1) DSHS Data will be kept on media (e.9. hard disk, optical disc, tape, etc.)which will contain no <br />non-DSHS Data. <br />(2) DSHS Data will be stored in a logical container on electronic media, such as a partition or folder <br />dedicated to DSHS Data. <br />(3) DSHS Data will be stored in a database which will contain no non-DSHS data. And/or, <br />(4) DSHS Data will be stored within a database and will be distinguishable from non-DSHS data by <br />the value of a specific field or fields within database records. <br />8. <br />DSHS Central Contract Services <br />1 769CS County Agreement 06-08-2021 <br />DSHS data in a drawer, folder, or other container. <br />b. When it is not feasible or practical to segregate DSHS Data from non-DSHS data, then both the <br />DSHS Data and the non-DSHS data with which it is commingled must be protected as described in <br />this exhibit. <br />Data Disposition. When the contracted work has been completed or when the Data is no longer <br />-^^l^,J a-^anl ^6 ^^+^'.t aharra in Qanlian tr h I'\ala chall ha rafu rrnar{ +n F)QIJQ, nr r{acf rnrrad l\/lar{iq nn <br />which Data may be stored and associated acceptable methods of destruction are as follows: <br />Data stored on:Will be destroyed by: <br />Server or workstation hard disks, or Using a "wipe" utility which will overwrite the Data at <br />least three (3) times using either random or single <br />character data, or <br />Page 24
The URL can be used to link to this page
Your browser does not support the video tag.