ACH Security Framework Sample Clauses

ACH Security Framework. The NACHA Rules require that each non-consumer Originator must establish, implement, and update, as appropriate, policies, procedures, and systems with respect to the initiation, processing, and storage of Entries that are designed to: (a) protect the confidentiality and integrity of Protected Information until its destruction; (b) protect against anticipated threats or hazards to the security or integrity of Protected Information until its destruction; (c) protect against unauthorized use of Protected Information that could result in substantial harm to a natural person.
AutoNDA by SimpleDocs
ACH Security Framework. You are bound by the NACHA established minimum data security regulations: to protect sensitive non-public data of their customer or employees. This includes confidential and personal data such as: Health information, Social Security Numbers, Driver’s License Numbers, Bank, and account number information. Monitoring access controls against unauthorized use to systems with sensitive ACH data. Create, verify, or update security policies, procedures and controls related to the initiation, processing, and storage of ACH entries. Storage and safekeeping procedures for voided checks and ACH Authorization agreements.
ACH Security Framework. The ACH Security Framework establishes minimum data security obligations for ACH Network participants to protect ACH data. The NACHA Rule implementation includes three sets of rules, two of which apply to you: (15.a) Protection of Sensitive Data and Access Controls; and (15.b) Self-Assessment. As a customer of the Bank using the ACH Services, both you and the Bank are required to operate under the NACHA Rules.
ACH Security Framework. You acknowledge that you must establish, implement, and update, as appropriate, policies, procedures, and systems with respect to the initiation, processing, and storage of Entries that are designed to: (i) protect the confidentiality and integrity of Protected Information until its destruction, (ii) protect against anticipated threats or hazards to the security or integrity of Protected Information until its destruction, and (iii) protect against unauthorized use of Protected Information that could result in substantial harm to a natural person. “Protected Information” for this purpose means the non-public personal information, including financial information, of a natural person used to create, or contained within, an Entry and any related addenda record.

Related to ACH Security Framework

  • NIST Cybersecurity Framework The U.S. Department of Commerce National Institute for Standards and Technology Framework for Improving Critical Infrastructure Cybersecurity Version 1.1.

  • Legal Framework 1. This programme agreement shall be read in conjunction with the following documents which, together with this programme agreement, constitute the legal framework of the EEA Financial Mechanism 2014-2021: (a) Protocol 38c to the EEA Agreement on the EEA Financial Mechanism 2014-2021; (b) the Regulation on the implementation of the EEA Financial Mechanism 2014-2021 (hereinafter referred to as the “Regulation”) issued by the Donor States in accordance with Article 10(5) of Protocol 38c; (c) the Memorandum of Understanding on the Implementation of the EEA Financial Mechanism 2014-2021 (hereinafter referred to as the “MoU”), entered into between the Donor States and the Beneficiary State; and (d) any guidelines adopted by the FMC in accordance with the Regulation. 2. In case of an inconsistency between this programme agreement and the Regulation, the Regulation shall prevail. 3. The legal framework is binding for the Parties. An act or omission by a Party to this programme agreement that is incompatible with the legal framework constitutes a breach of this programme agreement by that Party.

  • Security Cameras Security cameras have been installed throughout the Facility; however, they will not routinely be used in areas where there is an expectation of privacy, such as restrooms or patient care areas.

  • Contractor Security Clearance Customers may designate certain duties and/or positions as positions of “special trust” because they involve special trust responsibilities, are located in sensitive locations, or have key capabilities with access to sensitive or confidential information. The designation of a special trust position or duties is at the sole discretion of the Customer. Contractor or Contractor’s employees and Staff who, in the performance of this Contract, will be assigned to work in positions determined by the Customer to be positions of special trust, may be required to submit to background screening and be approved by the Customer to work on this Contract.

  • Data Security Requirements Without limiting Contractor’s obligation of confidentiality as further described in this Contract, Contractor must establish, maintain, and enforce a data privacy program and an information and cyber security program, including safety, physical, and technical security and resiliency policies and procedures, that comply with the requirements set forth in this Contract and, to the extent such programs are consistent with and not less protective than the requirements set forth in this Contract and are at least equal to applicable best industry practices and standards (NIST 800-53).

  • Framework This Agreement establishes a framework that will enable Red Hat to provide Software and Services to Client. “Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. The specific services (the “Services”) and/or Software that Red Hat will provide to Client will be described in an Order Form, signed by the parties or otherwise accepted by Red Hat, which may consist of (a) one or more mutually agreed order forms, statements of work, work orders or similar transaction documents, or (b) an order placed by Client through Red Hat's online store accessible from a Red Hat website. The parties agree that the terms of this Agreement will govern all purchases and use by Client of Software and Services unless otherwise agreed by the parties in writing.

  • Cash Management System On or prior to the Closing Date and until the Termination Date, Borrower will establish and maintain the cash management system described in Schedule D. All payments in respect of the Collateral shall be made to or deposited in the blocked or lockbox accounts described in Schedule D in accordance with the terms thereof.

  • Security Standards The Provider shall implement and maintain commercially reasonable security procedures and practices that otherwise meet or exceed industry standards designed to protect Student Data from unauthorized access, destruction, use, modification, or disclosure, including but not limited to the unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of the Student Data (a "Security Breach"). For purposes of the DPA and this Exhibit G, "Security Breach" does not include the good faith acquisition of Student Data by an employee or agent of the Provider or LEA for a legitimate educational or administrative purpose of the Provider or LEA, so long as the Student Data is used solely for purposes permitted by SOPPA and other applicable law, and so long as the Student Data is restricted from further unauthorized disclosure.

  • Cash Management Systems On or prior to the Closing Date, Borrowers will establish and will maintain until the Termination Date, the cash management systems described in Annex C (the “Cash Management Systems”).

  • Security Clearance 6.7.1 Where specified by the Authority or the Contract user, the Supplier shall be responsible for ensuring that all Staff are security cleared to the level required by the Security Requirements not less than 5 Working Days before such person begins to perform the Services. If the Authority is responsible for applying for security clearance for Staff pursuant to this Clause 6.7.1, the Supplier shall provide a completed security clearance application form for such members of Staff to the Authority not less than 30 days before such members of Staff begin to perform the Services. 6.7.2 The Authority shall issue a pass for all Staff who are security cleared to an appropriate level for the Premises in accordance with Clause 6.7.1 on or before the date when such member of Staff is required to enter onto the Premises in Order to perform the Services. Passes shall remain the property of the Authority and shall be surrendered on demand or on termination or expiry of this Contract. 6.7.3 A member of Staff not in possession of a pass who is required by the Supplier or any Sub-contractor to provide the services urgently shall be allowed temporary access to the Premises on condition that the Supplier ensures, or procures that any Sub- contractor shall ensure, that such individual is accompanied at all times while on the Premises by a member of Staff who has been issued with a pass in accordance with Clause 6.7.1. 6.7.4 Without prejudice to the provisions of Clauses 6.7.1 to 6.7.3 inclusive, the Authority may refuse any member of Staff Admission to the Premises or require the removal of any member of Staff from the Premises in accordance with Clause 3.3 if such member of Staff is not in possession of a pass pursuant to Clause 6.7.2 or accompanied in accordance with Clause 6.7.3.

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