CJIS Compliance Sample Clauses

CJIS Compliance. This Agreement incorporates by reference the requirements of the Criminal Justice Information Services (CJIS) Security Policy, and as referenced in Title 28 CFR 20.33.(a)(7), issued by the Federal Bureau of Investigation, Criminal Justice Information Services Division, as in force as of the date of this Agreement and as may, from time to time hereafter, be amended. Company covenants that it has the technological capability to handle Criminal Justice Information (CJI), as that term is defined by the FBI CJIS Security Policy, in the manner required by the CJIS Security Policy. Contractor expressly acknowledges that the CJIS Security Policy places restrictions and limitations on the access to, use of, and dissemination of CJI and hereby covenants that its system will abide by those restrictions and limitations.
AutoNDA by SimpleDocs
CJIS Compliance. Contractor represents and warrants that Contractor shall exercise commercially reasonable efforts to comply with the Criminal Justice Information Services Security Policy for Purchasers that collect, process, store, and/or share CJIS data.
CJIS Compliance. Customer is responsible for its own adherence to the FBI Criminal Justice Information Services (CJIS) Security Policy, the Health Insurance Portability and Accountability Act of 1996 (HIPAA) (to the extent applicable) and any other applicable security and privacy laws and regulations. Motorola will reasonably cooperate with Customer in connection therewith. Section 6: SAA and Support Contact Requirements
CJIS Compliance. Please provide a statement that confirms the Vendor shall provide an ALPR System that shall adhere to all guidelines set forth by the Criminal Justice Information Services (“CJIS”) Agency. These guidelines were established by the U.S. Department of Justice, Federal Bureau of Investigation and can be found utilizing the following link: xxxxx://xxx.xxx.xxx/services/cjis/cjis-security-policy-resource-center. This shall include all data in transit and at rest.
CJIS Compliance. This agreement incorporates by reference the requirements of the most current version of the Criminal Justice Information Services Security Policy (see “Appendix H”) issued by the Federal Bureau of Investigation, Criminal Justice Information Services Division, as in force as of the date of this Agreement and as may, from time to time hereafter, be amended. CrossWind Technologies, Inc. warrants that it has the technological capability to handle Criminal Justice Information, as that term is defined by the CJIS Policy, in the manner required by the Policy. Agency shall ensure, and hereby warrants, that it and all persons it authorizes to access or use the Services or Law Enforcement Data will comply with the Policy, maintain the confidentiality and integrity of the Law Enforcement Data, and will not take any steps to access, interfere with, jeopardize the confidentiality or integrity of the Valcour services.
CJIS Compliance. Xxxxxxxxx maintains policies and procedures for securely storing, handling, and transmitting data. By default, Peregrine encrypts all data both in transit and at rest in accordance with CJIS standards. The Peregrine system adheres to FIPS 140-2 cryptographic standards along with all the underlying cryptographic modules as mandated by the AWS government cloud platform. Encryption key management uses FIPS 140-2 security modules with 256-bit strength and follows password policies outlined in the CJIS security policy. The Peregrine system isolates boundaries using techniques such as security groups, policies, access controls, network firewalls, ACLs, intrusion systems, and IPSec within its virtual private cloud (VPC). Monitoring and controls are in place to ensure that any connections or data transmissions are through authorized mediums. Public and private networks are allocated to ensure that unauthorized access is restricted. The cloud infrastructure uses server-side encryption for both blob and block storage to provide an additional layer of protection.

Related to CJIS Compliance

  • PCI-DSS Compliance As applicable, Customer is responsible for ensuring that its use of the Cloud Service to store or process credit card data complies with applicable Payment Card Industry Data Security Standards (“PCI DSS”) requirements and shall not store credit card and social security data in the Cloud Service except in the designated encrypted fields for such data. During the Term, Oracle shall maintain PCI DSS compliance for those portions of the Cloud Service that are designated by Oracle as being designed to store and process credit card data. Any changes made to the Cloud Service by the Customer or at the Customer’s direction may affect the Customer’s compliance with PCI DSS requirements and Customer shall be solely responsible for ensuring that any such changes are compliant with PCI DSS requirements.

  • ETHICS COMPLIANCE All Bidders/Contractors and their employees must comply with the requirements of Sections 73 and 74 of the Public Officers Law, other State codes, rules, regulations and executive orders establishing ethical standards for the conduct of business with New York State. In signing the Bid, Bidder certifies full compliance with those provisions for any present or future dealings, transactions, sales, contracts, services, offers, relationships, etc., involving New York State and/or its employees. Failure to comply with those provisions may result in disqualification from the Bidding process, termination of contract, and/or other civil or criminal proceedings as required by law.

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.

  • Law Compliance In providing the SOLID WASTE HANDLING SERVICES required by this AGREEMENT, CONTRACTOR shall observe and comply with all applicable federal and, state laws, regulations and codes regarding the provision of the SOLID WASTE HANDLING SERVICES described herein, as such may be amended from time to time, including where required by such laws, the funding and maintenance of sufficient closure and post-closure maintenance financial assurances for any landfill operated or utilized by CONTRACTOR for disposal of the SOLID WASTE. Any violation of this Paragraph shall constitute a major breach.

  • HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

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