<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=2975524&amp;fmt=gif">
BLOG

3 Challenges to Consider When Building Your Cloud Security Strategy

September 26, 2019

Cloud Computing strategy

As a result of the widespread adoption of public and private cloud, companies must rethink their network security strategies. While it’s tempting to think that you can just leave cloud security to your cloud provider, it’s too important not to play an active role in securing your resources in the cloud. 

Think of it like this, would you leave your on-prem network security up to the company that physically built your infrastructure? No, you invest in dedicated security tools like NGFWs, IPS, WAFs, and more to secure, detect, and protect your network from intrusion. A similar strategy must be replicated in the cloud.
In order to develop a comprehensive cloud security strategy, there are several challenges that must be overcome. 

Data Breaches

As technology has evolved at a rapid pace, so too has cybersecurity threats. Data breaches are now costing companies on average of $4 million per incident, with the likelihood of a breach evolving from not if you will be breached, to when will it happen? The widespread adoption of the cloud for at least a portion of workloads and storage has expanded the threat landscape. Companies need to take adequate measures to protect their public and private clouds with the same level of security as their traditional data centers. 

New call-to-action

Insider Threats

Employee negligence can be a major risk to network security. While IT teams have trained employees about best practices related to issues like phishing emails and protecting intellectual property with BYOD guidelines, training needs to be revamped with cloud in mind. Lack of end user awareness and training on appropriate cloud security measures will lead to a greater risk of a breach. 

Limited Cloud Visibility

Blind spots have always been an inherent risk for organizations. You don’t know, and can’t protect against, what you can’t see. Companies have been creating network visibility strategies for their on-prem networks for years, comprised of network TAPs, bypass switches, and network packet brokers. Cloud platforms inherently have blind spots, as most traditional visibility tools were not built with cloud in mind. Today there are cloud TAPs that can be used to provide cloud packet visibility to monitoring tools and services to begin eliminating blind spots, and improving overall cloud security.

Developing a comprehensive cloud security strategy won’t happen overnight. It’s important to start documenting what resources you have from your cloud provider and what tools and resources your organization has added. From there you will have a better understanding of the gaps that need to be addressed. 

If lack of visibility into your cloud resources remains an issue, Garland Technology has solutions that can provide packet level visibility to your security and monitoring tools. Contact us today to learn more!

See Everything. Secure Everything.

Contact us now to secure and optimized your network operations

Heartbeats Packets Inside the Bypass TAP

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.

Glossary

  1. 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.

  2. Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.

  3. Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.

NETWORK MANAGEMENT | THE 101 SERIES