Business Continuity Registry Operator shall maintain a business continuity plan, which will provide for the maintenance of Registry Services in the event of an extraordinary event beyond the control of the Registry Operator or business failure of Registry Operator, and may include the designation of a Registry Services continuity provider. If such plan includes the designation of a Registry Services continuity provider, Registry Operator shall provide the name and contact information for such Registry Services continuity provider to ICANN. In the case of an extraordinary event beyond the control of the Registry Operator where the Registry Operator cannot be contacted, Registry Operator consents that ICANN may contact the designated Registry Services continuity provider, if one exists. Registry Operator shall conduct Registry Services Continuity testing at least once per year.
Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).
Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as all line-side and trunk-side facilities, plus the features, functions, and capabilities of the switch. The features, functions, and capabilities of the switch shall include the basic switching function of connecting lines to lines, lines to trunks, trunks to lines, and trunks to trunks. Local circuit switching includes all vertical features that the switch is capable of providing, including custom calling, custom local area signalling service features, and Centrex, as well as any technically feasible customized routing functions. 4.2.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for ▇▇▇▇ when ▇▇▇▇: (1) serves an End User with four (4) or more voice-grade (DS0) equivalents or lines served by BellSouth in Zone 1 of one of the following MSAs: Atlanta, GA;
Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.
Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following: