With each passing year, mobile- and cloud-based services are further supplanting the customer-premise equipment (CPE) standard.
This leads to two major challenges for network engineers.
The first is infrastructure. More and more people are using the cloud, but more than that, people are using more and more devices to access the cloud—usually without a wired connection. More and more mobile devices will require more and more infrastructure to support, monitor, and maintain.
The second challenge is information security. By end of the year, planet earth will exceed a new record for the amount of data which has been transmitted across it. Some of that data will be yours, and much of it will be valuable. When your first priority is increasing your users’ access to vast volumes of data, how will you task your second priority, which is keeping that data out of the hands of others?
Like they used to say, “knowing is half the battle.” Simply knowing what you’re in for is going to go a long way towards helping you prepare for what’s coming. So, with that said, here are our best guesses for the ongoing evolution of the cloud.
According to a research document from Cisco, entitled “The Zettabyte Era” a number of key trends will emerge by 2020 and directly impact network engineers
The implications of the cloud transition are especially pertinent for the information security industry: according to researchers at IHS, 54% of security services are delivered through CPE, with the remaining 46% coming through the cloud. By 2020, the firm predicts that those two numbers will flip in favor of cloud delivery.
Over that period, Allied Market Research anticipates that the global market for cloud security will reach $8.9 billion in revenue. However, experts anticipate that the continued advance of the cloud era will pose significant challenges on the security front.
Looking ahead to 2020, Gartner's position is that “95% of cloud security failures will be the customer's fault.” The expanded agency of the customer in cloud spaces, then, is very much a double-edged sword. This makes for a strange frontier, in that firms will need to account for end-user vulnerabilities that, in any previous era, would not have been considered to be the service vendor's problem.
It all serves to prove, then, that companies looking to push the cloud envelope must have all their bases covered. Either they need to build in a strong SOC, or partner with a company that can provide them with robust security tools. As an example of the latter, let’s take a look at a Garland technology partner, Imperva.
Imperva is an industry leader in the era of cloud security. Imperva's services cut out threats—including those originating from inside the network—and protect proprietary data by plugging up the security gaps that are inevitably created when businesses shift their pre-existing services from on-premises to the cloud. When it's time to perform maintenance or upgrade hardware, Garland's bypass network TAPs can switch an Imperva system on- or off-line in real time.
If you want to learn more about how to improve your network design for better cloud security, download our free white paper, Optimizing Network Design in Security Projects.
If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.
If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.
While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.
Some of you may have noticed a flaw in the logic behind this solution! You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.
Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.
Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.
Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.