Common Backbone Security Clause Samples
The Common Backbone Security clause establishes baseline security requirements for shared network infrastructure or backbone systems used by multiple parties. It typically outlines the minimum technical and procedural safeguards that must be implemented, such as encryption standards, access controls, and monitoring protocols, to protect data and maintain system integrity across the shared backbone. By setting these common standards, the clause ensures that all parties adhere to consistent security practices, reducing vulnerabilities and mitigating the risk of breaches in interconnected environments.
Common Backbone Security. No signaling from Internet routers is used or can be forwarded to VPN routers No signaling from Internet or VPN network, customers, or peers, is used on the Private Core Each Security Domain has its own BGP process Separate Forwarding Label-Switched Paths (LSPs) No forwarding path exists from Internet routers to VPN routers No IP forwarding in the Core, strictly MPLS LSPs between non-core routers No direct connections between the Security Domains.
Common Backbone Security. Yes CenturyLink IQ Networking maintains separate security domains for Internet, MPLS, and CenturyLink-provided VoIP services. MPLS services have the following features: Separate dedicated edge routers Separate Control Planes
Common Backbone Security. Describe how Supplier maintains both physical and logical separation of enterprise customers’ MPLS traffic and Public Internet traffic if the Supplier’s MPLS core (P-routers) is shared by both MPLS and Public Internet traffic.