preloader

Network Backbone

Description

Both Landing Zones and Managed Services are built on top of “simple” network topology: few Virtual Networks and Network Security Groups.

As soon as you need interconnection between environments (ex: on prem to TrustNest or landing zone to multiple managed services), enterprise routing begins a strong requirement to limit changes in the future, avoid IP overlapping. TrustNest Network Backbone offers a routing and an interconnection capabilities.

Depending on your security requirements or engineering maturity you may need to delegate internet exposition management to a partner (transversal team), to avoid having not secured enough application directly exposed to internet. TrustNest Network Backbone offers an advanced firewalling capability.

Use cases supported

  • Use case A: Point to Site interconnection. A user needs to access to specific ports (except HTTPS)
  • Use case B: Site to Site interconnection. An environment (on-premise, other cloud platforms) needs to be interconnected to TrustNest (move to Cloud, access to hardware / legacy systems)
  • Use case C: Interconnection between environments with corporate addon enabled
  • Use case D: Exposed your application with advanced firewalling capability (threat intelligence, IDPS)

SLA

  • For the interconnection between a datacenter and a TrustNest Hub using a double link, the SLA is 99.95%.

RoadMap

img

Next Steps

Request an IP range

Use postIT dedicated form

Request Flow modification (new Allow/Deny rule)

Warning: SSI validation is required

Use postIT dedicated form

Subscribe to an environment !

Start using one of MCS service by subscribing to a managed kubernetes, an APIM subscription key or a landing zone…

Subscribe
*