Compliance with Security Rule; Security Incidents Sample Clauses

Compliance with Security Rule; Security Incidents. As set forth and more fully described in Section 7(a), Business Associate agrees to implement appropriate administrative, physical and technical safeguards to protect the confidentiality, integrity and availability of any of Covered Entity’s Electronic Protected Health Information that it creates, receives, maintains or transmits on behalf of Covered Entity. Business Associate shall: (x) report to Covered Entity any successful unauthorized access, use, disclosure, modification or destruction of Covered Entity’s Electronic Protected Health Information or interference with system operations in an information system containing Covered Entity’s Electronic Protected Health Information and (y) report the aggregate number of unsuccessful, unauthorized attempts to access, use, disclose, modify or destroy Covered Entity’s Electronic Protected Health Information or interfere with system operations in an information system containing Covered Entity’s Electronic Protected Health Information, provided that: (a) such reports will be provided only as frequently as the parties hereto mutually agree, but no more than once per month; and (b) if the definition ofSecurity Incident” under the Security Rule is amended to remove the requirement for reporting “unsuccessful” attempts to use, disclose, modify or destroy Covered Entity’s Electronic Protected Health Information, the portion of this Section 2 addressing the reporting of unsuccessful, unauthorized attempts to access, use, disclose, modify or destroy Covered Entity’s Electronic Protected Health Information will no longer apply as of the effective date of such amendment.
AutoNDA by SimpleDocs

Related to Compliance with Security Rule; Security Incidents

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

  • Compliance with ERISA (i) Each employee benefit plan, within the meaning of Section 3(3) of the Employee Retirement Income Security Act of 1974, as amended (“ERISA”), for which the Company or any member of its “Controlled Group” (defined as any organization which is a member of a controlled group of corporations within the meaning of Section 414 of the Internal Revenue Code of 1986, as amended (the “Code”)) would have any liability (each, a “Plan”) has been maintained in compliance with its terms and the requirements of any applicable statutes, orders, rules and regulations, including but not limited to ERISA and the Code, except for noncompliance that could not reasonably be expected to result in material liability to the Company or its subsidiaries; (ii) no prohibited transaction, within the meaning of Section 406 of ERISA or Section 4975 of the Code, has occurred with respect to any Plan excluding transactions effected pursuant to a statutory or administrative exemption that could reasonably be expected to result in a material liability to the Company or its subsidiaries; (iii) for each Plan that is subject to the funding rules of Section 412 of the Code or Section 302 of ERISA, the minimum funding standard of Section 412 of the Code or Section 302 of ERISA, as applicable, has been satisfied (without taking into account any waiver thereof or extension of any amortization period) and is reasonably expected to be satisfied in the future (without taking into account any waiver thereof or extension of any amortization period); (iv) the fair market value of the assets of each Plan exceeds the present value of all benefits accrued under such Plan (determined based on those assumptions used to fund such Plan); (v) no “reportable event” (within the meaning of Section 4043(c) of ERISA) has occurred or is reasonably expected to occur that either has resulted, or could reasonably be expected to result, in material liability to the Company or its subsidiaries; (vi) neither the Company nor any member of the Controlled Group has incurred, nor reasonably expects to incur, any liability under Title IV of ERISA (other than contributions to the Plan or premiums to the PBGC, in the ordinary course and without default) in respect of a Plan (including a “multiemployer plan”, within the meaning of Section 4001(a)(3) of ERISA); and (vii) there is no pending audit or investigation by the Internal Revenue Service, the U.S. Department of Labor, the Pension Benefit Guaranty Corporation or any other governmental agency or any foreign regulatory agency with respect to any Plan that could reasonably be expected to result in material liability to the Company or its subsidiaries. None of the following events has occurred or is reasonably likely to occur: (x) a material increase in the aggregate amount of contributions required to be made to all Plans by the Company or its subsidiaries in the current fiscal year of the Company and its subsidiaries compared to the amount of such contributions made in the Company and its subsidiaries’ most recently completed fiscal year; or (y) a material increase in the Company and its subsidiaries’ “accumulated post-retirement benefit obligations” (within the meaning of Statement of Financial Accounting Standards 106) compared to the amount of such obligations in the Company and its subsidiaries’ most recently completed fiscal year.

  • Compliance with Non-Discrimination Requirements During the performance of this Agreement, Company, for itself, its assignees, successors in interest, subcontractors and consultants agrees as follows:

  • Compliance with Nondiscrimination Requirements During the performance of this contract, the Contractor, for itself, its assignees, and successors in interest (hereinafter referred to as the “Contractor”), agrees as follows:

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