Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Network Security

10/31/2017
11:45 AM
Patrick Foxhoven
Patrick Foxhoven
News Analysis-Security Now
50%
50%

A New Fence: The Software-Defined Perimeter

The network perimeter is dead: Long live the new perimeter! The boundary of your enterprise network can now be defined by software – but is that the right answer for your organization?

In today's digital environment, the user experience is everything. Thanks to the anytime/anywhere access they've come to expect from consumer apps on tablets and smartphones, workers want the same no-fuss experience in their business applications. They don't want anything to change because they're out of the office or using a phone, compared to being at their desks.

Add in the need for speed, and you can see why businesses are embracing the flexibility and agility of the cloud. But with more and more applications moving off the corporate network, and more employees working remotely, you're faced with a challenge: the systems designed to securely connect those users to their apps are ineffective in the cloud. In fact, they're practically irrelevant.

Let's look at how businesses offer secure remote access. Whether your apps are in the data center or cloud, users access them using 20-year-old virtual private network (VPN) technology. (VPNs were never meant to connect users to applications –- they were intended to connect networks to networks.) The problem is that bringing users from a remote network (via the Internet) onto a trusted or secure network just to access an application within is inefficient at best, and risky at worst.

If you grant outside users access to your network by way of a VPN, you are significantly broadening your attack surface and elevating risk. A partner or employee whose system has been compromised can infect your network, and malware can then move laterally, scanning for other resources and other vulnerabilities to exploit.

For example, we've all seen what happens when a remote user is compromised and they connect back to a network that has lateral access to a credit card payment processing environment or can communicate with sensitive back end financial systems. These types of breaches can, and have, put companies in the headlines and cost them fortunes.

In addition, many companies use a VPN to secure access to applications that are not even in the data center; instead, they've migrated to an infrastructure-as-a-service (IaaS) provider like AWS or Azure. To make this access possible, traditional VPNs require painful, hairpin-type traffic routing that moves traffic from the user to the corporate data center where the VPN concentrator is and out via another VPN to the IaaS provider before making its return trip back to the user. It's a slow and miserable experience for the user, an ongoing challenge for the administrator, and an expensive piece of technology that raises security concerns of its own.

Traditional VPNs are laborious, requiring users to take different actions depending on where they are and what applications they are accessing. Some examples are:

  • When outside the office, users must connect to a VPN before attempting access to applications, but when inside the office there's no need to connect.
  • Or, a user may attempt to access an application from a tablet, but is denied because there is no VPN client configured on the device.
  • Then there is the issue of a network that they are connecting from simply not supporting the communication requirements (ports and protocols) for a corporate VPN.
  • Sometimes the VPN doesn't work.
  • Sometimes users just need more. A very common scenario is clicking on a link within a corporate email account only to have the page that was attempted to load not work because they aren't on the corporate network and it's not something that is exposed externally.

Defining the perimeter differently
It's no longer enough to create a secure perimeter around your network assets. You need to flip the security model, basing it not on the location of the network but on policies tied to the user and application. This approach lets you provide fast, secure and efficient access that connects the right user to the right app, so you're not exposing your network and internal users to risk. With direct access to the applications needed, you're also providing a far superior user experience.

We can no longer risk the security of our networks by using outdated, inefficient and ineffective methods that don't adapt to new technological realities. Software-defined perimeters (SDP) offer a way of keeping networks safe and agile, while keeping employees satisfied and productive and helping you meet desired business outcomes.

Please join us for the remainder of this series on the software-defined network. In the following weeks, we'll offer insights on application "invisibility," using the Internet as a secure network and application segmentation without network segmentation. (For more insights on the SDP approach, check out the Cloud Security Alliance's SDP Security Model.)

Related posts:

— Patrick Foxhoven is CIO and VP of Emerging Technologies at Zscaler.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...