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


12 Free, Ready-to-Use Security Tools
Steve Zurier, Freelance Writer,  10/12/2018
Most IT Security Pros Want to Change Jobs
Dark Reading Staff 10/12/2018
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/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
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.