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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Survey: When Leaving Company, Most Insiders Take Data They Created
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Joe Stanganelli
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.
theb0x
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.
RyanSepe
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.
RyanSepe
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.
AndrewfOP
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.
<<   <   Page 2 / 2


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-1142
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
CVE-2023-1143
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
CVE-2023-1144
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
CVE-2023-1145
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
CVE-2023-1655
PUBLISHED: 2023-03-27
Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.