By: Robert DeWeese
Say you lead a small but highly competent networking team—working for a small but prestigious health care provider or bank. A few years ago, your team got a new deployments system up and running. It’s worked well so far, but now your organization is scaling up and the cracks are starting to show.
The manual side of cloud maintenance was always an annoyance for your team, but it was never prohibitive—until now. Today, cloud maintenance has become so labor intensive that you worry it’s only a matter of time until a mistake occurs, and a virtual door is left open to exposure or breach.
Now: scenario two.
You lead networking for a multinational hotel or car rental brand. You’ve spent the last few years migrating to a software-defined wide-area network (SD-WAN) network, supported by a private multi-protocol label switching (MPLS) network. You have software-defined routers at each of your 3,000 branch locations, each requiring $1,000 a month in licensing fees. On top of this hefty monthly bill, whenever you need to add a new branch to the network—granting access, authenticating, and other tasks—you deal with delays of up to 90 days.
Clearly, the networks in both these scenarios need a cloud makeover—a new roadmap for reducing monthly operational costs, better securing data, and reducing the chance of outages, exposures, and breaches.
I’ll suggest how to approach the task, but let’s first cover why these scenarios are so common. In other words, why have cloud networks become so messy in recent years?