Compliance with Security Procedures Sample Clauses
The Compliance with Security Procedures clause requires parties to adhere to specified security protocols and standards when handling sensitive information or systems. In practice, this means that organizations must implement measures such as access controls, encryption, regular security audits, and employee training to protect data from unauthorized access or breaches. The core function of this clause is to ensure that all parties maintain a consistent and adequate level of security, thereby reducing the risk of data breaches and ensuring regulatory or contractual compliance.
Compliance with Security Procedures. If an Entry (or request for cancellation or amendment of an Entry) received by the Bank purports to have been transmitted or authorized by Customer, it will be deemed effective as Customer's Entry (or request) and Customer shall be obligated to pay the Bank the amount of such Entry even though the Entry (or request) was not authorized by Customer, provided the Bank accepted the Entry in good faith and acted in compliance with the Security Procedures referred to in this Agreement or in the Appendix with respect to such Entry. If an Entry (or request for cancellation or amendment of an Entry) received by the Bank was transmitted or authorized by Customer, Customer shall pay Bank the amount of the Entry, whether or not Bank complied with the Security Procedure referred to in Schedule A and Schedule D with respect to that Entry and whether or not that Entry was erroneous in any respect or that error would have been detected if Bank had complied with such procedures.
Compliance with Security Procedures. Customer shall have complied with applicable Security Procedures for the Service as may be required by Bank from time to time.
Compliance with Security Procedures. If a Data File (or request for cancellation or amendment of an entry in a Data File) received by the Bank purports to have been transmitted or authorized by Customer, it will be deemed effective as Customer's Data File (or request) and Customer shall be obligated to pay the Bank the amount of such Data File even though the Data File (or request) was not authorized by Customer, provided the Bank accepted the Data File in good faith and acted in compliance with the Security Procedures referred to in this Agreement or in the Appendix with respect to such Data File. If a Data File (or request for cancellation or amendment of an entry in a Data File) received by the Bank was transmitted or authorized by Customer, Customer shall pay Bank the amount of the Data File, whether or not Bank complied with the Security Procedure with respect to that Data File and whether or not that Data File was erroneous in any respect or that error would have been detected if Bank had complied with such procedures.
Compliance with Security Procedures. 67.1 If an Entry (or a request for cancellation or amendment of an Entry) received by Bank was transferred in accordance with the Security Procedures applicable to the Service and thereby purports to have been transmitted or authorized by Customer, it shall be deemed effective as Customer’s Entry (or request), even if the Entry (or request) was not authorized by Customer. If Bank accepted the Entry (a) in compliance with the Security Procedures with respect to such Entry, (b) in compliance with any written agreement or instruction of Customer restricting acceptance of payment orders issued in Customer’s name, and (c) in good faith, then with respect to a credit Entry, Customer shall be obligated to pay Bank the amount of such Entry, and with respect to a debit Entry, Customer shall maintain sufficient funds in the Settlement Account, as defined in Section 73, to fund the reversal of such Entry, if necessary.
67.2 If an Entry (or a request for cancellation or amendment of an Entry) received by Bank was actually transmitted or authorized by Customer, Customer shall pay Bank the amount of any such credit Entry and shall maintain funds in the Customer’s Settlement Account to fund the reversal of any such debit Entry, whether or not Bank complied with the Security Procedures described herein or in the Part Iand whether or not that Entry was erroneous in any respect or that any such error would have been detected if Bank had complied with the Security Procedures.
Compliance with Security Procedures a. If an Entry (or a request for cancellation of an Entry) received by Bank purports to have been transmitted or authorized by Customer, it will be deemed effective as Customer’s Entry (or request) and Customer shall be obligated to pay Bank the amount of such Entry as provided herein even though the Entry (or request) was not authorized by Customer, provided Bank acted in compliance with the Security Procedures. If an Entry (or a request for cancellation of an Entry) received by Bank purports to have been transmitted or authorized by Customer (including, without limitation, any Authorized Representative or Authorized Agent), it will be deemed effective as Customer’s Entry (or request) and Customer shall be obligated to pay Bank the amount of such Entry as provided herein even though the Entry (or request) was not authorized by Customer, provided Bank acted in compliance with the Security Procedures with respect to such Entry. If signature comparison is to be used as a part of those Security Procedures, Bank shall be deemed to have complied with that part of such Security Procedures if it compares the signature accompanying a file of Entries (or request for cancellation of an Entry) received with the signature of an Authorized Representative and, on the basis of such comparison, believes the signature accompanying such file to be that of such Authorized Representative.
b. If an Entry (or request for cancellation of an Entry) received by Bank was transmitted or authorized by Customer, Customer shall be obligated to pay the amount of the Entry as provided herein, whether or not Bank complied with the Security Procedures with respect to that Entry and whether or not that Entry was erroneous in any respect or that error would have been detected if Bank had complied with such Security Procedures.
Compliance with Security Procedures a. If an Entry (or a request for cancellation or amendment of a File) received by the Bank purports to have been transmitted or authorized by the Business Entity, it will be deemed effective as the Business Entity's Entry (or request) and the Business Entity shall be obligated to pay the Bank the amount of such Entry (or request) even though the Entry (or request) was not actually authorized by the Business Entity, whether or not the Bank acted in compliance with the security procedure referenced in Schedule A. If signature comparison is to be used as a part of that security procedure, the Bank shall be deemed to have complied with that part of such procedure if it compares the signature accompanying a file of Entries (or request) with the signature of an Authorized Representative of the Business Entity and, on the basis of such comparison, believes the signature to be that of such Authorized Representative.
Compliance with Security Procedures. Contractor shall comply with all District safety and security protocols and shall maintain as confidential and shall not disclose to any third parties any information regarding District security protocols or any information regarding the planned or actual response of students, employees, contractors, or third parties, to any emergency situation at the District or involving District employees, contractors, or students. Contractor shall promptly report to a District administrator any threat related to the safety of the schools, its students, or staff, in accordance with District threat reporting protocols, except to the extent such reporting disclosure is prohibited by a confidentiality law, and may be asked to sign an acknowledgement of that reporting obligation.
Compliance with Security Procedures. Except as otherwise required by applicable law, if a Payment Order (or a request for cancellation or amendment of a Payment Order) received by Bank purports to have been transmitted or authorized by Client, it will be deemed effective as Client's Payment Order (or request) and Client shall be obligated to pay Bank the amount of such Payment Order as provided herein even though the Payment Order (or request) was not authorized by Client, provided Bank acted in compliance with the security procedure referred to in Appendix A with respect to such Payment Order.
Compliance with Security Procedures. The authorizations in Exhibit 3 (or Exhibit 5-B in the case of third-party processors) and security procedures in Exhibit 3 (or Exhibit 5-B in the case of third-party processors) shall apply equally to Entries and requests for cancellation or amendment of Entries. Accordingly, in this Section 19, “Entry” shall be construed to include requests for cancellation or amendment of Entries. If an Entry received by the Bank was transmitted or authorized by the Company, or if an Entry received by the Bank purports to have been transmitted or authorized by the Company, and the Bank has complied with the security procedures provided for herein, then, in either case, it will be deemed effective as the Company’s Entry. If signature comparison is to be part of that security procedure, the Bank shall be deemed to have complied with that part of such procedure if the signature accompanying a file or Entries bears any resemblance whatsoever to the signature of the Company’s authorized representative for submission of Entries. The Company is responsible for maintaining the confidentiality of the security procedures hereunder and shall promptly report to the Bank any breach thereof. The Bank shall have no liability for losses occasioned by the Company’s failure to maintain the confidentiality of its security procedures. The Bank may change, add, or delete any procedures established pursuant to this Agreement, from time to time, upon notice to the Company.
Compliance with Security Procedures. If an Entry (or a request for cancellation or amendment of an Entry) received by Bank purports to have been transmitted or authorized by Client, it will be deemed effective as Client’s Entry (or request) and Client shall be obligated to pay Bank the amount of such Entry even though the Entry (or request) was not authorized by Client, provided Bank accepted the Entry in good faith and acted in compliance with the Security Procedures with respect to such Entry.