Imaging Security Requirements Sample Clauses

Imaging Security Requirements. 1. Contractor assumes responsibility for protecting County equipment and data assets and maintaining their integrity, confidentiality, and availability at all times. County may, at any time, conduct a formal walk-through of Contractor's facility to validate that Contractor's physical security meets the minimum standards for security as described herein. The County Information Security Officer (CISO) or designee may validate that Contractor’s security plan is being enforced and that all precautions are being taken to secure and protect County records. 2. Contractor agrees to maintain the confidentiality of all County and County-related records and information pursuant to all statutory laws relating to privacy and confidentiality that currently exist or exist at any time during the term of this Contract. All such records and information shall be considered 3. Contractor shall only use and disclose County data as permitted in this Contract and only use the data to perform an administrative function in direct support of the County. All other uses and disclosure of County data requires the express written approval from the County. Access to County data will be limited to those who require this access to perform their official duties in support of County business requirements. Contractors, who access, disclose, or use County data for a purpose not authorized in this agreement may be subject to civil and criminal prosecution. 4. Contractor will provide training for all employees who access County data to ensure compliance with this Contract prior to providing them with access to this data and annually thereafter. Documentation of training completion shall be retained for three (3) years after completion. 5. All Contractor employees must sign a confidentiality statement acknowledging understanding all information security related provisions in this contract prior to accessing County data and annually thereafter. Signed statements must be retained for a minimum of three (3) years. The statement shall include at a minimum: general use; security and privacy safeguards; unacceptable use; and enforcement policies. 6. All workstations, laptops, tablets or other communication devices which process or store County data must encrypt the data using a FIPS 140-2 256 bit or higher algorithm that is full disk. Servers that process or store County data must have sufficient administrative, physical and technical controls in place to protect that data based on a risk assessment a...
Sample 1
AutoNDA by SimpleDocs
Imaging Security Requirements. The California Department of Health Care Services (DHCS) has recently established security requirements pertaining to the use, access and disclosure of Medi-Cal Personally Identifiable Information (PII). Since Social Services Agency (SSA) case files contain this and other confidential welfare client information, these requirements must be adhered to by any Contractor (and subcontractor) staff who engages in case scanning for SSA. If these requirements change during the course of this engagement, SSA will notify and work with the Contractor to ensure compliance with the new requirements.  All Contractor staff that has access to this data during this work must read and sign SSA’s standard Welfare Client Information confidentiality statement.
Sample 1
Imaging Security Requirements. The California Department of Health Care Services (DHCS) has recently established security requirements pertaining to the use, access and disclosure of Medi-Cal Personally Identifiable Information (PII). Since Social Services Agency (SSA) case files contain this and other confidential welfare client information, these requirements must be adhered to by any Contractor (and subcontractor) staff who engages in case scanning for SSA. If these requirements change during the course of this engagement, SSA will notify and work with the Contractor to ensure compliance with the new requirements. Privacy and Confidentiality Statement: The California Department of Health Care Services (as well as Welfare and Institutions Code section 14100.2 and 42 Code of Federal Regulations section 431.300 et.seq.) requires that those who have access to Medi-Cal Personally Identifiable Information (PII) sign a confidentiality statement. 1. All Contractor staff that has access to this data during this work must read and sign SSA’s standard Welfare Client Information confidentiality statement.
Sample 1
Imaging Security Requirements. The California Department of Health Care Services (DHCS) has recently established security requirements pertaining to the use, access and disclosure of Medi-Cal Personally Identifiable Information (PII). Since Social Services Agency (SSA) case files contain this and other confidential welfare client information, these requirements must be adhered to by any Contractor (and subcontractor) staff who engages in case scanning for SSA. If these requirements change during the course of this engagement, SSA will notify and work with the Contractor to ensure compliance with the new requirements.
Sample 1

Related to Imaging Security Requirements

  • Security Requirements 7.1 The Authority will review the Contractor’s Security Plan when submitted by the Contractor in accordance with the Schedule (Security Requirements and Plan) and at least annually thereafter.

  • Data Security Requirements Without limiting Contractor’s obligation of confidentiality as further described in this Contract, Contractor must establish, maintain, and enforce a data privacy program and an information and cyber security program, including safety, physical, and technical security and resiliency policies and procedures, that comply with the requirements set forth in this Contract and, to the extent such programs are consistent with and not less protective than the requirements set forth in this Contract and are at least equal to applicable best industry practices and standards (NIST 800-53).

  • Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable. 2. Provide service site(s) that will promote attainment of Contractor’s program objectives. Arrange the physical environment to support those activities. 3. Decrease program costs when possible by procuring items at no cost from County surplus stores and by accepting delivery of such items by County.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • City Requirements Design, construction, materials, sizing, other specifications, permitting, inspections, testing, documentation and furnishing of as-built drawings, and acceptance of completed infrastructure shall be in accordance with City Requirements. Design and construction shall be by professionals licensed in the state of North Carolina to do the relevant work. City approval of the design of the Improvements shall be required prior to construction, as set forth in City Requirements. If Developer is connecting to the County sewer system, the City may require Developer to furnish the contract providing for such connection.

  • Safety Requirements The Contractor shall comply with all Federal, State, and local safety laws and regulations applicable to the Work performed under this Agreement.

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • Residency Requirements 1. All single first-year freshmen students are required to live in University housing for at least two academic semesters. All single students who have earned less than 30 credit hours and have not resided in University housing for two academic semesters are required to live on campus for two academic semesters. This policy does not apply to single first-year students who have been out of high school for more than one year, or to single first-year freshmen who live with their parents in Miami-Dade or Broward Counties. Neither does it apply to those students who, for disciplinary or administrative reasons, may be denied the privilege of continued residency on campus. 2. Undergraduate students residing in University housing must be regularly enrolled students of the University, taking a minimum of 12 credit hours each semester. Graduate students (when housed by exception) must carry a minimum of nine credit hours per semester. To apply and sign-up for University Village apartments, students must have 45 or more completed academic credits. In order to move into University Village, students must have 60 or more completed academic credits or have completed 4 academic semesters at the University and be achieving satisfactory academic progress as defined by the University Bulletin.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Business Day Requirements In the event that any notice or other action or omission is required to be taken by a Party under this Agreement on a day that is not a Business Day then such notice or other action or omission shall be deemed to be required to be taken on the next occurring Business Day.

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