2016-204 - Laserfiche WebLink

Home Browse Search

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