Common Backbone Security Sample Clauses

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.
AutoNDA by SimpleDocs
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. 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.

Related to Common Backbone Security

  • Site Security While providing services at a DSHS location, the Contractor, its agents, employees, or Subcontractors shall conform in all respects with physical, fire, or other security regulations specific to the DSHS location.

  • SOFTWARE SECURITY If applicable, BA warrants that software security features will be compatible with the CE’s HIPAA compliance requirements. This HIPAA Business Associate Agreement-Addendum shall supersede any prior HIPAA Business Associate Agreements between CE and BA. EXHIBIT E

  • System Security (a) If any party hereto is given access to the other party’s computer systems or software (collectively, the “Systems”) in connection with the Services, the party given access (the “Availed Party”) shall comply with all of the other party’s system security policies, procedures and requirements that have been provided to the Availed Party in advance and in writing (collectively, “Security Regulations”), and shall not tamper with, compromise or circumvent any security or audit measures employed by such other party. The Availed Party shall access and use only those Systems of the other party for which it has been granted the right to access and use.

  • E7 Security E7.1 The Authority shall be responsible for maintaining the security of the Authority’s Premises in accordance with its standard security requirements. The Contractor shall comply with all security requirements of the Authority while on the Authority’s Premises, and shall ensure that all Staff comply with such requirements.

  • Network Security 10.1 Protection of Service and Property. Each Party shall exercise the same degree of care to prevent harm or damage to the other Party and any third parties, its employees, agents or End User Customers, or their property as it employs to protect its own personnel, End User Customers and property, etc.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:

  • Data Security Requirements A. Data Transport. When transporting Confidential Information electronically, including via email, the data will be protected by:

  • STATE SECURITY 4.01 Nothing in this Agreement shall be construed as requiring the Employer to do or refrain from doing anything contrary to any instruction, direction or regulations given or made by or on behalf of the Government of Canada in the interest of the safety or security of Canada or any state allied or associated with Canada.

  • Performance Security If our Tender is accepted, we commit to obtain a performance security in accordance with the Tendering document;

  • Electronic PHI Security Rule Obligations 5.1 With respect to Electronic PHI, Business Associate shall:

Time is Money Join Law Insider Premium to draft better contracts faster.