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.

Perimeter

7/23/2012
12:31 PM
Wendy Nather
Wendy Nather
Commentary
50%
50%

The Mobile Monitoring Mess

Bringing your own device to work sounds peachy to employees, but security, regulatory, and privacy issues still need to be worked out on the monitoring side

At what point did “their device” become “my device”? Probably as soon as I started taking personal calls on the brick I called a mobile phone around 1990. I never saw a bill because my employer was paying for every call -- even the international ones where I had to talk to a non-native English speaker in a loud data center on another continent through a reboot and fsck while at the same time navigating the Chicago freeway system. Good times.

I went through any number of personal digital assistants -- Palm, Casio, Sharp Zaurus -- because it was just so easy to keep all of my work appointments and contact numbers in them. Email clients were cumbersome to use back then, so the amount of work-related data I had on them was minimal, even though the fact that I was meeting with particular people might have been considered confidential. There was no thought of segregating the personal, especially when I had work reasons to be sending SMS messages to a friend while on a business trip.

However, things became a lot more voluminous once I started receiving work email on a BlackBerry. Email is the virtual file cabinet for a lot of people; that’s often where the gold is. The device (paid for by me) became a de facto business data repository, just as much as the servers in the data center. And that’s when the issues bubbled up: Is the data still subject to legally mandated retention schedules? Is it searchable in response to a required Public Information Act request? Can my employer search it without my knowledge or consent in the course of an investigation? Could I be forced to have it wiped if the device were stolen?

Ironically enough, the creation of mobile device management (MDM) and other network-based mobile security solutions made the question even bigger. Because many of those require the mobile device to send all of its traffic through an enterprise-owned proxy, this meant that all network activity -- including off-hours browsing -- could be logged by my employer. Should they be logging my personal activity? Should they be forcing it to comply with their enterprise policies? (I like going to Mabel’s 4chan Politically Incorrect Adult Exotic Yarn World as much as the next guy.)

In other words, this mobile device monitoring issue has always been lurking in the background. It just got worse as more functions became possible: the increased storage of data and the expanded ability to manage communications. In countries where data privacy laws are so strict that you can’t collect login events for your employees, this may actually tame the problem better than in places where privacy regulations are still undefined. When the policies have to be defined by the organization, vetted by legal and human resource experts, and communicated to staff, there is a lot of room for error and expensive misunderstanding.

Your monitoring policies have to strike a balance among any regulatory compliance, your security risk management, and your attitude toward your employees. Policies to protect the privacy of users should be independent of who paid for the smartphone. And it should be consistent across all IT assets because the enterprise isn’t based on box ownership anymore. The enterprise is an abstract operation that involves the manipulation of certain types of data in a business context. Don’t let the mobile angle fool you too much into treating those endpoints differently from the ones you have sitting in the office. Monitoring is monitoring, no matter where or how it happens.

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
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Russian Military Officers Unmasked, Indicted for High-Profile Cyberattack Campaigns
Kelly Jackson Higgins, Executive Editor at Dark Reading,  10/19/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-24847
PUBLISHED: 2020-10-23
A Cross-Site Request Forgery (CSRF) vulnerability is identified in FruityWifi through 2.4. Due to a lack of CSRF protection in page_config_adv.php, an unauthenticated attacker can lure the victim to visit his website by social engineering or another attack vector. Due to this issue, an unauthenticat...
CVE-2020-24848
PUBLISHED: 2020-10-23
FruityWifi through 2.4 has an unsafe Sudo configuration [(ALL : ALL) NOPASSWD: ALL]. This allows an attacker to perform a system-level (root) local privilege escalation, allowing an attacker to gain complete persistent access to the local system.
CVE-2020-5990
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in the ShadowPlay component which may lead to local privilege escalation, code execution, denial of service or information disclosure.
CVE-2020-25483
PUBLISHED: 2020-10-23
An arbitrary command execution vulnerability exists in the fopen() function of file writes of UCMS v1.4.8, where an attacker can gain access to the server.
CVE-2020-5977
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in NVIDIA Web Helper NodeJS Web Server in which an uncontrolled search path is used to load a node module, which may lead to code execution, denial of service, escalation of privileges, and information disclosure.