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 (22)
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. 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
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 (Company Name). (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 (Company Name), and (Business Associate) agrees to comply with these provisions of the Security Standards and all additional security provisions of the HITECH Act.
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. Vendor 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, Vendor 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, Vendor will use commercially reasonable efforts to ensure that the technology safeguards used by Vendor to secure PHI will render such PHI unusable, unreadable and indecipherable to individuals unauthorized to acquire or otherwise have access to such PHI. Vendor 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 Vendor that there are routine occurrences of: (i) unsuccessful attempts to penetrate computer networks or services maintained by Vendor; and
Sample 1
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
AutoNDA by SimpleDocs

Related to Implementation of Security Standards; Notice of Security Incidents

  • Confirmation of Security Borrower hereby confirms and agrees that all of the Security Instruments, as may be amended in accordance herewith, which presently secure the Indebtedness shall continue to secure, in the same manner and to the same extent provided therein, the payment and performance of the Indebtedness as described in the Credit Agreement as modified by this Amendment.

  • Perfection of Security Each Obligor shall have duly authorized, executed, acknowledged, delivered, filed, registered and recorded such security agreements, notices, financing statements, memoranda of intellectual property security interests and other instruments as the Agent may have reasonably requested in order to perfect the Liens purported or required pursuant to the Credit Documents to be created in the Credit Security and shall have paid all filing or recording fees or taxes required to be paid in connection therewith, including any recording, mortgage, documentary, transfer or intangible taxes.

  • 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. (b) The Lenders shall have no obligation to the GOB under this Agreement until such time as the Lenders or their designees succeed to the Company’s interest under this Agreement, whether by exercise of their rights or remedies under the Financing Documents or otherwise, in which case the Lenders or their designees shall give written notice of such succession (a “Succession Notice”) to the GOB and assume liability for all of the Company’s obligations under this Agreement, including without limitation payment of any amounts due and owing to the GOB for payment defaults by the Company under this Agreement (other than, so long as the liability insurance required by Section 6.5 has been and is in effect), damages or penalties incurred by the Company under Section 6.2(b), arising during the period prior to the Lenders’ or such designees’ succession to the Company’s interest in and under this Agreement, provided that any liability of the Lenders or their designees shall be strictly limited to the Lenders’ interest in the Facility. Except as otherwise set forth in the immediately preceding sentence, none of the Lenders or their designees shall be liable for the performance or observance of any of the obligations or duties of the Company under this Agreement, nor shall the assignment by the Company of this Agreement to the Lenders give rise to any duties or obligations whatsoever on the part of any of the Lenders owing to the GOB. Upon notification by the Lenders or the Agent to the GOB of the occurrence and continuance of an event of default under the Financing Documents and the succession of the Lenders to the Company’s interests in and under this Agreement, the Lenders shall have the right, among others, to: (i) take possession of the Facility and, prior to the Commercial Operations Date, complete construction of the Facility and operate the same and, after the Commercial Operations Date, operate the same; and (ii) cure any continuing Company Event of Default under this Agreement as provided in Section 13.5. Notwithstanding the foregoing, upon the delivery of a Succession Notice, the Lenders shall have no obligation to cure any Company Event of Default occurring before the delivery of such Succession Notice that is not capable of being cured and no right will exist for the GOB to terminate this Agreement based upon such Company Events of Default occurring prior to the delivery of the Lenders’ Succession Notice. Without the requirement of obtaining any further consent from the GOB, upon the exercise by the Lenders or their designees of any of the remedies set forth in the Financing Documents, the Lenders may assign their rights and interests and the rights of the Company under this Agreement to a Transferee acceptable to the GOB so long as such Transferee shall assume all of the obligations of the Company under this Agreement. Upon such assignment and assumption, the Lenders shall be relieved of all obligations under this Agreement arising after such assignment and assumptions. (c) As used herein, a “Transferee” shall be a person who (i) is a company organized under the Laws of Bangladesh, (ii) either is an experienced and qualified power plant operator or who shall have agreed to engage the services of a person who is an experienced and qualified power plant operator, (iii) shall have paid all amounts, if any, then due and payable to the GOB under this Agreement, and (iv) shall have expressly assumed in writing for the benefit of the GOB the ongoing obligations of the Company under this Agreement (including the obligation of the Company to maintain and operate the Facility in accordance with the requirements of this Agreement). (d) At the request of the Company, delivered to the GOB not less than 30 (thirty) Days in advance, the GOB shall execute and deliver at the Financial Closing, all such acknowledgements to the Lenders or their designees of any security created in accordance with this Section 9 as are reasonably requested by the Company and the Lenders to give effect to the foregoing.

  • Principle of Security The Board and the Association agree that increased length of service in the employment of the Board entitles all employees covered by this Agreement to commensurate increase in security of teaching employment, provided that they possess the qualifications necessary for the positions available.

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

  • Preservation of Security 6.1. It is hereby agreed and declared that: 6.1.1. the security created by this Charge shall be held by the Chargee as a continuing security for the payment and discharge of the Secured Obligations and the security so created shall not be satisfied by any intermediate payment or satisfaction of any part of the Secured Obligations; 6.1.2. the security created by this Charge is in addition to and independent of and shall not prejudice or merge with any other security (or any right of set-off) which the Chargee may hold at any time for the Secured Obligations or any of them; 6.1.3. the Chargee shall not be bound to seek to recover any amounts due from the Chargor or any other person, exercise any rights against the Chargor or any other person or enforce any other security before enforcing the security created by this Charge; 6.1.4. no delay or omission on the part of the Chargee in exercising any right, power or remedy under this Charge shall impair such right, power or remedy or be construed as a waiver thereof nor shall any single or partial exercise of any such right, power or remedy preclude any further exercise thereof or the exercise of any other right, power or remedy. The rights, powers and remedies herein provided are cumulative and not exclusive of any rights, powers and remedies provided by law and may be exercised from time to time and as often as the Chargee may deem expedient; and 6.1.5. any waiver by the Chargee of any terms of this Charge shall only be effective if given in writing and then only against the Chargee and for the purpose and upon the terms for which it is given. 6.2. Where any discharge is made in whole or in part or any arrangement is made on the faith of any payment, security or other disposition which is avoided or must be repaid on bankruptcy, liquidation, by virtue of Section 1001 of the Taxes Consolidation Act 1997 or otherwise without limitation, this Charge shall continue in force as if there had been no such discharge or arrangement. The Chargee shall be entitled to concede or compromise in good faith any claim that any such payment, security or other disposition is liable to avoidance or repayment. 6.3. Until the Secured Obligations have been unconditionally and irrevocably satisfied and discharged in full to the satisfaction of the Chargee or as otherwise provided in the Credit Agreement or the Security Agreement, the Chargee may at any time keep in a separate account or accounts (without liability to pay interest thereon) in the name of the Chargee for as long as the Chargee may think fit, any moneys received recovered or realised under this Charge or under any other guarantee, security or agreement relating in whole or in part to the Secured Obligations without being under any intermediate obligation to apply the same or any part thereof in or towards the discharge of such amount.

  • Principles of Security The Contractor acknowledges that the Authority places great emphasis on confidentiality, integrity and availability of information and consequently on the security of the Premises and the security for the Contractor System. The Contractor also acknowledges the confidentiality of the Authority's Data.

  • Release of Security (a) In the event that (i) on a pro forma basis giving effect to the release of the security for the Securities and any other Debt of the Company with similar release provisions, (A) no Debt of the Company would be outstanding and (B) there would be no availability to the Company under any bank credit facilities, operating credit facilities or swap agreements, in the case of each of (A) and (B) that is or are secured by a Lien of the Pledge Agreement or any Collateral Document or any other Lien on the Deed of Trust Collateral, (ii) the ratings assigned to the Securities by at least two of the three Rating Agencies are Investment Grade Ratings and (iii) no Default or Event of Default has occurred and is continuing under this Indenture, then, without the consent of the Holders, the Company may permanently terminate the Lien of the Pledge Agreement or any Collateral Document and any other Lien on the Deed of Trust Collateral. On the Release Date, the provisions of Article Twelve of this Indenture shall terminate and have no further force or effect. (b) The Company shall notify the Rating Agencies and the Trustee of its intention to exercise its option to release the collateral at least 45 days prior to the proposed date of such release (the "Release Date"). In order to effect the release of the security, on the proposed Release Date the Company shall deliver to the Trustee an Officers' Certificate stating that (A) each of the conditions specified above has been satisfied and (B) the Company has not been notified by the Rating Agencies that the ratings assigned to the Securities will be downgraded as a result of the release of the security such that the ratings assigned to the Securities by at least two of the three Rating Agencies will be below Investment Grade. Such Officers' Certificate shall be dated on, or not more than one day prior to, the Release Date. (c) As soon as practicable after the occurrence of the Release Date, the Trustee will, upon Company Order and at the Company's expense, (i) return to the Company all Collateral in the Trustee's possession as shall not have been sold or otherwise applied pursuant to the terms of the Lien of the Pledge Agreement and any Collateral Document and any other Lien on the Deed of Trust Collateral and (ii) promptly execute and deliver further instruments and documents, and take all further actions, that may be necessary or desirable, or that the Company may reasonably request, in order to evidence the termination of the Lien of the Pledge Agreement and any Collateral Document and any other Lien on the Deed of Trust Collateral.

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

  • 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: 11.5.1 The guarantee must be made by an entity that meets the commercially reasonable creditworthiness requirements of Connecting Transmission Owner, and contains terms and conditions that guarantee payment of any amount that may be due from Developer, up to an agreed-to maximum amount. 11.5.2 The letter of credit must be issued by a financial institution reasonably acceptable to Connecting Transmission Owner and must specify a reasonable expiration date. 11.5.3 The surety bond must be issued by an insurer reasonably acceptable to Connecting Transmission Owner and must specify a reasonable expiration date. 11.5.4 Attachment S to the ISO OATT shall govern the Security that Developer provides for System Upgrade Facilities and System Deliverability Upgrades.

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