Ongoing Security Testing Sample Clauses

The Ongoing Security Testing clause requires that regular assessments of a system's security are conducted throughout the duration of an agreement or project. This typically involves periodic vulnerability scans, penetration testing, or other security evaluations to identify and address potential weaknesses as they arise. By mandating continuous security checks, the clause helps ensure that security standards are maintained over time and that emerging threats are promptly managed, thereby reducing the risk of data breaches or system compromise.
Ongoing Security Testing. Vendor will periodically test its systems for potential areas where security could be breached. During the term, to the extent Vendor engages a Third Party auditor to perform an SSAE 16 of Vendor’s operations, information security program, and/or disaster recovery/business continuity plan, Vendor shall promptly furnish a copy of the test report or audit report to OCIO. In addition, Vendor shall disclose its non-proprietary security processes and technical limitations to OCIO to enable OCIO to identify compensating controls necessary to adequately safeguard and protect Customer Data. For example, Vendor shall disclose its security processes with respect to virus checking and port sniffing to OCIO.
View SourceView Similar (4)
Ongoing Security Testing. Vendor will periodically test its systems for potential areas where security could be breached. During the term, to the extent Vendor engages a Third Party auditor to perform an SSAE 16 of Vendor’s operations, information security program, and/or disaster recovery/business continuity plan, Vendor shall promptly furnish a copy of the test report or audit report to OCIO or its Authorized Contractors. In addition, Vendor shall disclose its non- proprietary security processes and technical limitations to OCIO or its Authorized Contractors to enable OCIO to identify compensating controls necessary to adequately safeguard and protect Customer Data, or to otherwise assist OCIO or any other Governmental Entity in complying with any laws, rules, regulations, orders, or corresponding audits. For example, Vendor shall disclose its security processes with respect to virus checking and port sniffing to OCIO.
View SourceView Similar (2)
Ongoing Security Testing. Vendor will periodically test its systems for potential areas where security could be breached. During the Term, to the extent Vendor engages a Third Party auditor to perform an SSAE 16 of Vendor’s operations, information security program, and/or disaster recovery/business continuity plan, Vendor shall promptly furnish a copy of the test report or audit report to the State or Governmental Entity. In addition, Vendor shall disclose its non-proprietary security processes and technical limitations to the State or Governmental Entity to enable the State or Governmental Entity to identify compensating controls necessary to adequately safeguard and protect Customer Data. For example, Vendor shall disclose its security processes with respect to virus checking and port sniffing to the State or Governmental Entity.
View Source
Ongoing Security Testing. Vendor will periodically test its systems for potential areas where security could be breached. In addition, Vendor shall disclose its non-proprietary security processes and technical limitations to OCIO to enable OCIO to identify compensating controls necessary to adequately safeguard and protect Customer Data. For example, Vendor shall disclose its security processes with respect to virus checking and port sniffing to OCIO.
View Source

Related to Ongoing Security Testing

  • Stability Testing Patheon will conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within [***], after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications and cGMPs. Patheon will give Client all stability test data and results at Client’s request.

  • Performance Testing (a) All performance tests of the Project, including any Initial Performance Test required in Section 2 of Appendix VIII, will be performed in accordance with the test procedures set forth in Appendix VIII (“Performance Test”), including additional procedures and protocols related to Performance Testing as mutually agreed between Buyer and Seller (“Test Procedures”). Seller shall bear all costs and receive all revenues, if applicable, associated with all Performance Tests. (b) After the Initial Delivery Date and during the Delivery Term, Buyer will have the right to conduct a Performance Test (“Buyer Performance Test”) no more than once a calendar year to demonstrate whether the Project is capable of delivering the Distribution Services at the Contract Capacity. Within 30 calendar days following a Buyer Performance Test, Seller will have the right to retest the Project with a Performance Test (“Seller Retest”). For the avoidance of doubt, the results of any Seller Retest will supersede the results of the preceding Buyer Performance Test. (i) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at or above ninety-nine percent (99%) of the Initial Contract Capacity, the Contract Capacity will remain the Initial Contract Capacity; (ii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at more than or equal to eighty-five (85%) of the Initial Contract Capacity, but less than ninety-nine percent (99%) of the Initial Contract Capacity (“Testing Band”), the Contract Capacity will be automatically adjusted (upwards or downwards) to the capacity commensurate with the amount of Distribution Services the Project delivered during the Performance Test within the Testing Band. (iii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is not capable of delivering Distribution Services of at least eighty-five percent (85%) of the Initial Contract Capacity, an Event of Default shall occur in accordance with Section 7.1(a)(viii).

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.