Comments
From DevOps to DevSecOps: Structuring Communication for Better Security
Newest First  |  Oldest First  |  Threaded View
tom.gillis
50%
50%
tom.gillis,
User Rank: Author
2/21/2018 | 5:45:09 PM
Is DevSecOps the right answer?
No doubt it makes sense to build apps in a way that a single SEIM can provide a holistic view.  But that's not the entire security story - that's really just consolidatiing the forensics.  As we move into a world with cloud native applications, it is risky to rely on developers to also think about operations AND security.  Is it possible that one person can optimize all three?  Organizations have utilized the seperation of duties model for years for the simple reason that focus and accountability brings results.  Increasing developer awareness of security is of course a good thing and likely to yield some results. But maintaining a strong, independant security team just seems to make sense.  Beyond the org structure, the security tools need to evolve to bring the seperation of duties model to the self service cloud.  Amazon took a big step forward with recent enhancements to their IAM capabilites, segmenting some security functions from day to day dev and ops functions.  But there's still a long way to go for the tools to enforce true seperation of duties.  DevOps yes.  DevSecOps and security is all taken care of?  Doubtful.
roberthawk
50%
50%
roberthawk,
User Rank: Author
2/19/2018 | 6:46:34 PM
Re: SIEM as Hub
In regard to "If change management is central, why are you focusing on the SIEM as central?".  Though the SEIM traditionally has been used as a 'security' device or system, it is evolving into the organizations information systems nerve processing center.  Shipping logs to the SIEM from internal and external systems can be used to detect issues within the network.  The same is true for change management logs.  In effect connecting change management to the SEIM is useful in regard to detecting possible outages that may result due to bad or incorrect changes implemented.  in regard to "DevSecOps should bring together all IT operational teams, not merely orchestrate silo'd security tools."  It is easy to dictate to people the necessity to collaborate and they may try to.  Creating technology bridges across silos may be a great way to start tearing down the silo walls.
GeoffZ290
50%
50%
GeoffZ290,
User Rank: Apprentice
2/15/2018 | 11:02:01 AM
SIEM as Hub
If change management is central, why are you focusing on the SIEM as central? The SIEM focuses on threats, not context. Your CMDB provides risk context including for change management. If you don't know clearly what you are protecting you will focus on threats for which you have no underlying exposure. DevSecOps should bring together all IT operational teams, not merely orchestrate silo'd security tools.


Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
The State of Cyber Security Incident Response
The State of Cyber Security Incident Response
Organizations are responding to new threats with new processes for detecting and mitigating them. Here's a look at how the discipline of incident response is evolving.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3483
PUBLISHED: 2019-03-25
Mitigates a potential information leakage issue in ArcSight Logger versions prior to 6.7.
CVE-2019-3484
PUBLISHED: 2019-03-25
Mitigates a remote code execution issue in ArcSight Logger versions prior to 6.7.
CVE-2019-6240
PUBLISHED: 2019-03-25
An issue was discovered in GitLab Community and Enterprise Edition before 11.4. It allows Directory Traversal.
CVE-2015-3953
PUBLISHED: 2019-03-25
Hard-coded accounts may be used to access Hospira Plum A+ Infusion System version 13.4 and prior, Plum A+3 Infusion System version 13.6 and prior, and Symbiq Infusion System, version 3.13 and prior. Hospira recommends that customers close Port 20/FTP and Port 23/TELNET on the affected devices. Hospi...
CVE-2015-3954
PUBLISHED: 2019-03-25
Hospira Plum A+ Infusion System version 13.4 and prior, Plum A+3 Infusion System version 13.6 and prior, and Symbiq Infusion System, version 3.13 and prior give unauthenticated users root privileges on Port 23/TELNET by default. An unauthorized user could issue commands to the pump. Hospira recommen...