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.

Risk

Users Still Careless With Email

Company employees still consistently send confidential and sensitive information via email in violation of rules and regulations, according to a survey by VaporStream.

While not necessarily a surprise, secure email is a huge problem for enterprises. In a survey of how people use email shows that employees may be a bit too loose with their email use when it comes to sensitive and protected information, according to secure messaging service provider VaporStream. Of course, the results play into the services the messaging provider offers, but the results are nonetheless scary for any business--especially those in regulated industries.

For instance, respondents were asked: "Have your or any member of your organization ever sent information via email that was in violation of regulatory compliance?" An unexpectedly high 73.7% of those from companies with 100 or more employees said they did so accidently. Another 28% admitted to doing so intentionally. Smaller businesses faired better, perhaps because many of them escape the regulatory grip. Roughly 25% of those organizations answered yes to "accidentally" or "intentionally."

It also appears "sender's remorse" is a common affliction. About 50% indicated that they have worried about what might happen to emails after they sent them. Around 20% said that emails have "haunted" them after being sent.

A surprisingly low 3 out of 10 respondents said that they send private and confidential business information by email. One would think that figure would be close to 100%.

About 10% of respondents say they have accidently leaked confidential information. And 60% of those surveyed have accidently hit "reply all" when responding to an e-mail.

The question is, after about 40 years of using email, why don't we have a better handle on sharing data more securely with it? Security awareness training might help, but probably not a lot. Some companies may consider sanctioning employees who abuse email by sending regulated information insecurely, while others may let users know that their work emails are monitored.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/2020
4 Security Tips as the July 15 Tax-Day Extension Draws Near
Shane Buckley, President & Chief Operating Officer, Gigamon,  7/10/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
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
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15105
PUBLISHED: 2020-07-10
Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authenticati...
CVE-2020-11061
PUBLISHED: 2020-07-10
In Bareos Director less than or equal to 16.2.10, 17.2.9, 18.2.8, and 19.2.7, a heap overflow allows a malicious client to corrupt the director's memory via oversized digest strings sent during initialization of a verify job. Disabling verify jobs mitigates the problem. This issue is also patched in...
CVE-2020-4042
PUBLISHED: 2020-07-10
Bareos before version 19.2.8 and earlier allows a malicious client to communicate with the director without knowledge of the shared secret if the director allows client initiated connection and connects to the client itself. The malicious client can replay the Bareos director's cram-md5 challenge to...
CVE-2020-11081
PUBLISHED: 2020-07-10
osquery before version 4.4.0 enables a priviledge escalation vulnerability. If a Window system is configured with a PATH that contains a user-writable directory then a local user may write a zlib1.dll DLL, which osquery will attempt to load. Since osquery runs with elevated privileges this enables l...
CVE-2020-6114
PUBLISHED: 2020-07-10
An exploitable SQL injection vulnerability exists in the Admin Reports functionality of Glacies IceHRM v26.6.0.OS (Commit bb274de1751ffb9d09482fd2538f9950a94c510a) . A specially crafted HTTP request can cause SQL injection. An attacker can make an authenticated HTTP request to trigger this vulnerabi...