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.

Analytics //

Security Monitoring

6/28/2013
02:16 PM
Wendy Nather
Wendy Nather
Commentary
50%
50%

Surrendering The Endpoint

Imagine there’s no desktop...

What if you had to design all of your security and monitoring around the fact that it's not your endpoint any more, and it will never be your endpoint again?

Yes, I know there are a few verticals where the security requirements are so stringent this won't be the case; the organization insists on end-to-end ownership along with end-to-end management. But let's all partake of the clue buffet: For the majority of enterprises out there, the ownership and control are going to continue to erode, and it will be harder for security teams to argue that the business should pay for redundant endpoints; the potential capital savings are too great with BYOD. If you're giving your data to a third-party provider already, then why wouldn't you do that on the user end as well?

When you do the thought experiment, a few issues might come to light. One is that if it's not your endpoint, how can you assert the right to monitor it? (NSA jokes can go in the comments section.) Monitoring may have to become more granular. The enterprise could have the right to monitor any interactions involving the infrastructure that it does own: You could watch the traffic from a phone that's hitting your server, but you couldn't watch all the phone's traffic.

If you can't monitor what's actually happening on the endpoint, then it's pretty clear that you need to get your enterprise data off of it. We're seeing more vendors offering "panes of glass" applications that allow a mobile user to view the application that's hosted by the enterprise. In other words, we had a thin client back when it was a Web browser and a Web server. The client got thicker when we developed mobile applications, and now we're putting the client back on a diet because we shouldn't trust the endpoint after all.

The corollary to withdrawing from the endpoint is that you can't trust it any more. Companies that provide applications to customers, such as banking apps, know this all too well. (One figure I've heard is that roughly 25 percent of a bank's customers are accessing its site from an infected endpoint.) The type of monitoring you do has to change. You'll treat the endpoint as potentially hostile; you won't care what happens on it, as long as it behaves itself when it's accessing your resources.

So if you surrender the endpoint, you'll just have to pull your defensive perimeter in tighter. Some say that the app has become the perimeter, some say it's the data, and some claim it's the identity. You'll have to do more behavior monitoring and up-front authentication because you'll have to decide with each session whether to continue to trust that user. Again, this is not news to several industry groups out there. But the very organizations that will benefit most financially from BYOD are probably the ones that still need to learn this and must rearchitect their security accordingly.

Wendy Nather is Research Director of the Enterprise Security Practice at the independent analyst firm 451 Research. You can find her on Twitter as @451wendy. Wendy Nather is Research Director of the Enterprise Security Practice at independent analyst firm 451 Research. With over 30 years of IT experience, she has worked both in financial services and in the public sector, both in the US and in Europe. Wendy's coverage areas ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-23534
PUBLISHED: 2021-02-25
A server-side request forgery (SSRF) vulnerability in Upgrade.php of gopeak masterlab 2.1.5, via the 'source' parameter.
CVE-2021-27330
PUBLISHED: 2021-02-25
Triconsole Datepicker Calendar <3.77 is affected by cross-site scripting (XSS) in calendar_form.php. Attackers can read authentication cookies that are still active, which can be used to perform further attacks such as reading browser history, directory listings, and file contents.
CVE-2021-3124
PUBLISHED: 2021-02-25
Stored cross-site scripting (XSS) in form field in robust.systems product Custom Global Variables v 1.0.5 allows a remote attacker to inject arbitrary code via the vars[0][name] field.
CVE-2021-21064
PUBLISHED: 2021-02-25
Magento UPWARD-php version 1.1.4 (and earlier) is affected by a Path traversal vulnerability in Magento UPWARD Connector version 1.1.2 (and earlier) due to the upload feature. An attacker could potentially exploit this vulnerability to upload a malicious YAML file that can contain instructions which...
CVE-2021-21065
PUBLISHED: 2021-02-25
Adobe Bridge version 11.0 (and earlier) is affected by an out-of-bounds write vulnerability when parsing TTF files that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.