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.

Comments
Survey: When Leaving Company, Most Insiders Take Data They Created
Oldest First  |  Newest First  |  Threaded View
Page 1 / 2   >   >>
AndrewfOP
50%
50%
AndrewfOP,
User Rank: Moderator
12/23/2015 | 2:20:16 PM
Confidentiality Agreement Documentation
What I am curious about is: what is the percentage of those surveyed that have signed a confidentiality agreement?  Granted, having papers signed, people following the agreement and subsequent enforcements/lawsuits are different things, but signing a document using pen with your name on it always signals significance.  Just having a policy without enforcements, or some easily ignored pop-up warnings are hardly sufficient, which is what I suspect are the practice of the companies that people in the survey worked for.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
12/23/2015 | 2:36:06 PM
DropBox and Google Drive are free and easy to obtain.
Two points. First, file sharing services can be blocked via security tools such as web security or implementing a CASB.

Second, I feel like it could be argued that not everything created at a company is that company's property. If that is built into the company's policies then fine, but I think we need to revisit these policies. As it pertains to IP, documentation created specifically for the company or tools created to handle explicitly proprietary data, etc, then I believe it is wrong to take with you.

But for example what about a powershell script written to grep data you need from a Microsoft tool? Or perform certain actions that may be business agnostic. I feel like there are some shady areas here as it does not pertain specifically to company data.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
12/23/2015 | 2:38:25 PM
Re: Confidentiality Agreement Documentation
Agreed, without a process to follow you will have a hard time changing the outlook and behavior of the employee.
theb0x
100%
0%
theb0x,
User Rank: Ninja
12/26/2015 | 10:25:31 AM
Re: Confidentiality Agreement Documentation
It's not just a signed Confidentiality Agreement by all employees that is needed. This also falls under an Acceptible Use Policy. Keep in mind that the employee is most likely performing their job functions on company provided computer equipment and network. Therefore any electronic storage or transmission of any data is the sole property of that company. The systems and networks are solely to be used for business purposes only in serving the best interest of the Company in the course of normal operations.

As far as proprietary information, this would require a well defined Data Protection Policy and you may access/use/share proprietary company information only to the extent it is authorized and necessary to fulfill the employees assigned job duties.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
12/27/2015 | 2:08:01 PM
For decades
Of course, this has been the standard practice by exiting employees for decades, well before the Worldwide Web.  The technology is simply different.  These are good suggestions, but good employee relations and reasonable employee monitoring remain best practice.
Joe Stanganelli
0%
100%
Joe Stanganelli,
User Rank: Ninja
12/27/2015 | 2:11:31 PM
Re: Confidentiality Agreement Documentation
Acceptable Use Policies and the like will inform, but in general simply storing something on a company server will not make it the company's property. (Otherwise, AOL Instant Messenger would have become open source 12 years ago!) *Creating* it with company equipment while at work, however, can be a different story.
theb0x
100%
0%
theb0x,
User Rank: Ninja
12/28/2015 | 10:32:23 AM
Re: Confidentiality Agreement Documentation
True, an Acceptable Use Policy will not stop an employee's actions whether they be intentional or unintentional. However, this can and will be grounds for immediate termination of employment if enforced appropriately.

I am referencing to electronic data created/stored that pertains to one's job function in best interest of the Company. And if it wasn't something an employee created that does not give them the right exfiltrate data on the Company's equipment or network after being discharged and then escorted off the premises. If an employee is being terminated all accounts are to be frozen and their electronic equipment should be physically seized immediately. Clearly you do not have application white listing in place if you and or your employees are installing AOL Instant Messenger. Although it is not supported anymore the TOC and TOC2 protocol was open source by AOL.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/28/2015 | 2:22:12 PM
Data or insights?
I would doubt that anybody individually would own the data in an organization, it will be like customers' data being taken and released to other companies no customers would like that. If it is insights gained from data then I would think the person who created the insights would own it and he/she can take it, if it is not directly related with the customers I would say.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/28/2015 | 2:24:25 PM
Re: Confidentiality Agreement Documentation
That is something certainly interesting to know. The norm is that you do not take company's customer list and share with somebody else. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/28/2015 | 2:30:24 PM
Re: DropBox and Google Drive are free and easy to obtain.
It can be blocked but you need tools and services for that. Some companies do not want to restrict employees' options to use personal email at work, that that creates a risk of losing data without knowing it of course.
Page 1 / 2   >   >>


COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/13/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/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-2019-20907
PUBLISHED: 2020-07-13
In Lib/tarfile.py in Python through 3.8.3, an attacker is able to craft a TAR archive leading to an infinite loop when opened by tarfile.open, because _proc_pax lacks header validation.
CVE-2020-14174
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to view titles of a private project via an Insecure Direct Object References (IDOR) vulnerability in the Administration Permission Helper. The affected versions are before version 7.13.6, from version 8.0.0 before 8.5....
CVE-2019-20901
PUBLISHED: 2020-07-13
The login.jsp resource in Jira before version 8.5.2, and from version 8.6.0 before version 8.6.1 allows remote attackers to redirect users to a different website which they may use as part of performing a phishing attack via an open redirect in the os_destination parameter.
CVE-2019-20898
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to access sensitive information without being authenticated in the Global permissions screen. The affected versions are before version 8.8.0.
CVE-2019-20899
PUBLISHED: 2020-07-13
The Gadget API in Atlassian Jira Server and Data Center in affected versions allows remote attackers to make Jira unresponsive via repeated requests to a certain endpoint in the Gadget API. The affected versions are before version 8.5.4, and from version 8.6.0 before 8.6.1.