Cloud

9/14/2017
11:00 AM
Rob Enns
Rob Enns
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Encryption: A New Boundary for Distributed Infrastructure

As the sheet metal surrounding traditional infrastructure continues to fall away, where should security functions in a cloud environment reside?

The public cloud delivers unbundled, distributed infrastructure — compute, storage, and network resources are here for the asking with nothing more than an API call. Platform services like databases are similarly available for developers wanting to consume resources above the infrastructure level. À la carte infrastructure, available self-service to developers, allows for agility and elasticity previously unavailable to enterprise IT.

But as the sheet metal surrounding this infrastructure falls away, so does the physical perimeter of the enterprise data center, leaving distributed infrastructure with no clear boundary. The perimeter has proved a convenient, if not always optimal, spot to insert data center security functions. With it gone, where should security functions reside?

In some cases, the answer is easy. Network segmentation previously provided by physical network subnets has been abstracted in AWS as a virtual private cloud, or VPC. With a simple API call, VPCs are available cheaply and easily.

Other instances aren’t so simple. The AWS object storage service, S3, is one example. The AWS Elastic Block Store volumes, or EBS, are another. AWS allows volumes and S3 objects to be shared between accounts in creative and useful ways, far beyond what their physical analogs could achieve. However, as I've written before, developers frequently misconfigure permissions, making their data vulnerable to loss. As cloud service providers expand the flexibility of their services, complexity and the risk of misconfiguration grow. 

Distributed infrastructure demands distributed security, and the industry is responding. VMware NSX and AWS security groups offer good solutions for network segmentation and firewalling in a homogenous cloud.

While these solutions suffice in single environments, these solutions don't work in hybrid environments, and they become unwieldy at scale. In hybrid environments, routers, firewalls, and the rest function under different controls and different conditions. They don't scale because any policies created — any single configuration — cannot apply across environments.

The rise of distributed infrastructure didn't result only from the rise of cloud, but it is largely attributable to it. With past data centers, the switch or router that forwarded data to the Internet relied on physical boxes (firewalls, load balancers, IDP, etc.) for security services. In today's cloud, virtualized software infrastructure inserts this functionality into every server. Rather than trying to replicate perimeters on infrastructure we don't control, the most logical approach implies securing applications individually — creating a perimeter for every application. The old perimeter has vaporized, but it needs to reappear in this distributed world.

For the new perimeter, the best solution is properly implemented encryption. Encryption allows IT teams to maintain control over assets in environments they don't physically control, especially as those assets become increasingly distributed. Encryption allows IT security to ensure the confidentiality and integrity of enterprise resources in any environment — particularly across the hybrid cloud.

In other words, encryption enables logical control over assets even in the absence of physical control. This logical boundary around enterprise assets is the new perimeter. The enterprise holds the keys, and their assets remain under their control.

With distributed infrastructure as the new normal, the security space is racing to catch up. But to accommodate complexity and scale, we need to adopt a model that attaches "distributed security" to workloads and data rather than replicating traditional data center solutions.

Related Content:

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry’s most knowledgeable IT security experts. Check out the INsecurity agenda here.

Rob Enns joined Bracket Computing from VMware, where he was vice president of engineering in their networking and security business unit. Before joining VMware, Rob was vice president of engineering at Nicira, which was acquired by VMware in 2012. Previously he spent 11 years ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Understanding Evil Twin AP Attacks and How to Prevent Them
Ryan Orsi, Director of Product Management for Wi-Fi at WatchGuard Technologies,  11/14/2018
Veterans Find New Roles in Enterprise Cybersecurity
Kelly Sheridan, Staff Editor, Dark Reading,  11/12/2018
To Click or Not to Click: The Answer Is Easy
Kowsik Guruswamy, Chief Technology Officer at Menlo Security,  11/14/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Online Malware and Threats: A Profile of Today's Security Posture
Online Malware and Threats: A Profile of Today's Security Posture
This report offers insight on how security professionals plan to invest in cybersecurity, and how they are prioritizing their resources. Find out what your peers have planned today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19296
PUBLISHED: 2018-11-16
PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack.
CVE-2018-19301
PUBLISHED: 2018-11-15
tp4a TELEPORT 3.1.0 allows XSS via the login page because a crafted username is mishandled when an administrator later views the system log.
CVE-2018-5407
PUBLISHED: 2018-11-15
Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'.
CVE-2018-14934
PUBLISHED: 2018-11-15
The Bluetooth subsystem on Polycom Trio devices with software before 5.5.4 has Incorrect Access Control. An attacker can connect without authentication and subsequently record audio from the device microphone.
CVE-2018-14935
PUBLISHED: 2018-11-15
The Web administration console on Polycom Trio devices with software before 5.5.4 has XSS.