STATE OWNED DATA Sample Clauses

STATE OWNED DATA a. SUB-CONTRACTOR agrees to comply with the following requirements to ensure the preservation, security, and integrity of State-owned data on portable computing devices and portable electronic storage media: i. Encrypt all State-owned data stored on portable computing devices and portable electronic storage media using government-certified Advanced Encryption Standard (AES) cipher algorithm with a 256-bit or 128-bit encryption key to protect CALTRANS data stored on every sector of a hard drive, including temp files, cached data, hibernation files, and even unused disk space. ii. Data encryption shall use cryptographic technology that has been tested and approved against exacting standards, such as FIPS 140-2 Security Requirements for Cryptographic Modules. iii. Encrypt, as described above, all State-owned data transmitted from one computing device or storage medium to another. iv. Maintain confidentiality of all State-owned data by limiting data sharing to those individuals contracted to provide services on behalf of the State of California, and limit use of State of California information assets for State of California purposes only. v. Install and maintain current anti-virus software, security patches, and upgrades on all computing devices used during the course of the Contract.
AutoNDA by SimpleDocs
STATE OWNED DATA a. SUB-CONTRACTOR agrees to comply with the following requirements to ensure the preservation, security, and integrity of State-owned data on portable computing devices and portable electronic storage media: i. Encrypt all State-owned data stored on portable computing devices and portable electronic storage media using government-certified Advanced Encryption Standard (AES) cipher algorithm with a 256- bit or 128-bit encryption key to protect CALTRANS data stored on every sector of a hard drive, including temp files, cached data, hibernation files, and even unused disk space. ii. Data encryption shall use cryptographic technology that has been tested and approved against exacting standards, such as FIPS 140-2 Security Requirements for Cryptographic Modules. iii. Encrypt, as described above, all State-owned data transmitted from one computing device or storage medium to another. iv. Maintain confidentiality of all State-owned data by limiting data sharing to those individuals contracted to provide services on behalf of the State of California, and limit use of State of California information assets for State of California purposes only. v. Install and maintain current anti-virus software, security patches, and upgrades on all computing devices used during the course of the Contract. vi. Notify the Contract Manager immediately of any actual or attempted violations of security of State-owned data, including lost or stolen computing devices, files, or portable electronic storage media containing State-owned data. vii. Advise the owner of the State-owned data, the agency Information Security Officer, and the agency Chief Information Officer of vulnerabilities that may present a threat to the security of State- owned data and of specific means of protecting that State-owned data. b. To use the State-owned data only for State of California purposes under this Contract. c. To not transfer State-owned data to any computing system, mobile device, or desktop computer without first establishing the specifications for information integrity and security as established for the original data file(s). Reference State Administrative Manual (XXX) section 5335.1.
STATE OWNED DATA a. LOCAL AGENCY agrees to comply with the following requirements to ensure the preservation, security, and integrity of State-owned data on portable computing devices and portable electronic storage media: 1. Encrypt all State-owned data stored on portable computing devices and portable electronic storage media using government-certified Advanced Encryption Standard (AES) cipher algorithm with a 256-bit or 128-bit encryption key to protect CALTRANS data stored on every sector of a hard drive, including temp files, cached data, hibernation files, and even unused disk space. 2. Data encryption shall use cryptographic technology that has been tested and approved against exacting standards, such as FIPS 140-2 Security Requirements for Cryptographic Modules. 3. Encrypt, as described above, all State-owned data transmitted from one computing device or storage medium to another. 4. Maintain confidentiality of all State-owned data by limiting data sharing to those individuals contracted to provide services on behalf of the State, and limit use of State information assets for State purposes only. 5. Install and maintain current anti-virus software, security patches, and upgrades on all computing devices used during the course of the Agreement. 6. Notify the Contract Manager immediately of any actual or attempted violations of security of State-owned data, including lost or stolen computing devices, files, or portable electronic storage media containing State-owned data. 7. Advise the owner of the State-owned data, the agency Information Security Officer, and the agency Chief Information Officer of vulnerabilities that may present a threat to the security of State-owned data and of specific means of protecting that State- owned data. b. To use the State-owned data only for State purposes under this Agreement. c. To not transfer State-owned data to any computing system, mobile device, or desktop computer without first establishing the specifications for information integrity and security as established for the original data file(s). Reference State Administrative Manual (XXX) section 5335.
STATE OWNED DATA a. SUB-CONTRACTOR agrees to comply with the following requirements to ensure the preservation, security, and integrity of State-owned data on portable computing devices and portable electronic storage media: I. Encrypt all State-owned data stored on portable computing devices and portable electronic storage media using government-certified Advanced Encryption Standard (AES) cipher algorithm with a 256-bit or 128-bit encryption key to protect CALTRANS data stored on every sector of a hard drive, including temp files, cached data, hibernation files, and even unused disk space. II. Data encryption shall use cryptographic technology that has been tested and approved against exacting standards, such as FIPS 140-2 Security Requirements for Cryptographic Modules. III. Encrypt, as described above, all State-owned data transmitted from one computing device or storage medium to another. IV. Maintain confidentiality of all State-owned data by limiting data sharing to those individuals contracted to provide services on behalf of the State, and limit use of State information assets for State purposes only. V. Install and maintain current anti-virus software, security patches, and upgrades on all computing devices used during the course of the Contract.
STATE OWNED DATA. A. LOCAL AGENCY agrees to comply with the following requirements to ensure the preservation, security, and integrity of State-owned data on portable computing devices and portable electronic storage media: 1) Encrypt all State-owned data stored on portable computing devices and portable electronic storage media using government-certified Advanced Encryption Standard (AES) cipher algorithm with a 256-bit or 128-bit encryption key to protect CALTRANS data stored on every sector of a hard drive, including temp files, cached data, hibernation files, and even unused disk space. 2) Data encryption shall use cryptographic technology that has been tested and approved against exacting standards, such as FIPS 140-2 Security Requirements for Cryptographic Modules. 3) Encrypt, as described above, all State-owned data transmitted from one computing device or storage medium to another. 4) Maintain confidentiality of all State-owned data by limiting data sharing to those individuals contracted to provide services on behalf of the State, and limit use of State information assets for State purposes only. 5) Install and maintain current anti-virus software, security patches, and upgrades on all computing devices used during the course of the Agreement.
STATE OWNED DATA 

