Security for NIDV Proofs. We say that an NIDV proof system is secure if it satisfies the notions of correctness, non-transferability and soundness. These are defined as follows.
Security for NIDV Proofs Sample Clauses
Related to Security for NIDV Proofs
Review Procedures for Identifying Entity Accounts With Respect to Which Reporting Is Required For Preexisting Entity Accounts described in paragraph B of this section, the Reporting Finnish Financial Institution must apply the following review procedures to determine whether the account is held by one or more Specified U.S. Persons, by Passive NFFEs with one or more Controlling Persons who are U.S. citizens or residents, or by Nonparticipating Financial Institutions:
Security for Obligations This Agreement secures, and the Collateral is collateral security for, the prompt and complete payment or performance in full when due, whether at stated maturity, by required prepayment, declaration, acceleration, demand or otherwise (including the payment of amounts that would become due but for the operation of the automatic stay under Section 362(a) of the Bankruptcy Code, 11 U.S.C. §362(a) (and any successor provision thereof)), of all Obligations with respect to every Grantor (the “Secured Obligations”).
Security for Performance In the event that Exhibit A Section 4 indicates the need for Consultant to provide additional security for performance of its duties under this Agreement, Consultant shall provide such additional security prior to commencement of its Required Services in the form and on the terms prescribed on Exhibit A, or as otherwise prescribed by the City Attorney.
ACCESS TO SECURITY LOGS AND REPORTS Upon request, the Contractor shall provide access to security logs and reports to the State or Authorized User in a format as specified in the Authorized User Agreement.
Objections to New Subprocessors (a) If Customer has a legitimate reason under Data Protection Law to object to the new Subprocessors’ processing of Personal Data, Customer may terminate the Agreement (limited to the Cloud Service for which the new Subprocessor is intended to be used) on written notice to SAP. Such termination shall take effect at the time determined by the Customer which shall be no later than thirty days from the date of SAP’s notice to Customer informing Customer of the new Subprocessor. If Customer does not terminate within this thirty day period, Customer is deemed to have accepted the new Subprocessor.
Entity Accounts With Respect to Which Reporting Is Required With respect to Preexisting Entity Accounts described in paragraph B of this section, only accounts that are held by one or more Entities that are Specified U.S. Persons, or by Passive NFFEs with one or more Controlling Persons who are U.S. citizens or residents, shall be treated as U.S. Accounts. In addition, accounts held by Nonparticipating Financial Institutions shall be treated as accounts for which aggregate payments are required to be reported under an FFI Agreement.
Program Requirements Provided At No Charge to the Judicial Council A. The Contractor shall provide the following items during the Program at no charge to the Judicial Council:
Security for Payment To secure payment of all obligations due hereunder, the Customer hereby grants to Custodian a continuing security interest in and right of setoff against each Account and all Property held therein from time to time in the full amount of such obligations; provided that, if there is more than one Account and the obligations secured pursuant to this Section can be allocated to a specific Account or the Portfolio related to such Account, such security interest and right of setoff will be limited to Property held for that Account only and its related Portfolio. Should the Customer fail to pay promptly any amounts owed hereunder, Custodian shall be entitled to use available Cash in the Account or applicable Account, as the case may be, and to dispose of Securities in the Account or such applicable Account as is necessary. In any such case and without limiting the foregoing, Custodian shall be entitled to take such other action(s) or exercise such other options, powers and rights as Custodian now or hereafter has as a secured creditor under the New York Uniform Commercial Code or any other applicable law.
Service Accountability Agreements The HSP acknowledges that if the LHIN and the HSP enter into negotiations for a subsequent service accountability agreement, subsequent funding may be interrupted if the next service accountability agreement is not executed on or before the expiration date of this Agreement.
Security Violations and Accounts Updates Grantee will adhere to the Confidentiality Article requirements and HHS Data Usage Agreement of this contract and immediately contact System Agency if a security violation is detected, or if Grantee has any reason to suspect that the security or integrity of the CMBHS data has been or may be compromised in any way.
