sFTP (Secure File Transmission Protocol) Sample Clauses

sFTP (Secure File Transmission Protocol). The Client may upload FT Instructions through a secure file transmission protocol (“sFTP”), which includes multi-factor authentication processes and encryption of the complete transmission. The Client is responsible for maintaining the confidentiality of passwords or other codes used in connection with sFTP. BBH will act on FT Instructions received through sFTP without duty of further verification unless the Client notifies BBH in writing that its credentials have been compromised. As a prerequisite to receiving FT Instructions via sFTP, BBH and the Client shall have conducted testing and confirmed that the FT Instructions sent via sFTP can be processed in good time and order; once such testing and confirmation is satisfactory to the Client and BBH, BBH will act on FT Instructions received via sFTP.
Sample 1Sample 2Sample 3See All (24)
AutoNDA by SimpleDocs
sFTP (Secure File Transmission Protocol). The Authorized Person(s) may upload FT Instructions through a secure file transmission protocol (“sFTP”), which includes multi-factor authentication processes and encryption of the complete transmission. The Authorized Person(s) is responsible for maintaining the confidentiality of passwords or other codes used in connection with sFTP. BBH will act on FT Instructions received through sFTP without duty of further verification unless the Authorized Person(s) notifies BBH in writing that its credentials have been compromised. As a prerequisite to receiving FT Instructions via sFTP, BBH and the Authorized Person(s) shall have conducted testing and confirmed that the FT Instructions sent via sFTP can be processed in good time and order; once such testing and confirmation is satisfactory to the Authorized Person(s) and BBH, BBH will act on FT Instructions received via sFTP.
Sample 1Sample 2Sample 3See All (24)

Related to sFTP (Secure File Transmission Protocol)

  • Transmission encryption All data transmissions of County PHI or PI outside the secure internal network must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as AES. Encryption can be end to end at the network level, or the data files containing PHI can be encrypted. This requirement pertains to any type of PHI or PI in motion such as website access, file transfer, and E-Mail.

  • Information Transmission The Provider, on behalf of itself and its respective Subsidiaries, shall use commercially reasonable efforts to provide or make available, or cause to be provided or made available, to the Recipient, in accordance with Section 6.1 of the Separation and Distribution Agreement, any Information received or computed by the Provider for the benefit of the Recipient concerning the relevant Service during the Service Period; provided, however, that, except as otherwise agreed to in writing by the Parties (a) the Provider shall not have any obligation to provide, or cause to be provided, Information in any non-standard format, (b) the Provider and its Subsidiaries shall be reimbursed for their reasonable costs in accordance with Section 6.3 of the Separation and Distribution Agreement for creating, gathering, copying, transporting and otherwise providing such Information, and (c) the Provider shall use commercially reasonable efforts to maintain any such Information in accordance with Section 6.4 of the Separation and Distribution Agreement.

  • NYISO and Connecting Transmission Owner Obligations Connecting Transmission Owner and NYISO shall cause the New York State Transmission System and the Connecting Transmission Owner’s Attachment Facilities to be operated, maintained and controlled in a safe and reliable manner in accordance with this Agreement and the NYISO Tariffs. Connecting Transmission Owner and NYISO may provide operating instructions to Developer consistent with this Agreement, NYISO procedures and Connecting Transmission Owner’s operating protocols and procedures as they may change from time to time. Connecting Transmission Owner and NYISO will consider changes to their respective operating protocols and procedures proposed by Developer.

  • Connecting Transmission Owner Obligations Connecting Transmission Owner shall maintain its transmission facilities and Attachment Facilities in a safe and reliable manner and in accordance with this Agreement.

  • Data Transmission The procedures for transmitting load obligation data to PJM for DS Supplier’s DS Load shall be as set forth by PJM.

  • Data Transmission Control Except as necessary for the provision of the Cloud Services in accordance with the Agreement, Personal Data must not be read, copied, modified or removed without authorization during transfer. Where data carriers are physically transported, adequate measures are implemented at SAP to provide the agreed-upon service levels (for example, encryption and lead-lined containers).

  • Information Submission by Connecting Transmission Owner The initial information submission by Connecting Transmission Owner shall occur no later than one hundred eighty (180) Calendar Days prior to Trial Operation and shall include New York State Transmission System information necessary to allow the Developer to select equipment and meet any system protection and stability requirements, unless otherwise mutually agreed to by the Developer and Connecting Transmission Owner. On a monthly basis Connecting Transmission Owner shall provide Developer and NYISO a status report on the construction and installation of Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades, including, but not limited to, the following information: (1) progress to date; (2) a description of the activities since the last report; (3) a description of the action items for the next period; and (4) the delivery status of equipment ordered.

  • Loop Transmission Types 3.1 Subject to the conditions set forth in Section 1 of this Attachment, Verizon shall allow CBB to access Loops unbundled from local switching and local transport, in accordance with this Section 3 and the rates and charges provided in the Pricing Attachment. Verizon shall allow CBB access to Loops in accordance with, but only to extent required by, Applicable Law. The available Loop types are as set forth below:

  • Interconnection Request This Section 3 shall not apply to any proposed modifications by Interconnection Customer to its facilities for which Interconnection Customer must make an Interconnection Request under the Tariff. In such circumstances, the Interconnection Customer and Transmission Provider shall follow the requirements of Subpart A of Part IV of the Tariff.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

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