INFORMATION SECURITY PROGRAM REQUIREMENTS STANDARDS Sample Clauses

INFORMATION SECURITY PROGRAM REQUIREMENTS STANDARDS. Provider shall implement, and warrants that it will implement throughout the Term of the Agreement, a documented information security program that is based on one or more of the following industry standard information security frameworks (each an "Information Security Industry Standard"): (a) International Organization for Standardization ("ISO") / International Electrotechnical Commission ("IEC") ISO/IEC 27002 - Information technology – Security techniques – (b) American Institute of Certified Public Accountants (“AICPA”) Trust Services Principles, Criteria and Illustrations; or (c) Information Security Forum ("ISF") Standards of Good Practice ("SoGP") for Information Security; or (d) National Institute of Standards and Technology ("NIST") Special Publication 800-53 - (e) Information Systems Audit and Control Association ("ISACA") Control Objectives for Information and related Technology (COBIT).
Sample 1
AutoNDA by SimpleDocs
INFORMATION SECURITY PROGRAM REQUIREMENTS STANDARDS. Provider shall implement, and warrants that it will implement throughout the Term of the Agreement, a documented information security program that is based on one or more of the following industry standard information security frameworks (each an "Information Security Industry Standard"): (a) International Organization for Standardization ("ISO") / International Electrotechnical Commission ("IEC") ISO/IEC 27002 - Information technology – Security techniques – Code of practice for information security controls; or (b) American Institute of Certified Public Accountants (“AICPA”) Trust Services Principles, Criteria and Illustrations; or
Sample 1
INFORMATION SECURITY PROGRAM REQUIREMENTS STANDARDS. Each Party shall implement, and warrants that it will implement throughout the Term of the Agreement, a documented information security program that is based on one or more of the following industry standard information security frameworks (each an “Information Security Industry Standard”):
Sample 1
INFORMATION SECURITY PROGRAM REQUIREMENTS STANDARDS. Provider shall implement, and warrants that it will implement throughout the Term of the Agreement, a documented information security program that is based on one or more of the following industry standard information security frameworks (each an "Information Security Industry Standard"): 1. Standard dei requisiti del Programma relativo alla sicurezza delle informazioni. Il Fornitore implementa e garantisce che implementerà per tutta la durata dell’Accordo, un programma documentato relativo alla sicurezza delle informazioni che si basa su uno o più dei seguenti quadri di sicurezza delle informazioni standard del settore (ciascuno uno “Standard del settore della sicurezza delle informazioni”): (a) International Organization for Standardization ("ISO") / International Electrotechnical Commission ("IEC") ISO/IEC 27002 - Information technology – Security techniques – Code of practice for information security controls; or (a) Organizzazione internazionale per la normazione (“ISO”)/Commissione elettrotecnica internazionale (“IEC”): UNI CEI EN ISO IEC 27002 Tecnologie Informatiche - Tecniche di sicurezza - Codice di pratica per la gestione della sicurezza delle informazioni; (b) American Institute of Certified Public Accountants (“AICPA”) Trust Services Principles, Criteria and Illustrations; or (b) Istituto Americano dei Dottori Commercialisti e Revisori Contabili (“AICPA”): Principi, criteri e illustrazioni dei servizi fiduciari; (c) Information Security Forum ("ISF") Standards of Good Practice ("SoGP") for Information Security; or (c) Forum sulla sicurezza delle informazioni (“ISF”): Standard delle buone pratiche (“SoGP”) per la sicurezza delle informazioni; (d) National Institute of Standards and Technology ("NIST") Special Publication 800-53 - Security and Privacy Controls for Federal Information Systems and Organizations; or (d) National Institute of Standards and Technology (“NIST”): Pubblicazione speciale 800-53 - Controlli di sicurezza e privacy per i sistemi informativi e le organizzazioni federali; (e) Information Systems Audit and Control Association ("ISACA") Control Objectives for Information and related Technology (COBIT).
Sample 1

Related to INFORMATION SECURITY PROGRAM REQUIREMENTS STANDARDS

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

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.

  • Child Abuse Reporting Requirement Grantee will: a. comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. b. develop, implement and enforce a written policy that includes at a minimum the System Agency’s Child Abuse Screening, Documenting, and Reporting Policy for Grantees/Providers and train all staff on reporting requirements. c. use the System Agency Child Abuse Reporting Form located at xxxxx://xxx.xxxx.xxxxx.xx.xx/Contact Us/report abuse.asp as required by the System Agency. d. retain reporting documentation on site and make it available for inspection by the System Agency.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11164 et seq. and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.

  • Security Standards The Provider shall implement and maintain commercially reasonable security procedures and practices that otherwise meet or exceed industry standards designed to protect Student Data from unauthorized access, destruction, use, modification, or disclosure, including but not limited to the unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of the Student Data (a "Security Breach"). For purposes of the DPA and this Exhibit G, "Security Breach" does not include the good faith acquisition of Student Data by an employee or agent of the Provider or LEA for a legitimate educational or administrative purpose of the Provider or LEA, so long as the Student Data is used solely for purposes permitted by SOPPA and other applicable law, and so long as the Student Data is restricted from further unauthorized disclosure.

  • EDD Independent Contractor Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the state.” The term is further defined by the California Employment Development Department to refer specifically to independent Contractors. An independent Contractor is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm

  • Safety and Security Procedures Contractor shall maintain and enforce, at the Contractor Work Locations, industry-standard safety and physical security policies and procedures. While at each Court Work Location, Contractor shall comply with the safety and security policies and procedures in effect at such Court Work Location.

  • Safety Standards Performance of the Contract for all commodities or contractual services must comply with requirements of the Occupational Safety and Health Act and other applicable State of Florida and federal requirements.

  • Standards Compliance 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!