Connectivity Requirements Clause Samples

Connectivity Requirements. In the event that a data connection agreement, such as a “Master Data Connection Agreement,” “Data Connection Agreement,” and/or “Connection Supplement” (“DCA”) exists between the Parties, and incorporates the Agreement by reference, or is otherwise integrated with, or used to govern the Parties’ connectivity obligations under, this Agreement, agree that any information security requirements incorporated within such DCA are hereby superseded by the terms of these Security Requirements, effective as of the date these Security Requirements become effective under the Agreement, and the terms of such DCA are amended to require that the Security Requirements and not the information security requirements incorporated within the DCA are controlling in the Agreement (as well as any agreements subordinate to the Agreement). Notwithstanding the foregoing, the DCA remains in full force and effect for all other agreements between the Parties to which it applies.

Connectivity Requirements. Customer is solely responsible for providing, installing, managing and maintaining all necessary hardware, software, web browser, and related licenses (collectively, "Customer Devices"). The Customer Devices have, or be able to support, or be compatible with the following minimum operating system, web browser and Adobe flash player plug-in requirements:  Operating System: Windows, Linux, Solaris, Mac OS;  Web Browser: Microsoft® Internet Explorer 9, 10, and 11, Firefox 36.x, Chrome 41, and Safari 8; and  Adobe Flash Player plug-in 11.

Connectivity Requirements. All of the following apply and must be satisfied and correct for Allscripts’ corresponding obligations to apply:

Connectivity Requirements. In the event Supplier has, or will be provided, connectivity (i.e., access to AT&T’s or its customers’ networks) in conjunction with this Agreement, then, in addition to the foregoing, the following requirements shall apply to Supplier: 1. In the event that a data connection agreement, such as a “Master Data Connection Agreement,” “Data Connection Agreement,” and/or “Connection Supplement” (“DCA”) exists between the Parties, and incorporates this Agreement by reference, or is otherwise integrated with, or used to govern the Parties’ connectivity obligations under, this Agreement, such DCA is hereby superseded by the terms of these Security Requirements, effective as of the date these Security Requirements become effective under the Agreement, and the terms of such DCA are amended to require that the Security Requirements, and not the DCA, are controlling in the Agreement (as well as any agreements subordinate to this Agreement). Notwithstanding the foregoing, the DCA remains in full force and effect for all other agreements between the Parties to which it applies.

Connectivity Requirements. In the event that Supplier has, or will be provided, connectivity to AT&T’s or AT&T’s customers’ Nonpublic Information Resources in conjunction with this Agreement, then Supplier shall not establish interconnection to AT&T’s and AT&T’s customers’ Nonpublic Information Resources without the prior consent of AT&T and:

Connectivity Requirements. Mobile will provide and own the circuits to the Provider’s United States call center or data center location (or to a United States port of entry for locations outside the United States).

Connectivity Requirements. Devices communicating with Crestron Fusion require direct outbound connectivity to the Internet via the following ports: • The HTTPS Port 443 provides stateless Control Connection to Crestron Fusion SSLencrypted. • The Secure CIP Port 41796 provides stateful CIP Protocol Connection SSLencrypted. The path to the Internet for Ports 443 and 41796 needs to be free and unencumbered by other devices such as proxy servers, WAN optimizers, firewalls, etc. In the process of communicating with the server, the Control Connection is initiated by the device and used only during the following transactions: • When the device is registered with the server • When the RVI file (control processors) is transferred for auto-discovery • When re-registering with the server in case of loss of connection The CIP Protocol Connection is established by the device as a permanent TCP connection with the server. After the device is registered with the server, the CIP Protocol Connection does the following: • Exchanges Attributes (Joins) and other stateful information about the device • Exchanges the XML schedule (scheduling panels) • Provides heartbeats to keep the connection alive at all times NOTE: The Crestron AirMedia device uses only Port 41794 for the CIP Protocol Connection, which is not SSL encrypted.

Connectivity Requirements. Content Provider will provide: WAP URL to the main deck as identified in section 1 and 2.

Connectivity Requirements. Unless otherwise specified, the Subscription and Surge Services are provided by FireEye personnel remotely accessing Customer’s environment from FireEye’s networks. Customer must provide outbound TCP-based connectivity from all Products to FireEye for the establishment of a virtual private network (VPN). Details pertaining to specific network access requirements will be established in conjunction with installation activities.