Cyber incident damage assessment activi- ties Sample Clauses

Cyber incident damage assessment activi- ties. If DOT elects to conduct a damage as- sessment, the Contracting Officer will re- quest that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (c) of this clause.
AutoNDA by SimpleDocs

Related to Cyber incident damage assessment activi- ties

  • Liability for Incidental and Consequential Damages Contractor shall be responsible for incidental and consequential damages resulting in whole or in part from Contractor’s acts or omissions.

  • Indemnity Limitation for TIPS Sales Texas and other jurisdictions restrict the ability of governmental entities to indemnify others. Vendor agrees that if any "Indemnity" provision which requires the TIPS Member to indemnify Vendor is included in any TIPS sales agreement/contract between Vendor and a TIPS Member, that clause must either be stricken or qualified by including that such indemnity is only permitted, "to the extent permitted by the laws and constitution of [TIPS Member's State]” unless the TIPS Member expressly agrees otherwise. Any TIPS Sale Supplemental Agreement containing an "Indemnity" clause that conflicts with these terms is rendered void and unenforceable.

  • Breach of Contract and Liquidated Damages A. Where OGS determines that the Contractor is not in compliance with the requirements of subsection 4.7 of this Contract, and the Contractor refuses to comply with such requirements, or if it is found to have willfully and intentionally failed to comply with the MWBE participation goals set forth in the Contract, the Contractor shall be obligated to pay liquidated damages to OGS. B. Such liquidated damages shall be calculated as an amount equaling the difference between: 1. All sums identified for payment to MWBEs had the Contractor achieved the contractual MWBE goals; and 2. All sums actually paid to MWBEs for work performed or materials supplied under the Contract. C. If OGS determines that Contractor is liable for liquidated damages and such identified sums have not been withheld by OGS, Contractor shall pay such liquidated damages to OGS within sixty (60) days after they are assessed. Provided, however, that if the Contractor has filed a complaint with the Director of the Division of Minority and Women’s Business Development pursuant to 5 NYCRR § 142.12, liquidated damages shall be payable only in the event of a determination adverse to the Contractor following the complaint process.

  • Compensation for Damage or Loss 1. When investments made by investors of either Contracting Party suffer loss or damage owing to war or other armed conflict which is not a result of the activities of the Contracting Party to which the investors belong, civil disturbances, revolution, riot or similar events in the territory of the latter Contracting Party, they shall be accorded by the latter Contracting Party, treatment, as regards restitution, indemnification, compensation or any other settlement, not less favourable than that that the latter Contracting Party accords to its own investors or to investors of any third State, whichever is most favourable to the investors concerned. 2. Without prejudice to paragraph 1 of this Article, investors of one Contracting Party who in any of the events referred to in that paragraph suffer damage or loss in the territory of the other Contracting Party resulting from: a) requisitioning of their property or part thereof by its forces or authorities; b) destruction of their property or part thereof by its forces or authorities which was not caused in combat action or was not required by the necessity of the situation, shall be accorded a prompt restitution, and where applicable prompt, adequate and effective compensation for damage or loss sustained during the period of requisitioning or as a result of destruction of their property. Resulting payments shall be made in freely convertible currency without delay. 3. Investor whose investments suffer damage or loss in accordance to paragraph 2. of this Article, shall have the right to prompt review of its case by a judicial or other competent authority of that Contracting Party and of valuation of its investments and payment of compensation in accordance with the principles set out in paragraph 2. of this Article.

  • Exceptions from Liability Without limiting the generality of any other provisions hereof, neither the Custodian nor any Domestic Subcustodian shall be under any duty or obligation to inquire into, nor be liable for:

  • Incidental and Consequential Damages Contractor shall be responsible for incidental and consequential damages resulting in whole or in part from Contractor’s acts or omissions. Nothing in this Agreement shall constitute a waiver or limitation of any rights that City may have under applicable law.

  • Termination Damages If the Term of this Lease is terminated for default, unless and until Landlord elects lump sum liquidated damages described in the next paragraph, Tenant covenants, as an additional, cumulative obligation after any such termination, to pay punctually to Landlord all the sums and perform all of its obligations in the same manner as if the Term had not been terminated. In calculating such amounts Tenant will be credited with the net proceeds of any rent then actually received by Landlord from a reletting of the Premises after deducting all Rent that has not then been paid by Tenant, provided that Tenant shall never be entitled to receive any portion of the re-letting proceeds, even if the same exceed the Rent originally due hereunder.

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-­‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-­‐and-­‐ media/announcement-­‐2-­‐17nov13-­‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-­‐OARC) <xxxxx://xxx.xxx-­‐xxxx.xxx/xxxx/xxxx/xxxx>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-­‐ new-­‐gtld-­‐annex-­‐1-­‐07oct13-­‐en.pdf>.

  • Six-Month Delay Notwithstanding anything to the contrary in this Agreement, no compensation or benefits, including without limitation any severance payments or benefits payable under this Section 4, shall be paid to the Executive during the six-month period following the Executive’s Separation from Service if the Company determines that paying such amounts at the time or times indicated in this Agreement would be a prohibited distribution under Section 409A(a)(2)(B)(i) of the Code. If the payment of any such amounts is delayed as a result of the previous sentence, then on the first day of the seventh month following the date of Separation from Service (or such earlier date upon which such amount can be paid under Section 409A without resulting in a prohibited distribution, including as a result of the Executive’s death), the Company shall pay the Executive a lump-sum amount equal to the cumulative amount that would have otherwise been payable to the Executive during such period.

  • Loss or Damage The District and its agents and authorized representatives shall not in any way or manner be answerable or suffer loss, damage, expense, or liability for any loss or damage that may happen to the Work, or any part thereof, or in or about the same during its construction and before acceptance, and the Contractor shall assume all liabilities of every kind or nature arising from the Work, either by accident, negligence, theft, vandalism, or any cause whatsoever; and shall hold the District and its agents and authorized representatives harmless from all liability of every kind and nature arising from accident, negligence, or any cause whatsoever.

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