Implementation of Security Standards; Notice of Security Incidents Sample Clauses

Implementation of Security Standards; Notice of Security Incidents. Business Associate will use appropriate safeguards to prevent the use or disclosure of PHI other than as expressly permitted under this Agreement. Business Associate will implement administrative, physical and technical safeguards that reasonably and appropriately protect the confidentiality, integrity and availability of the PHI that it creates, receives, maintains or transmits on behalf of Covered Entity. Business Associate acknowledges that the HITECH Act requires Business Associate to comply with 45 C.F.R. §§164.308, 164.310, 164.312 and 164.316 as if Business Associate were a Covered Entity, and Business Associate agrees to comply with these provisions of the Security Standards and all additional security provisions of the HITECH Act. Furthermore, to the extent feasible, Business Associate will use commercially reasonable efforts to secure PHI through technology safeguards that render such PHI unusable, unreadable and indecipherable to individuals unauthorized to acquire or otherwise have access to such PHI in accordance with HHS Guidance published at 74 Federal Register 19006 (April 17, 2009), or such later regulations or guidance promulgated by HHS or issued by the National Institute for Standards and Technology (“NIST’) concerning the protection of identifiable data such as PHI. Lastly, Business Associate will promptly report to Covered Entity any successful Security Incident of which it becomes aware. At the request of Covered Entity, Business Associate shall identify: the date of the Security Incident, the scope of the Security Incident, Business Associate’s response to the Security Incident and the identification of the party responsible for causing the Security Incident, if known.
Sample 1Sample 2Sample 3See All (19)
AutoNDA by SimpleDocs
Implementation of Security Standards; Notice of Security Incidents. Business Associate will use appropriate safeguards to prevent the use or disclosure of PHI other than as expressly permitted under this Agreement. Business Associate will implement administrative, physical and technical safeguards that reasonably and appropriately protect the confidentiality, integrity and availability of the PHI that it creates, receives, maintains or transmits on behalf of Covered Entity. Business Associate acknowledges that the HITECH Act requires Business Associate to comply with 45 C.F.R. §§ 164.308, 164.310, 164.312, 164.314, and 164.316 as if Business Associate were a Covered Entity, and Business Associate agrees to comply with these provisions of the Security Standards and all additional security provisions of the HITECH Act. Furthermore, to the extent feasible, Business Associate will use commercially reasonable efforts to ensure that the technology safeguards used by Business Associate to secure PHI will render such PHI unusable, unreadable and indecipherable to individuals unauthorized to acquire or otherwise have access to such PHI in accordance with HHS Guidance published at 74 Federal Register 19006 (April 17, 2009), or such later regulations or guidance promulgated by HHS or issued by the National Institute for Standards and Technology (“NIST”) concerning the protection of identifiable data such as PHI. Business Associate acknowledges and agrees that the HIPAA Omnibus Rule finalized January 25, 2013 at 78 Fed. Reg. 5566 requires Business Associate to comply with new and modified obligations imposed by that rule under 45 C.F.R. §164.306, 45 C.F.R. § 164.308, 45 C.F.R. § 163.310, 45 C.F.R. § 164.312, 45 C.F.R. § 164.316, 45 C.F.R. § 164.502, 45 C.F.R. § 164.504. Lastly, Business Associate will promptly report to Covered Entity any successful Security Incident of which it becomes aware. At the request of Covered Entity, Business Associate shall identify: the date of the Security Incident, the scope of the Security Incident, the Business Associate’s response to the Security Incident and the identification of the party responsible for causing the Security Incident, if known. Business Associate and Covered Entity shall take reasonable measures to ensure the availability of all affirmative defenses under the HITECH Act, HIPAA, and other state and federal laws and regulations governing PHI and EPHI.
Sample 1Sample 2Sample 3See All (10)
Implementation of Security Standards; Notice of Security Incidents. BA will use appropriate safeguards to prevent the use or disclosure of PHI other than as expressly permitted under this BAA. BA will implement administrative, physical and technical safeguards that reasonably and appropriately protect the confidentiality, integrity and availability of the PHI that it creates, receives, maintains or transmits on behalf of CE. BA acknowledges BA shall comply with 45 C.F.R. §§164.308, 164.310, 164.312 and 164.316, as if BA were a CE. To the extent feasible, BA will use commercially reasonable efforts to secure PHI through technology safeguards that render such PHI unusable, unreadable and indecipherable to individuals unauthorized to acquire or otherwise have access to such PHI. BA will promptly report to CE any successful Security Incident of which it becomes aware. At the request of CE, BA shall identify: the date of the Security Incident, the scope of the Security Incident, BA’s response to the Security Incident, and the identification of the party responsible for causing the Security Incident, if known.
Sample 1
Implementation of Security Standards; Notice of Security Incidents. Subcontractor will comply with the Security Standards and, by way of example and not limitation, use appropriate safeguards to prevent the use or disclosure of PHI other than as expressly permitted under this Agreement. In accordance with the Security Standards, Subcontractor will implement administrative, physical, and technical safeguards that protect the confidentiality, integrity and availability of the PHI that it uses, discloses, accesses, creates, receives, maintains or transmits. To the extent feasible, Subcontractor will use commercially reasonable efforts to ensure that the technology safeguards used by Subcontractor to secure PHI will render such PHI unusable, unreadable and indecipherable to individuals unauthorized to acquire or otherwise have access to such PHI in accordance with HHS Guidance published at 74 Federal Register 19006 (April 17, 2009) or such later regulations or guidance promulgated by HHS or issued by the National Institute for Standards and Technology (“NIST”) concerning the protection of identifiable data such as PHI. Subcontractor will promptly report to TokenEx any Security Incident of which it becomes aware; provided, however, that TokenEx acknowledges and shall be deemed to have received notice from Subcontractor that there are routine occurrences of: (i) unsuccessful attempts to penetrate computer networks or services maintained by Subcontractor; and (ii) immaterial incidents such as “pinging” or “denial of services” attacks. At the request of TokenEx, Subcontractor shall identify: the date of the Security Incident, the scope of the Security Incident, Subcontractor’s response to the Security Incident, and to the extent permitted by law, the identification of the party responsible for causing the Security Incident, if known.
Sample 1
Implementation of Security Standards; Notice of Security Incidents. In compliance with the applicable Confidentiality Requirements, Business Associate will use appropriate safeguards to prevent the use or disclosure of PHI other than as permitted under this Exhibit. Business Associate will implement administrative, physical and technical safeguards that reasonably and appropriately protect the confidentiality, integrity and availability of the PHI that it uses, discloses, creates, receives, maintains or transmits on behalf of Covered Entity. Business Associate will promptly report to Covered Entity any Security Incident of which it becomes aware; provided, however, that Covered Entity acknowledges and shall be deemed to have received notice from Business Associate that there are routine occurrences of: (i) unsuccessful attempts to penetrate computer networks or services maintained by Business Associate; and (ii) immaterial incidents such as “pinging” or “denial of services” attacks.
Sample 1

