01/17/2017 (2) - Laserfiche WebLink

Home Browse Search

4. Secure FTP (SFTP) Transmission. 4.1 This method of data transmission permits Customer to deliver to and/or receive files from a Bank -maintained SFTP server Files transfers through SFTP communications are encrypted using Secure Shell ("SSH"). SSH is an open protocol for securing data communication across computer networks providing a secure channel for data transmission. The encryption used by SSH is intended to provide confidentiality and integrity of data over an unsecured network, such as the Internet. SSH uses public -key cryptography to authenticate the remote computer and allow the remote computer to authenticate the user, if necessary 4.2 Customer has the option to push files to Bank's SFTP server or have Bank pull Customer's files. For Customer push, Bank will create a drop -box directory on the SFTP server and provide Customer with a user name, password, and URL/domain name. Customer must provide an external IP address of the location sending files so that Customer's IP address can be added to access control lists within Bank's firewalls. For Bank to pull Customer's files, Bank will need a user name, password, URL/domain name, and directory from Customer so that Bank can pull files from Customer's SFTP servers. Bank and Customer will perform, to their mutual satisfaction, connectivity testing between platforms prior to Customer's use of the Services. 4.3 Customer also has the option for Bank to push Customer files (recommended by Bank) or Customer can pull the files from Bank's SFTP server For Bank to push Customer's file, Bank needs Customer's URL/domain name, unique user name, password, and directory For Customer to pull files from Bank's SFTP server, Customer must provide the external IP address of the location pulling the files so that Customer's IP address can be added to access control lists within Bank's firewalls. If Customer chooses to pull files from Bank's SFTP server, then files must be PGP encrypted, since files will reside on an SFTP server within Bank's DMZ. Bank will need Customer's public PGP key so that Bank can encrypt files. Bank and Customer will perforin, to their mutual satisfaction, connectivity testing between platforms and encryption testing (if necessary) on transmitted files prior to Customer's use of the Services. 4.4 Customer will need an FTP client capable of using the SSH protocol. If Customer decides to pull files from Bank, Customer will need an application/utility capable of creating a PGP key pair and decrypting PGP files. 5. Secure Software. 5.1 This method of data transmission involves the use of a Java® -based program that serves as a secure access channel through which information may be exchanged between Customer's Computer and Bank. This software is provided by Bank and must be installed on a Customer's Computer or network. Secure Software facilitates the secure transfer of files both to and from Customer's network location. 5.2 The technical requirements for Secure Software include an Internet connection. 5.3 Files for transmission through Secure Software are encrypted using SSL. SSL is an open protocol for securing data communication across computer networks that provides a secure channel for data transmission through its encryption capabilities. SSL allows for the transfer of digitally -signed certificates for authentication procedures and provides message integrity to protect against data being altered en route. Bank and Customer will perform, to their mutual satisfaction, connectivity testing between platforms and encryption testing on transmitted files pnor to Customer's use of the Services via Secure Software. 6. SWIFT Transmission. 6.1 This method of transmission provides Customer with the ability to use Society of Worldwide Interbank Financial Telecommunications operating as S.W.I.F.T. SCRL, Limited Liability Cooperative Society ("SWIFT") messaging services as described in this Section to engage in certain electronic communications with Bank (hereinafter the "SWIFT Services"). With the SWIFT Services, Customer may (1) transmit certain SWIFT messages and documents to Bank and receive certain SWIFT messages and documents from Bank and other financial institutions, using SWIFT FIN and/or SWIFTNet FileAct, the latter of which is a file transfer service that allows the transmission of messages and documents over the SWIFT network in all formats agreed upon by Bank, and (2) transmit and receive SWIFT Instructions (as further described below) from Bank and other fmancial institutions in connection with certain Cash Management Services as agreed by the parties from time to time. Bank is a participating depository financial institution in SWIFT. 6.2 SWIFT Rules. The "SWIFT Rules" are the documents and other publications as amended by SWIFT from time to time that Customer may access at www.swift.com whether in paper or electronic format, providing specific terms and conditions and other details relating to the provision and use of the SWIFT Services, including without limitation the SWIFT Contractual Arrangements; the SWIFT General Terms and Conditions; the SWIFT Service Bureau Policy and the SWIFT Data Retrieval Policy; the SWIFT MA-CUG, SCORE and TRCO Service Descriptions and any other SWIFT Service Descriptions applicable to the SWIFT Services; and the SWIFT On-line Support Service information. This Appendix, the SWIFT Services provided hereunder and the rights and obligations of the parties hereto shall be subject to the SWIFT Rules, as they may be amended from time to time. The parties agree to comply with the SWIFT Rules and to be aware of and comply with changes or updates to the SWIFT Rules. 6.3 SWIFT Instructions. 6.3.1 Bank may honor and act upon any authenticated SWIFT message, comfnunication or instruction, including any Payment Order (hereinafter a "SWIFT Instruction") received in Customer's name or BCS 4846-43833572 v.1 Page 51 of 58 0716 P65