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
The Truth About DLP & SIEM: Its A Process Not A Product
Newest First  |  Oldest First  |  Threaded View
media@bryansimon.pro
50%
50%
[email protected],
User Rank: Author
9/15/2015 | 12:55:57 PM
Re: Under-utilization of DLP and SIEM
I think the issue again is that even if we were to call it a product that requires a process, we still miss entire portions of our organizaton that has data that needs to be secured from loss. DLP isn't just our digitial data, but also, as a very simple example, data in printed form. Data in printed form is also in scope for protection. We have several public high profile examples of where individuals have carried sensitive information (paper documents) out of an organization, that needed to be protected in both digital and printed form.

Thanks for the good comments!
media@bryansimon.pro
50%
50%
[email protected],
User Rank: Author
9/15/2015 | 12:51:12 PM
Re: Under-utilization of DLP and SIEM
You are exactly correct with your statements. That was why I decided to write the article. The article was written to point out that these activites are attempted to be done with technology only, which isn't possible. And further, the technology cannot do the 'process' driven portion of the work required to have a succesful implementation.
Dubai_eye
50%
50%
Dubai_eye,
User Rank: Apprentice
9/13/2015 | 1:46:31 AM
Re: Under-utilization of DLP and SIEM
An interesting article, not sure your argument applies to SIEM as the 'process' (more of a service) is only found inside technology. Moreover the process is provided with matromony of people with technology.

A more apt example than DLP or SIEM process would be vulnerability management. Many vendors proclaim that the service resides on a device which scans your network. However, we know that finding technical vulnerabilities stretches further than seeing which server needs the latest patch or not. 

I agree that understanding what data is important is the first initial step, (then regularly refreshing) is important but I view this as a parallel activity and of which the processes are dependent upon. Finding out what is important, classifying it and safeguarding it are more GRC activities than technical ones.  
mattwilliamsfromseattle
50%
50%
mattwilliamsfromseattle,
User Rank: Apprentice
9/11/2015 | 8:09:52 PM
Under-utilization of DLP and SIEM
It seems that the inability to recognize these "products" as process, or maybe it would be fair to call them a product that requires a process, results in them sitting on the shelf, and not being deployed to their full potential. This seems to be especially true for DLP. There seems to be a large challenge for organizations who are working with an older security system. This is where newer organizations in some ways have an advantage that they are starting from scratch, and can make sure to use best practices from the outset.


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
How Data Breaches Affect the Enterprise
Data breaches continue to cause negative outcomes for companies worldwide. However, many organizations report that major impacts have declined significantly compared with a year ago, suggesting that many have gotten better at containing breach fallout. Download Dark Reading's Report "How Data Breaches Affect the Enterprise" to delve more into this timely topic.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-4020
PUBLISHED: 2021-11-27
janus-gateway is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE-2021-23654
PUBLISHED: 2021-11-26
This affects all versions of package html-to-csv. When there is a formula embedded in a HTML page, it gets accepted without any validation and the same would be pushed while converting it into a CSV file. Through this a malicious actor can embed or generate a malicious link or execute commands via C...
CVE-2021-43785
PUBLISHED: 2021-11-26
@joeattardi/emoji-button is a Vanilla JavaScript emoji picker component. In affected versions there are two vectors for XSS attacks: a URL for a custom emoji, and an i18n string. In both of these cases, a value can be crafted such that it can insert a `script` tag into the page and execute malicious...
CVE-2021-43776
PUBLISHED: 2021-11-26
Backstage is an open platform for building developer portals. In affected versions the auth-backend plugin allows a malicious actor to trick another user into visiting a vulnerable URL that executes an XSS attack. This attack can potentially allow the attacker to exfiltrate access tokens or other se...
CVE-2021-41243
PUBLISHED: 2021-11-26
There is a Potential Zip Slip Vulnerability and OS Command Injection Vulnerability on the management system of baserCMS. Users with permissions to upload files may upload crafted zip files which may execute arbitrary commands on the host operating system. This is a vulnerability that needs to be add...