Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection.
Interconnection 2.1.10 Startup Testing and Commissioning
Interconnection Customer’s Interconnection Facilities The Interconnection Customer shall design, procure, construct, install, own and/or control the Interconnection Customer’s Interconnection Facilities described in Appendix A at its sole expense.
Use of Interconnection Facilities by Third Parties 46 9.9.1 Purpose of Interconnection Facilities 46 9.9.2 Third Party Users. 46
Interconnection Facilities 4.1.1 The Interconnection Customer shall pay for the cost of the Interconnection Facilities itemized in Attachment 2 of this Agreement. The NYISO, in consultation with the Connecting Transmission Owner, shall provide a best estimate cost, including overheads, for the purchase and construction of its Interconnection Facilities and provide a detailed itemization of such costs. Costs associated with Interconnection Facilities may be shared with other entities that may benefit from such facilities by agreement of the Interconnection Customer, such other entities, the NYISO, and the Connecting Transmission Owner.
Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 5.1 Scope of Traffic 13 5.2 Trunk Group Architecture and Traffic Routing 13 5.3 Logical Trunk Groups 13 5.4 End Office Access 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 6.1 Meet-Point Billing Services 14 6.2 Data Format and Data Transfer 14 6.3 Errors or Loss of Access Usage Data 15 6.4 Payment 15 6.5 Additional Limitation of Liability Applicable to Meet-Point Billing Arrangements 16 ARTICLE VII BLV/BLVI TRAFFIC 16
System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.
Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.
Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks.
One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from CBB to Verizon, CBB, at CBB’s own expense, shall:
