Comments
'Shift Left': Codifying Intuition into Secure DevOps
Newest First  |  Oldest First  |  Threaded View
KevGreene_Cyber
50%
50%
KevGreene_Cyber,
User Rank: Author
1/13/2018 | 2:41:51 PM
Re: Design-time Security Engagement: Still Coming
Yes, this isn't an new problem. I wanted to present the issue in a way to get developers and security folks to think differently about software security; especially with the rise of DevOps and the ongoing issues with security tools clogging up CI pipelines. Do it early and do it often is the name of the game. Thanks for commenting and reading the article.
Brook S.E.S308
50%
50%
Brook S.E.S308,
User Rank: Apprentice
1/10/2018 | 8:00:43 PM
Design-time Security Engagement: Still Coming
As I point out in the intro to my last book, Securing Systems, the first standards reference to design-time security requirements that I managed to find was NIST 800-14, 1996! My chapter in Core Software Security describes early aat inception engagement followed by full participation in creation of the the structure (architecture) that will be built.  Of course, IEEE Center For Secure Design's "Avoiding The Top 10 Security Design Flaws" reiterates the same message (I'm a co-author). 

Talking about early engagement for security requirements is not new. It amazes me that we have to keep reiterating this as though it were something new. Why? because such engagements are still too rare, unfortunately. 

Still, within the 4 security architecture practices that I've lead, we have achieved early engagment. Part of whatever success I and my teams have enjoyed has depended upon security people becoming fulll participants in the entire development process. When seen as a key subject matter expert (SME) develop teams are quick to integrate their security members right from inception. I call it, "developer-centric security".

As I've become more involved in DevOps (as I spoke about at RSA SF '16), it's become clear to me that just as the software/system needs security architecture, so does the DevOps chain, as early as possible: same deal.

the problem with DevOps is that it often begins organically as experiments. But the tipping point to production and canonization, architecting DevOps with security deeply engaged has the promise of fulfilling the "shift left" imperative.

/brook schoenfield


How the US Chooses Which Zero-Day Vulnerabilities to Stockpile
Ricardo Arroyo, Senior Technical Product Manager, Watchguard Technologies,  1/16/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3906
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 contains hardcoded credentials in the WCF service on port 9003. An authenticated remote attacker can use these credentials to access the badge system database and modify its contents.
CVE-2019-3907
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 stores user credentials and other sensitive information with a known weak encryption method (MD5 hash of a salt and password).
CVE-2019-3908
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 stores backup files as encrypted zip files. The password to the zip is hard-coded and unchangeable. An attacker with access to these backups can decrypt them and obtain sensitive data.
CVE-2019-3909
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 database uses default credentials. Users are unable to change the credentials without vendor intervention.
CVE-2019-3910
PUBLISHED: 2019-01-18
Crestron AM-100 before firmware version 1.6.0.2 contains an authentication bypass in the web interface's return.cgi script. Unauthenticated remote users can use the bypass to access some administrator functionality such as configuring update sources and rebooting the device.