Related to Implementation of Security Standards; Notice of Security Incidents

  • Creation of Security (a) Notwithstanding the foregoing, for the purpose of financing the Facility, the Company may assign to, or grant a security interest in favor of, the Lenders in its rights and interests under or pursuant to: (i) this Agreement, (ii) any agreement or document included in the Security Package, (iii) the Facility, (iv) the movable, immovable and intellectual property of the Company, and (vi) the revenues or any of the rights or assets of the Company. The Company shall not create any security over its rights and interests under this Agreement without the prior written consent of the GOB except as already provided above.

  • Protection of Security Each Grantor shall, at its own cost and expense, take any and all actions necessary to defend title to the Collateral against all persons and to defend the Security Interest of the Collateral Agent in the Collateral and the priority thereof against any Lien not expressly permitted pursuant to Section 6.02 of the Credit Agreement.

  • Release of Security (a) If a disposal of any asset subject to security created by a Security Document is made in the following circumstances:

  • Impairment of Security, etc Any Loan Document, or any Lien granted thereunder, shall (except in accordance with its terms or pursuant to Section 7.2.9), in whole or in part, terminate, cease to be effective or cease to be the legally valid, binding and enforceable obligation of any Credit Party thereto; any Credit Party or any other party shall, directly or indirectly, contest in any manner the effectiveness, validity, binding nature or enforceability of any Loan Document or Lien granted thereunder; or any Lien securing any Obligation shall, in whole or in part, cease to be a perfected first priority Lien, subject only to those exceptions expressly permitted by such Loan Document.

  • Provision of Security At least thirty (30) Calendar Days prior to the commencement of the procurement, installation, or construction of a discrete portion of a Connecting Transmission Owner’s Attachment Facilities, Developer shall provide Connecting Transmission Owner, at Developer’s option, a guarantee, a surety bond, letter of credit or other form of security that is reasonably acceptable to Connecting Transmission Owner and is consistent with the Uniform Commercial Code of the jurisdiction identified in Article 14.2.1 of this Agreement. Such security for payment shall be in an amount sufficient to cover the cost for the Developer’s share of constructing, procuring and installing the applicable portion of Connecting Transmission Owner’s Attachment Facilities, and shall be reduced on a dollar-for-dollar basis for payments made to Connecting Transmission Owner for these purposes. In addition:

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