Contract Security Requirements Sample Clauses

Contract Security Requirements. The Contractor shall abide by all contract cybersecurity requirements located in Sections H.6, H.7, Attachment J-2, and related federal policy, and other contract security requirements in Sections H.8
AutoNDA by SimpleDocs
Contract Security Requirements. 3.1 The highest level of security clearance required for this effort is CONFIDENTIAL. Therefore, a DD245 will be prepared and executed in support of the required performance.
Contract Security Requirements 

Related to Contract Security Requirements

  • Security Requirements 11.1 The Supplier shall comply, and shall procure the compliance of the Suppliers Personnel, with the Security Policy and the Security Plan and the Supplier shall ensure that the Security Plan produced by the Supplier fully complies with the Security Policy.

  • Payment Security Requirements A. Unless Company has maintained an agreement similar to this Agreement with Authority during the 18 months prior to the effective date of this Agreement without the occurrence of any act or omission that would have been a default under this Agreement, Company will provide Authority on or before the commencement date of this Agreement with an acceptable bond, irrevocable letter of credit or other similar security acceptable to Authority in an amount equal to the estimate of three months’ Rents, fees and charges, payable by Company under this Agreement, to guarantee the faithful performance by Company of its obligations under this Agreement and the payment of all Rents, fees, tax assessments, and charges due hereunder (hereinafter referred to as “Payment Security”). Company will be obligated to maintain such Payment Security in effect until the expiration of 18 consecutive months during which Company commits no default under this Agreement. Such Payment Security will be in a form and with a company acceptable to Authority and licensed to do business in the State of Florida. In the event that any such Payment Security is for a period less than the full period required under this Agreement or if such Payment Security is canceled, Company will provide a renewal or replacement Payment Security for the remaining required period at least 60 days prior to the date of such expiration or cancellation. Such Payment Security will require notice by the surety to Authority at least 60 days prior to any cancellation.

  • Information Security Requirements In cases where the State is not permitted to manage/modify the automation equipment (server/computer/other) that controls testing or monitoring devices, the Contractor agrees to update and provide patches for the automation equipment and any installed operating systems or applications on a quarterly basis (at minimum). The Contractor will submit a report to the State of updates installed within 30 days of the installation as well as a Plan of Actions and Milestones (POA&M) to remediate any vulnerabilities ranging from Critical to Low. The contractor will provide an upgrade path or compensatory security controls for any operating systems and applications listed as beyond “end-of-life” or EOL, within 90 days of the EOL and complete the EOL system’s upgrade within 90 days of the approved plan.

  • Data Security Requirements A. Data Transport. When transporting Confidential Information electronically, including via email, the data will be protected by:

  • Additional security requirements The following provisions apply in respect of any Additional Security provided:

  • Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable.

  • 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.

  • 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.

  • 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.

  • Quality Requirements Performance Indicator Heading Indicator (specific) Threshold Method of Measurement Frequency of monitoring Consequence of Breach QUALITY Patient Safety - Incidents I1 Number of incidents Adverse incidents include the following: clinical or non clinical adverse events that have potential to cause avoidable harm to a patient, including medical errors or adverse events related to medical devices or other equipment. Clinical or non- clinical accidents, accidental injuries to staff and members of the public, verbal, physical or psychological abuse or harassment, unusual or dangerous occurrences, damage to trust property, plant or equipment, fire or flood, security, theft or loss, near misses are identified as any event where under different circumstances significant injury or loss may have occurred Number of recorded incidents in the contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed I2 Number of Sis Definition of SUI according to trust policy and national guidance Number of Serious Untoward Incidents reported in contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed S1 Percentage of eligible staff received child safeguarding training at level 2 (as identified in LSCB training strategy) 95% Number received training/ Number of identified staff requiring training Monthly S2 Percentage of eligible staff received adult safeguarding awareness training at level 2 ( as identified in K&M Safeguarding Vulnerable Adults training strategy) 95% Number of staff trained/ Number of identified staff requiring training Monthly

Time is Money Join Law Insider Premium to draft better contracts faster.