Information Assurance Vulnerability Alert Compliance Sample Clauses

Information Assurance Vulnerability Alert Compliance. The Contractor shall ensure compliance with all Information Assurance Vulnerability Alerts through the United States Computer Emergency Readiness Team
AutoNDA by SimpleDocs

Related to Information Assurance Vulnerability Alert Compliance

  • Privacy Compliance The Provider shall comply with all applicable federal, state, and local laws, rules, and regulations pertaining to Student Data privacy and security, all as may be amended from time to time.

  • HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.

  • Reporting Compliance The Company is subject to, and is in compliance in all material respects with, the reporting requirements of Section 13 and Section 15(d), as applicable, of the Exchange Act.

  • ERISA Information and Compliance The Obligors will promptly furnish and will cause the Subsidiaries and any ERISA Affiliate to promptly furnish to the Administrative Agent with sufficient copies to the Lenders (i) promptly after the filing thereof with the United States Secretary of Labor, the Internal Revenue Service or the PBGC, copies of each annual and other report with respect to each Plan or any trust created thereunder, (ii) immediately upon becoming aware of the occurrence of any ERISA Event or of any “prohibited transaction,” as described in section 406 of ERISA or in section 4975 of the Code, in connection with any Plan or any trust created thereunder, a written notice signed by a Responsible Officer specifying the nature thereof, what action the Obligors, the Subsidiary or the ERISA Affiliate is taking or proposes to take with respect thereto, and, when known, any action taken or proposed by the Internal Revenue Service, the Department of Labor or the PBGC with respect thereto, and (iii) immediately upon receipt thereof, copies of any notice of the PBGCs intention to terminate or to have a trustee appointed to administer any Plan. With respect to each Plan (other than a Multiemployer Plan), the Obligors will, and will cause each Subsidiary and ERISA Affiliate to, (i) satisfy in full and in a timely manner, without incurring any late payment or underpayment charge or penalty and without giving rise to any lien, all of the contribution and funding requirements of section 412 of the Code (determined without regard to subsections (d), (e), (f) and (k) thereof) and of section 302 of ERISA (determined without regard to sections 303, 304 and 306 of ERISA), and (ii) pay, or cause to be paid, to the PBGC in a timely manner, without incurring any late payment or underpayment charge or penalty, all premiums required pursuant to sections 4006 and 4007 of ERISA.

  • Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

  • Information for Regulatory Compliance Each of the Company and the Depositary shall provide to the other, as promptly as practicable, information from its records or otherwise available to it that is reasonably requested by the other to permit the other to comply with applicable law or requirements of governmental or regulatory authorities.

  • Financial Viability and Regulatory Compliance 2.6.1 Contractor warrants and represents that its corporate entity is in good standing with all applicable federal, state, and local licensing authorities and that it possesses all requisite licenses to perform the services required by this contract. Contractor further warrants and represents that it owes no outstanding delinquent federal, state or local taxes or business assessments. 2.6.2 Contractor agrees to promptly disclose to the MPHA any IRS liens or licensure suspension or revocation that may adversely affect its capacity to perform the services outlined within this contract. The failure by Contractor to disclose such issue to the MPHA in writing within 5 days of such notification received will constitute a material breach of this contract. 2.6.3 Contractor further agrees to promptly disclose to the MPHA any change of more than 50% of its ownership and/or any declaration of bankruptcy that Contractor may undergo during the term(s) of this contract. The failure of Contractor to disclose any change of more than 50% of its ownership and/or its declaration of bankruptcy within 5 days of said actions shall constitute a material breach of this contract. 2.6.4 All disclosures made pursuant to this section of the contract shall be made in writing and submitted to MPHA within the time periods required herein.

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

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!