Elastic Visibility Into Your Clouds – Without The Strain
The rapid move to the cloud is understandable since it is so alluring: It is elastic, costs less to operate and manage and is scalable — enhancing business agility. The latest Cisco Global Cloud Index states that by 2020, 92% of workloads will be processed in public and private cloud data centers and just 8% in physical data centers. But in engineering, there is no such thing as getting something for nothing. With cloud migration, the benefits of agility are realized at the expense of visibility and control.
When we surveyed a range of businesses on their virtualization practices, just 37% monitored their virtualized environments with the same rigor as their physical networks, revealing a big visibility gap when it comes to the cloud. While it may seem like a worthwhile trade-off today, it won’t be if and when things go wrong.
For instance, malicious activity can happen right under a company’s nose considering a significant portion of network traffic in virtualized environments doesn’t even hit a physical link or traditional monitoring tool. Moreover, virtualized networks introduce additional software layers that could be riddled with bugs. Organizations need to monitor their virtual networks even more rigorously than their physical counterparts. Not a risk worth taking, the visibility gap needs to be bridged quickly to ensure better control, maintain security no matter where their data goes and confirm the reliability of core business applications.
Inserting virtual network taps into the virtualized environment and sending the traffic to their monitoring, analytics and security tools should help the problem. Unfortunately, doing this would quickly flood these tools with data because internal “East-West” traffic in virtual data centers typically represents 80% of the total traffic. It would be like connecting a lawn sprinkler to a fire hydrant. Identifying and extracting only relevant traffic is key, but how can that efficiently be done efficiently? More so, how can virtual taps handle scaling up and down as virtual machines emerge and dissolve? Let’s take a closer look at the key requirements for visibility and monitoring in virtual environments.
There are four key points to consider when deploying virtual for meaningful, granular access to critical application traffic on virtualized networks.
Horizontal scale: Cloud environments are attractive because they can scale up and down rapidly as user demands and workloads change. When placing virtual taps in a virtual network, ensure they can scale up to accommodate rapid growth in traffic volumes as well as user numbers and data interactions. The taps should do this automatically, without IT intervention. Virtualization means agility, so if an application or service expands to handle 10x or 100x the number of users, make sure the virtual tap in use can scale elastically — without impacting application performance.
Securing in the dark: Virtualized networks are typically segmented using virtual firewalls to protect key applications and services from attack and to prevent compromising lateral movement in the virtualized environment. So the virtual taps used need to see the application and network traffic flowing between segments. With this comprehensive insight, it’s easier to make sure the appropriate security rules and policies governing each segment are being enforced.
More containers: As virtual machine use grows, container use multiplies even faster by as much as 10x or more since each application may employ multiple containers. An organization using container-based virtualization to boost application performance must have virtual taps that can access traffic in the container environment.
DevOps elasticity: When the DevOps team puts out a new build — which doesn’t just cover new applications and services, but also updates to existing ones — then that update propagates across the virtual environment. Individual virtual machines, containers and their hosted applications have shorter and shorter lifespans requiring continual awareness of the actual state of the environment. It is vital that these changes not block the entire traffic path or take the virtual tap down. As an example, consider how to archive and retrieve monitored traffic from a container that no longer exists. The tap is your sentinel, which has to maintain pervasive access to traffic to enable you to see what is happening on the virtual network: it must be fault-tolerant, even if the application it is monitoring fails.
These four points apply when monitoring any virtualized environment, whether public cloud, private cloud or software defined wide-area networks (SD-WANs). The virtual taps and the overall visibility solution need to be completely environment-agnostic.
Once the virtual taps have been deployed to extract traffic from the virtual machines in an environment, organizations can start processing packets. This can be done via network packet brokers, which keep duplicate data from overwhelming monitoring and security tools while ensuring they scale up/down as needed. Ultimately, data traffic should be broken up into manageable pieces using packet filtering, grooming and brokering processes, so security systems and analytics tools see everything.
Elastically scalable access is achievable for all the data crossing virtual networks and clouds through intelligent distribution to analytics and compliance tools. You do not have to give up visibility to gain cloud speed and cost advantages. Fortunately, you can have both with the right architecture.