Security and Malicious Code; PCI Compliance Sample Clauses

Security and Malicious Code; PCI Compliance a) Supplier will not cause or permit any viruses, malware, or similar items (“Malicious Code”) to be coded or introduced into Supplier systems or Buc-ee’s systems to which Supplier is given access and, if Malicious Code is introduced, Supplier will assist Buc-ee’s in reducing the effects of the Malicious Code, including restoring any loss of data, operational efficiency and mitigating any security risks;
Sample 1
AutoNDA by SimpleDocs

Related to Security and Malicious Code; PCI Compliance

  • Security and Safety A. The Contractor warrants it is and shall remain in compliance with all applicable local, state and federal laws, regulations, codes and ordinances relating to fire, construction, building, health, food service and safety, including but not limited to the Hotel and Motel Fire Safety Act of 1990, Public Law 101-391. The Judicial Council may terminate this Agreement, pursuant to the termination for cause provision set forth herein, without penalty or prejudice if the Contractor fails to comply with the foregoing requirements.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • COMPLIANCE WITH NEW YORK STATE INFORMATION SECURITY BREACH AND NOTIFICATION ACT Contractor shall comply with the provisions of the New York State Information Security Breach and Notification Act (General Business Law Section 899-aa; State Technology Law Section 208).

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.

  • COMPLIANCE WITH HEALTH, SAFETY, AND ENVIRONMENTAL REGULATIONS The Contractor, it’s Subcontractors, and their respective employees, shall comply fully with all applicable federal, state, and local health, safety, and environmental laws, ordinances, rules and regulations in the performance of the services, including but not limited to those promulgated by the City and by the Occupational Safety and Health Administration (OSHA). In case of conflict, the most stringent safety requirement shall govern. The Contractor shall indemnify and hold the City harmless from and against all claims, demands, suits, actions, judgments, fines, penalties and liability of every kind arising from the breach of the Contractor’s obligations under this paragraph.

  • Privacy Act If performance involves design, development or operation of a system of records on individuals, this Agreement incorporates by reference FAR 52.224-1 Privacy Act Notification (Apr 1984) and FAR 52.224-2 Privacy Act (Apr 1984).

  • Data Protection Act Compliance E2.1 The Contractor shall (and shall ensure that all of its Staff) comply with any notification requirements under the DPA and both Parties will duly observe all their obligations under the DPA which arise in connection with the Contract.

  • Anti-Boycott Verification To the extent this Agreement constitutes a contract for goods or services within the meaning of Section 2270.002 of the Texas Government Code, as amended, solely for purposes of compliance with Chapter 2270 of the Texas Government Code, and subject to applicable Federal law, the Developer represents that neither the Developer nor any wholly owned subsidiary, majority-owned subsidiary, parent company or affiliate of Developer (i) boycotts Israel or (ii) will boycott Israel through the term of this Agreement. The terms “boycotts Israel” and “boycott Israel” as used in this paragraph have the meanings assigned to the term “boycott Israel” in Section 808.001 of the Texas Government Code, as amended.

  • Security and Validation Procedures The Scheduling Coordinator shall apply to the Meter Data of the Scheduling Coordinator Metered Entities that it represents the security and validation procedures prescribed by the relevant Local Regulatory Authority. If the relevant Local Regulatory Authority has not prescribed any such procedures, the Scheduling Coordinator shall apply the procedures set forth in the CAISO Tariff. Meter Data submitted by a Scheduling Coordinator for Scheduling Coordinator Metered Entities shall conform to these standards unless the CAISO has, at its discretion, exempted the Scheduling Coordinator from these standards.

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