Attacks/Breaches

Breach Awareness Made Easy

50%
50%

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 

 
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
The Fundamental Flaw in Security Awareness Programs
Ira Winkler, CISSP, President, Secure Mentem,  7/19/2018
Number of Retailers Impacted by Breaches Doubles
Ericka Chickowski, Contributing Writer, Dark Reading,  7/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14505
PUBLISHED: 2018-07-22
mitmweb in mitmproxy v4.0.3 allows DNS Rebinding attacks, related to tools/web/app.py.
CVE-2018-14500
PUBLISHED: 2018-07-22
joyplus-cms 1.6.0 has XSS via the manager/collect/collect_vod_zhuiju.php keyword parameter.
CVE-2018-14501
PUBLISHED: 2018-07-22
manager/admin_ajax.php in joyplus-cms 1.6.0 has SQL Injection, as demonstrated by crafted POST data beginning with an "m_id=1 AND SLEEP(5)" substring.
CVE-2018-14492
PUBLISHED: 2018-07-21
Tenda AC7 through V15.03.06.44_CN, AC9 through V15.03.05.19(6318)_CN, and AC10 through V15.03.06.23_CN devices have a Stack-based Buffer Overflow via a long limitSpeed or limitSpeedup parameter to an unspecified /goform URI.
CVE-2018-3770
PUBLISHED: 2018-07-20
A path traversal exists in markdown-pdf version <9.0.0 that allows a user to insert a malicious html code that can result in reading the local files.