Data Connection Security Requirements Sample Clauses

Data Connection Security Requirements. 33.11.1 CLEC agrees that interconnection of CLEC data facilities with SBC- 13STATE data facilities for access to OSS will be in compliance with the applicable regional interconnection procedures: “SBC-13STATE Competitive Local Exchange Carrier (CLEC) Operations Support System Interconnection Procedures” document, current at the time of initial interconnection in each region for access to SBC-13STATE’s OSS. The following additional terms in this section govern direct and dial up connections between CLEC and SBC-13STATE for access to OSS Interfaces:
AutoNDA by SimpleDocs
Data Connection Security Requirements. 9.1 CARRIER agrees to comply with AT&T-22STATE data connection security procedures, including but not limited to procedures on joint security requirements, information security, user identification and authentication, network monitoring, and software integrity. These procedures are set forth on the AT&T CLEC Online website.
Data Connection Security Requirements. 7.1 WSP agrees to comply with AT&T-21STATE data connection security procedures, procedures as set forth on the AT&T CLEC Online website as they may change from time to time, including but not limited to procedures on joint security requirements, information security, user identification and authentication, network monitoring, and software integrity. To the extent there is a conflict between this Section 7.0 and the Competitive Local Exchange Carrier (CLEC) Operations Support Systems (OSS) Procedures, the CLEC OSS Interconnection Procedures shall govern.
Data Connection Security Requirements. 9.1 CLEC agrees that interconnection of CLEC data facilities with AT&T data facilities for access to OSS will be in compliance with AT&T’s “Competitive Local Exchange Carrier (CLEC) Operations Support System Interconnection Procedures” document current at the time of initial connection to a RAF. The following additional terms in this Section 9.0 govern direct and dial up connections between CLEC and the PRAF, LRAF, ARAF and SRAF for access to OSS Interfaces.
Data Connection Security Requirements. 8.1 WSP agrees that interconnection of WSP data facilities with AT&T-13STATE data facilities for access to the applicable OSS for the purposes described herein will be in compliance with AT&T-13STATE’s “Competitive Local Exchange Carrier (CLEC) Operations Support System Interconnection Procedures” document current at the time of initial connection to a RAF. The following additional terms in this Section 8 govern direct and dial up connections between WSP and the PRAF, LRAF, ARAF and SRAF for access to OSS Interfaces.
Data Connection Security Requirements. 7.1 WSP agrees to comply with AT&T-21STATE data connection security procedures, including but not limited to procedures on joint security requirements, information security, user identification and authentication, network monitoring, and software integrity. These procedures are set forth on the AT&T-21STATE Prime Access website.
Data Connection Security Requirements. 9.1 CLEC agrees to comply with AT&T data connection security procedures as set forth on the AT&T CLEC Online website as they may change from time to time, including but not limited to procedures on joint security requirements, information security, user identification and authentication, network monitoring, and software integrity. To the extent there is a conflict between this Amendment’s Section 2 and the Competitive Local Exchange Carrier (CLEC) Operations Support Systems (OSS) Procedures, the CLEC OSS Interconnection Procedures shall govern.
AutoNDA by SimpleDocs
Data Connection Security Requirements. 9.1 CARRIER agrees that interconnection of CARRIER data facilities with AT&T-13STATE data facilities for access to OSS will be in compliance with AT&T-13STATE’s “Competitive Local Exchange Carrier (CLEC) Operations Support System Interconnection Procedures” document current at the time of initial connection to a RAF. The following additional terms in this Section 9 govern direct and dial up connections between CARRIER and the PRAF, LRAF, ARAF and SRAF for access to OSS Interfaces.
Data Connection Security Requirements. 14.1. This Agreement incorporates Data Connection Security Requirements by reference, as posted on AT&T Prime Access, as they may be amended from time to time at the discretion of AT&T, and for those listed responsibilities to control in the event of any conflict between the responsibilities and the TPA.
Data Connection Security Requirements. 11.1 CLEC agrees that interconnection of CLEC data facilities with SBC-13STATE data facilities for access to OSS will be in compliance with the applicable regional interconnection procedures: SBC-7STATE Competitive Local Exchange Carrier (CLEC) Operations Support System Interconnection Procedures document, SNET’s “Wholesale CIWin User Guide”; SNET’s “EF User Guide”; SNET’s “ESAP Installation Guide”; SNET’s “ESAP Help Desk Guide”; and SNET’s “CLEC Mechanized Interface Specification” current at the time of initial interconnection in each region for access to SBC-13STATE’s OSS. The following additional terms in this Section 16 govern direct and dial up connections between CLEC and SBC-13STATE for access to OSS Interfaces
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!