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.

Endpoint //


11:00 AM
David Melnick
David Melnick
Connect Directly
E-Mail vvv

Workplace Privacy: Big Brother Is Watching

Companies may have the right to monitor employees who are checking their bank balances or shopping online on corporate networks. The real question is, should they?

The technological sophistication of employee monitoring tools available today gives companies the power to scrutinize virtually every move an employee makes using keyboard logging, cellphone tapping, tracking devices attached to office badges -- even chairs that vibrate when an employee gets up from his or her desk.

To be sure, many of these approaches are extreme. But they all raise ethical issues we’ve never faced before as a society.

Why do companies monitor? One reason, according to a study Kansas State University conducted last year called “The Effects of Sanctions and Stigmas on Cyberloafing,” is that between 60% and 80% of employees’ time on the Internet at work has nothing to do with work. Here are a few other scary stats from the study:

  • 77% of people check their social media profiles from work computers
  • 49% of women shop online at work during the holiday season
  • 20% of men view pornography at work

So, companies monitor. They notify employees and gain consent with strong Acceptable Use Policies (AUPs) and then operationalize increasingly sophisticated rules-based monitoring with Data Loss Prevention (DLP), Deep Packet Inspection of SSL activity, and even spyware.

Of course, companies have the right to monitor what travels over their networks, at least in the US. They have shareholder, customer, and employee interests to protect. In fact, in the US, with limited notification and consent, employers have very few limitations as to what they can monitor around employees’ Internet use at work.

In Europe, privacy is a human rights issue
The right to monitor becomes a bit more complicated for companies operating outside of the US, however. Europe, for example, has worked actively on the issue of governing privacy. The EU Data Protection Directive -- which is in transition at the moment -- provides protections for employees’ personal life in the workplace. The European Convention for the Protection of Human Rights, Article 8.1, proclaims that “everyone has the right to respect for his private and family life, his home and correspondence.”

According to the Article 29 Working Party working document on surveillance of electronic communications in the workplace, “Court has made it clear that the protection of private life enshrined in Article 8 does not exclude the professional life as a worker …” This approach to extending personal privacy protection into the workplace has been migrating to other jurisdictions around the world. For now, most employers outside of Europe can access any email or text message or track employee online activity -- anything that relies on a company asset to travel, unless it’s a personal device -- and limit employees’ expectations of privacy at work.

Whoa! Why are we monitoring, again?
Security professionals are keenly aware of the pressure to secure without consideration for privacy, and monitoring seems to be the tactic du jour. But let’s take a moment to step back and reflect on the implications and realities of monitoring.

We monitor because our networks and our employees are under constant cyberattack and because CIOs and CISOs are attempting to maintain command and control over increasingly distributed corporate networks. Employees have 24/7 access to the corporate network via a variety of personal devices. To achieve security and address liability, employer policies often assert no-employee-right-to-privacy, and they often implement monitoring systems in an attempt to regain control over employee Internet use.

These issues are legitimate, but I’m not sure that the end justifies the means. I think we’re monitoring because we don’t know what else to do, and fundamentally, I think we’re monitoring because we can. It’s time to ask ourselves whether we should.

The heart of the problem is that our personal lives are co-mingled with our work lives. Because we use work devices for personal reasons and personal devices for work reasons, it’s difficult for employers not to invade personal space when monitoring work activity. At the same time, we can and should isolate and protect personal activity and privacy. The debate needs to move beyond "we can" and "we should" to how can we separate and protect personal stuff.

Is there a less invasive approach that benefits us all? Let’s chat about the possibilities in the comments.

David has worked for 25 years with US and global companies, advising them on strategy, risk-based priorities, and effective governance of highly sensitive and regulated data. He is a CIPP/E/US, CISA, and CISSP and has authored several books through McGraw-Hill Publishing and ... View Full Bio
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
11/4/2014 | 4:37:06 PM
Re: trust
It doesn't surprise (or bother) me that 77% of people check their social media profiles from work computers or that 49% of women shop online at work during the holiday season (and probably other times of the year as well.) But 20% of men view pornography at work? Really? Hard to imagine that even the EU would sanction that in workplace privacy laws. 

Thomas Claburn
Thomas Claburn,
User Rank: Ninja
11/4/2014 | 4:04:19 PM
If you can't trust your employees to follow fair and established rules, you've already lost. 
<<   <   Page 2 / 2
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...