A how-to guide to network integrity validation and trusted path routing
Can you verify that your network is safe and authentic across all its components? For most Service Providers, the complicated—but honest—answer is no.
The reason behind the uncertainty is easier to answer. Service providers like you operate the largest and most complex networks in the world making it difficult—if not impossible—to have complete visibility into all your network components and traffic. It’s even more challenging to gain an understanding of just how much you don’t know about your network. The root of the network trust problem is the inability to accurately verify that all domains and network components have not been tampered with and are genuine to their manufactured state.
To overcome these challenges and establish network trust, service providers are turning to an automated integrity validation or “trust verification” capability. This gives service providers a continuously updated ‘trust status’ for their infrastructure elements that is measured against known good values for those elements—ensuring they are unaltered. One application for a trustworthy infrastructure is a service known as trusted path routing. Adding this capability is essential—or soon will be—for service providers as well as their customers to ensure data security and privacy across the transport networks. Understanding exactly how you can enable and deploy network trustworthiness at a massive scale will help you give your business a competitive edge when it comes to security.
There are two essential elements to building network trust. First, define exactly what a trusted network is for your organization and second, create an automated, continuous process that verifies your network continuously meets that definition. Using a definition founded on immutable information contained within the infrastructure components allows the automated process to quickly and accurately assess the state of your network to ensure it is entirely in your control.
But what do these processes look like in a mass-scale network? Two metaphors help us illustrate how it works: a snapshot and a handshake.
Imagine taking a snapshot of your “pure” network infrastructure at the time each component was manufactured into the routers. That snapshot would contain the unique identifiable information of each component used onboard your router. Having this information for each router within your network would provide you with a baseline of the original manufactured elements provided to you. The snapshot defines your network trust by defining the hardware and components that should be on the network. Additionally, the operating software for those routers also contains unique identifiable information that would provide authentication that it is genuine.
The snapshot is a data artifact that clearly defines the unique identifiers for your network infrastructure so it can be easily and continuously referenced against your active network elements to identify irregularities.
Related link: Learn more about how to achieve mass network awareness and visibility >
A handshake requires trust and agreement: both parties must acknowledge one another and agree to the connection.
That’s why it is historically used as a metaphor in a network environment. When used to establish trust in a network, or network trust, the handshake occurs between the hardware and software within each routing device. Each party, hardware or software, has a list of the other’s unique identifiers to use as a validation tool. This allows the hardware and software to have a secret handshake of sorts, and if either party fails at the secret handshake, the router is either not allowed to operate or a ‘failed’ message is sent to an administrator for attention.
Together, the snapshot and the handshake form the foundation of trust within the infrastructure that comprises your network. While enforcing network trust manually is not plausible, your infrastructure already manages it on an ongoing basis. Operating a trustworthy network just inserts a crucial but quick moment of verification into the process and stores the trust status of your network so your engineers can quickly receive notifications on irregularities and take action.
The trust status of the network is continually updated and stored in an attestation database. This database acts as an independent verification tool for each network router to use to ensure that the router they want to communicate with is playing nice in the network and can be trusted with the data transport, thus enabling trusted path routing.
When you set up trusted path routing, your network engages in a continuous, ongoing measurement, almost like whitelisting, confirming that no alterations have been made. Or, if it detects alterations, your network can react appropriately to reroute traffic and issue notifications to make sure these issues can get resolved. In short, only trustworthy components of your network are engaged, ensuring more secure connections.
Trust verification and trusted path routing offer clear and significant security benefits to your mass-scale network, not to mention the peace of mind that comes with knowing your infrastructure is free of tampering and other malicious efforts. High network trust also offers significant benefits to your customers—benefits that complement the traditional network services they already use.
Consider a few points that help you build a business case for implementing trust verification processes as a service provider:
Related link: Learn more about Cisco’s approach to Segment Routing >
Network trustworthiness represents a growing field of opportunity for service providers - especially in applications for mass-scale networks. Combined with Trusted Path Routing and Segment Routing, trust verification allows you to expand your business by offering these new, advanced types of network connections to some of your most valuable customers and users.