Related to STATE OWNED DATA

  • Real Estate Owned Reports Together with the statement furnished pursuant to Section 5.02, the Company shall furnish to the Purchaser on or before the Remittance Date each month a statement with respect to any REO Property covering the operation of such REO Property for the previous month and the Company's efforts in connection with the sale of such REO Property and any rental of such REO Property incidental to the sale thereof for the previous month. That statement shall be accompanied by such other information as the Purchaser shall reasonably request.

  • De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes: (1) assisting the LEA or other governmental agencies in conducting research and other studies; and (2) research and development of the Provider's educational sites, services, or applications, and to demonstrate the effectiveness of the Services; and (3) for adaptive learning purpose and for customized student learning. Provider's use of De-Identified Data shall survive termination of this DPA or any request by XXX to return or destroy Student Data. Except for Subprocessors, Xxxxxxxx agrees not to transfer de- identified Student Data to any party unless (a) that party agrees in writing not to attempt re-identification, and (b) prior written notice has been given to the LEA who has provided prior written consent for such transfer. Prior to publishing any document that names the LEA explicitly or indirectly, the Provider shall obtain the LEA’s written approval of the manner in which de-identified data is presented.

  • Covered Data All instances of "Student Data" should be replaced with "LEA Data". The protections provided within this DPA extend to all data provided to or collected by the Provider.

  • Categories of Data Subjects Any individual accessing and/or using the Services through the Customer's account ("Users"); and any individual: (i) whose email address is included in the Customer's Distribution List; (ii) whose information is stored on or collected via the Services, or (iii) to whom Users send emails or otherwise engage or communicate with via the Services (collectively, "Subscribers").

  • No Ownership Interest Nothing contained in this Agreement shall be deemed to vest in Parent any direct or indirect ownership or incidence of ownership of or with respect to the Covered Shares. All rights, ownership and economic benefits of and relating to the Covered Shares shall remain vested in and belong to the Stockholder, and Parent shall have no authority to direct the Stockholder in the voting or disposition of any of the Covered Shares, except as otherwise provided herein.

  • Categories of Data Subject 2.1. When using this Service, the groups of individual’s data by category • Your end users using the service that you deliver • The personal data about your employees and contractors that bookinglab collects as a Customer of ours to complete account administration and set up

  • Data Subject Rights (a) The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter. (b) The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required. (c) In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.

  • Rights of Data Subjects 5.1 You control access to Your Services environment that holds Personal Information about Your end users, and Your end users should direct any requests related to their rights under Applicable Data Protection Law to You. 5.2 To the extent such access is not available to You, Oracle will provide assistance with requests from individuals to access, delete or erase, restrict, rectify, receive and transmit, block access to or object to processing related to Personal Information held in Your Services environment on Oracle systems, insofar as reasonably and technically possible. 5.3 If Oracle directly receives any requests or inquiries from Your end users that have identified You as the Controller, it will promptly pass on such requests to You without responding to the end user.

  • Categories of Data Data relating to individuals provided to Google via the Services, by (or at the direction of) Customer or End Users. Data subjects include the individuals about whom data is provided to Google via the Services by (or at the direction of) Customer or End Users.

  • Source of Data A description of (1) the process used to identify claims in the Population, and (2) the specific documentation relied upon by the IRO when performing the Quarterly Claims Review (e.g., medical records, physician orders, certificates of medical necessity, requisition forms, local medical review policies (including title and policy number), CMS program memoranda (including title and issuance number), Medicare contractor manual or bulletins (including issue and date), other policies, regulations, or directives).‌‌‌

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!