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


White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
Mueller Probe Yields Hacking Indictments for 12 Russian Military Officers
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/13/2018
10 Ways to Protect Protocols That Aren't DNS
Curtis Franklin Jr., Senior Editor at Dark Reading,  7/16/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-10869
PUBLISHED: 2018-07-19
redhat-certification does not properly restrict files that can be download through the /download page. A remote attacker may download any file accessible by the user running httpd.
CVE-2018-10870
PUBLISHED: 2018-07-19
redhat-certification does not properly sanitize paths in rhcertStore.py:__saveResultsFile. A remote attacker could use this flaw to overwrite any file, potentially gaining remote code execution.
CVE-2018-12959
PUBLISHED: 2018-07-19
The approveAndCall function of a smart contract implementation for Aditus (ADI), an Ethereum ERC20 token, allows attackers to steal assets (e.g., transfer all contract balances into their account).
CVE-2018-14336
PUBLISHED: 2018-07-19
TP-Link WR840N devices allow remote attackers to cause a denial of service (connectivity loss) via a series of packets with random MAC addresses.
CVE-2018-10620
PUBLISHED: 2018-07-19
AVEVA InduSoft Web Studio v8.1 and v8.1SP1, and InTouch Machine Edition v2017 8.1 and v2017 8.1 SP1 a remote user could send a carefully crafted packet to exploit a stack-based buffer overflow vulnerability during tag, alarm, or event related actions such as read and write, with potential for code t...