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.

Attacks/Breaches

Breach Awareness Made Easy

100%
0%

What if companies had to disclose breach history in the same way food companies display nutritional information?

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
ODA155
0%
100%
ODA155,
User Rank: Ninja
10/9/2014 | 3:12:02 PM
Re: Security Seals of approval (or disapproval)
I think you're looking for a simple solution to a very complicated problem. So, my question, who explains to the consumer what a CrossSite Scripting attack is... DDoS or SQL Injection?

Instead, I would recommend something like this, although government sponsored. If you want to get people attention they will need to know what you're talking about and if you search this DB you will see the shock value it could have if more people (consumers) were aware of its existance.

 

Chronology of Data Breaches Security Breaches 2005 - Present

https://www.privacyrights.org/data-breach

 
Sara Peters
50%
50%
Sara Peters,
User Rank: Author
10/6/2014 | 2:09:01 PM
Re: Security Seals of approval (or disapproval)
@Marilyn  Definitely hard to argue against more transparency when it comes to breaches. One thing that's going to take some time to do, though, is to educate the general public.so that they'd actually understand what the heck the data meant. Maybe things like "cross-site scripting vulnerabilities" on an app security box would only matter to IT people anyway. But a breach disclosure box for the general public would have to be a bit simpler.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
10/6/2014 | 1:54:21 PM
Re: Security Seals of approval (or disapproval)
That appsec lable, is cool, isn't it? Would be a litte trick to implemment for web apps, to be sure. But it's hard to argue against the idea of more transparency when it comes to breach disclosure.... 
Sara Peters
50%
50%
Sara Peters,
User Rank: Author
10/6/2014 | 12:47:21 PM
Re: Security Seals of approval (or disapproval)
@Marilyn  Ooo I like the OWASP version with app security too. The tricky thing with doing it for Web apps is that you could only focus on the app and not the implementation on the Website, since looking for vulnerabilities on someone else's site is illegal without permission.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
9/29/2014 | 8:02:03 AM
Re: Security Seals of approval (or disapproval)
Agreed, Robert. More so, I think a public disclosure of breach history would put security right where it belongs -- on the front burner of the C-suite which sould give security teams much more clout and visibility for getting the resources they need to be proactive.
Robert McDougal
50%
50%
Robert McDougal,
User Rank: Ninja
9/28/2014 | 1:29:52 PM
Re: Security Seals of approval (or disapproval)
Not only would it make the information more digestable and understandable for consumers, it would additionally drive business away from the poorest performers and shepard business to the most secure companies.   I like it.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
9/26/2014 | 4:27:01 PM
Security Seals of approval (or disapproval)
This isn't totally analagous but Jeff Williams creator of the OWASP Top 10 came up with a similar idea for application security. I'm sure something similar could come be fashioned for data breach disclosure. Check it out: 

on security. Take a look 

 
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 Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3903
PUBLISHED: 2021-10-27
vim is vulnerable to Heap-based Buffer Overflow
CVE-2021-41191
PUBLISHED: 2021-10-27
Roblox-Purchasing-Hub is an open source Roblox product purchasing hub. A security risk in versions 1.0.1 and prior allowed people who have someone's API URL to get product files without an API key. This issue is fixed in version 1.0.2. As a workaround, add `@require_apikey` in `BOT/lib/cogs/website....
CVE-2021-1115
PUBLISHED: 2021-10-27
NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for private IOCTLs, where an attacker with local unprivileged system access may cause a NULL pointer dereference, which may lead to denial of service in a component beyond the vulnerable co...
CVE-2021-1116
PUBLISHED: 2021-10-27
NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer (nvlddmkm.sys), where a NULL pointer dereference in the kernel, created within user mode code, may lead to a denial of service in the form of a system crash.
CVE-2021-1117
PUBLISHED: 2021-10-27
Windows contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape, where an attacker through specific configuration and with local unprivileged system access may cause improper input validation, which may lead to denial of service.