Spark security requirements Sample Clauses

Spark security requirements. Without limiting clause 20.1 Supplier must protect the Data against unauthorised access, use, modification, deletion or disclosure by: (a) implementing and maintaining an effective information security policy and management framework in accordance with Good Industry Practice, and including reasonable personnel, physical, system and data controls; (b) complying with all security standards relevant to the Deliverables (e.g. COBIT, ISO/IEC 27001, ISO/IEC 3100, PCI DSS, NZISM, SSAE 16); (c) providing appropriate specialist training for personnel involved in information security as relevant to the Deliverables (e.g. CISSP, CISM, PCI ISA, SANS GIAC); (d) creating and encouraging a proactive, security-centric culture that recognises the importance of people in protecting information and systems; (e) monitoring and following current globally-accepted security guidelines (e.g. OWASP Top Ten, SANS Critical Security Controls for Effective Cyber Defense, ASD Strategies to Mitigate Targeted Cyber Intrusions; (f) proactively and regularly testing services for security vulnerabilities, including remediating all findings that are critical, high severity or expose the service to unnecessary risk; and (h) complying with any other reasonable security requirements notified by Spark to Supplier from time to time.
AutoNDA by SimpleDocs

Related to Spark 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.

  • 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). Contractor also shall provide technical and organizational safeguards against accidental, unlawful, or unauthorized access or use, destruction, loss, alteration, disclosure, transfer, commingling, or processing of such information that ensure a level of security appropriate to the risks presented by the processing of County Data, Contractor personnel and/or subcontractor personnel and affiliates approved by County to perform work under this Contract may use or disclose County personal and confidential information only as permitted in this Contract. Any other use or disclosure requires express approval in writing by the County of Orange. No Contractor personnel and/or subcontractor personnel or affiliate shall duplicate, disseminate, market, sell, or disclose County personal and confidential information except as allowed in this Contract. Contractor personnel and/or subcontractor personnel or affiliate who access, disclose, market, sell, or use County personal and confidential information in a manner or for a purpose not authorized by this Contract may be subject to civil and criminal sanctions contained in applicable federal and state statutes. Contractor shall take all reasonable measures to secure and defend all locations, equipment, systems, and other materials and facilities employed in connection with the Services against hackers and others who may seek, without authorization, to disrupt, damage, modify, access, or otherwise use Contractor systems or the information found therein; and prevent County data from being commingled with or contaminated by the data of other customers or their users of the Services and unauthorized access to any of County data. Contractor shall also continuously monitor its systems for potential areas where security could be breached. In no case shall the safeguards of Contractor’s data privacy and information and cyber security program be less stringent than the safeguards used by County. Without limiting any other audit rights of County, County shall have the right to review Contractor’s data privacy and information and cyber security program prior to commencement of Services and from time to time during the term of this Contract. All data belongs to the County and shall be destroyed or returned at the end of the contract via digital wiping, degaussing, or physical shredding as directed by County.

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

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

  • Safety Requirements 17.1.1 The Concessionaire shall comply with the provisions of this Agreement, Applicable Laws and Applicable Permits and conform to Good Industry Practice for securing the safety of the Users. In particular, the Concessionaire shall develop, implement and administer a surveillance and safety programme for providing a safe environment on or about the Project, and shall comply with the safety requirements.

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