Data Segregation a. DSHS Data must be segregated or otherwise distinguishable from non-DSHS data. This is to ensure that when no longer needed by the Contractor, all DSHS Data can be identified for return or destruction. It also aids in determining whether DSHS Data has or may have been compromised in the event of a security breach. As such, one or more of the following methods will be used for data segregation.
(1) DSHS Data will be kept on media (e.g. hard disk, optical disc, tape, etc.) which will contain no non-DSHS Data. And/or,
(2) DSHS Data will be stored in a logical container on electronic media, such as a partition or folder dedicated to DSHS Data. And/or,
(3) DSHS Data will be stored in a database which will contain no non-DSHS data. And/or,
(4) DSHS Data will be stored within a database and will be distinguishable from non-DSHS data by the value of a specific field or fields within database records.
(5) When stored as physical paper documents, DSHS Data will be physically segregated from non- DSHS data in a drawer, folder, or other container.
b. When it is not feasible or practical to segregate DSHS Data from non-DSHS data, then both the DSHS Data and the non-DSHS data with which it is commingled must be protected as described in this exhibit.
Data Segregation. 4.1 HCA’s Data received under this Contract must be segregated or otherwise distinguishable from non-HCA Data. This is to ensure that when no longer needed by the Contractor, all of HCA’s Data can be identified for return or destruction. It also aids in determining whether HCA’s Data has or may have been compromised in the event of a security breach. HCA’s Data must be kept in one of the following ways:
A. on media (e.g. hard disk, optical disc, tape, etc.) which will contain only HCA Data; or
B. in a logical container on electronic media, such as a partition or folder dedicated to HCA’s Data; or
C. in a database that will contain only HCA Data; or
D. within a database and will be distinguishable from non-HCA Data by the value of a specific field or fields within database records; or
E. when stored as physical paper documents, physically segregated from non-HCA Data in a drawer, folder, or other container.
4.2 When it is not feasible or practical to segregate HCA’s Data from non-HCA data, then both HCA’s Data and the non-HCA data with which it is commingled must be protected as described in this Attachment.
4.3 Contractor must designate and be able to identify all computing equipment on which they store, process, and maintain HCA Data. No Data at any time may be processed on or transferred to any portable storage medium. Laptop/tablet computing devices are not considered portable storage medium devices for purposes of this Contract provided it is installed with end-point encryption.
Data Segregation. The ISP will require that (i) Customer Data is stored in either physically or logically segregated databases from other BNYM data and (ii) different databases are maintained for development, testing, staging and production environments used in the provision of Services.
Data Segregation. Convercent will physically or logically separate and segregate Customer Data from its other clients’ data.
Data Segregation a. Data must be segregated or otherwise distinguishable from non-DCYF data. This is to ensure that when no longer needed by the Contractor, all Data can be identified for return or destruction. It also aids in determining whether Data has or may have been compromised in the event of a security breach. As such, one or more of the following methods will be used for data segregation:
(1) Data will be kept on media (e.g. hard disk, optical disc, tape, etc.) which will contain no non- DCYF Data; and/or;
Data Segregation. 1. County data must be segregated or otherwise distinguishable from non- County data. This is to ensure that when no longer needed by the Agency, all County data can be identified for return or destruction. It also aids in determining whether County data has or may have been compromised in the event of a security breach.
2. Electronic County data will be stored:
a. On media (e.g., hard disk, optical disc, tape, etc.) which will contain no non-County data; or
b. In a logical container on electronic media, such as a partition or folder dedicated to County data; or
c. In a database which will contain no non-County data; or
d. Within a database and will be distinguishable from non-County data by the value of a specific field or fields within database records;
3. When stored as physical paper documents, County data will be physically segregated from non-County data in a drawer, folder or other container.
4. When it is not feasible or practical to segregate County data from non- County data, then both the County data and the non-County data with which it is commingled must be protected as described in this Agreement.
Data Segregation a. Great Rivers Data must be segregated or otherwise distinguishable from non- Great Rivers data. This is to ensure that when no longer needed by the Contractor, all Great Rivers Data can be identified for return or destruction. It also aids in determining whether Great Rivers Data has or may have been compromised in the event of a security breach. As such, one or more of the following methods will be used for data segregation.
b. Great Rivers Data will be kept on media (e.g. hard disk, optical disc, tape, etc.) which will contain no non-Great Rivers data. And/or,
c. Great Rivers Data will be stored in a logical container on electronic media, such as a partition or folder dedicated to Great Rivers Data. And/or,
d. Great Rivers Data will be stored in a database which will contain no non- Great Rivers data. And/or,
e. Great Rivers Data will be stored within a database and will be distinguishable from non-Great Rivers data by the value of a specific field or fields within database records.
f. When stored as physical paper documents, Great Rivers Data will be physically segregated from non-Great Rivers data in a drawer, folder, or other container.
g. When it is not feasible or practical to segregate Great Rivers Data from non- Great Rivers data, then both the Great Rivers Data and the non-Great Rivers data with which it is commingled must be protected as described in this exhibit.
Data Segregation. 1. The data must be segregated or otherwise distinguishable from all other data. This is to ensure that when no longer needed by the Information Recipient, all of the data can be identified for return or destruction. It also aids in determining whether the data has or may have been compromised in the event of a security breach.
2. When it is not feasible or practical to segregate the data from other data, then all commingled data is protected as described in this Exhibit.
Data Segregation. Personal Data from different Oracle customers’ environments is logically segregated on Oracle’s systems.
Data Segregation. Genesys leverages a multi-tenant architecture logically separated at the database level, based on a user’s or organization’s Genesys account. Only authenticated parties are granted access to relevant accounts. New Genesys customers can use the Data Residency Option to choose whether their Content will be stored in Genesys’ on- premises United States or European data centers and third-party cloud providers’ United States, European and Indian regions hosted and replicated in separate regions to meet cross-border data privacy and residency requirements.
