From DevOps to DevSecOps: Structuring Communication for Better Security
Source – darkreading.com
A solid approach to change management can help prevent problems downstream.
Security has long been considered an afterthought in the software development process, with ad hoc measures typically tacked on just before release. This approach is no longer adequate in sustaining today’s expectations for rapid and reliable service.
DevSecOps is emerging as a superior way to integrate security throughout the DevOps cycles, using better intelligence, situational awareness, and enhanced collaboration. It entails a solid approach to change management, or standardizing specific processes that can help prevent problems downstream. Poor (or no) change management is the biggest culprit in preventing organizations from pinpointing the root cause of critical issues, thereby slowing down the entire business.
Security Incident and Event Management (SIEM)
The key to optimizing your business for DevSecOps is to build the necessary infrastructure to interact with your SIEM system, and enable rapid data collection, data analysis, and incident response. Your SIEM platform should act as the hub, around which you can customize the full workflow for managing incidents.
Having one absolute source of data is crucial; when you rely on spreadsheets that sit on people’s local computers or manual communication mechanisms such as email, information quickly gets old and out of sync. Plus, it’s too difficult to draw meaningful correlations across data sitting in silos. The best incident management solutions can automate moving data between tools, from incident ticketing systems to collaboration tools, system updates, chatbots, and more. Not only do these automation measures save time, they preserve the accuracy of information for all parties involved.
Through descriptive and predictive data mining, machine learning, and simulation, the advanced analytics of SIEM make it easy to visualize and correlate data by mapping previous or pre-categorized events against a
cyber kill chain framework or past events to better support incident investigations.
Of course, not all incidents are equal; you’ll want an analytics-driven platform that gives you the flexibility to categorize the severity of potential threats, as well as provide your entire organization with a “single source of truth” and contextual insight to determine the appropriate response to any event. This includes integrating threat intelligence data, watch lists, correlation rules and queries, and the like.
Let’s take a look at three use cases that highlight the importance of DevSecOps.
1. Internal Communications
The security team for a multinational financial corporation takes down the company’s firewall as part of routine maintenance. In the middle of the night, the application team can see that changes have been made, but because there is no documented, standardized procedure for changing the firewall, they flag it as an anomaly and a possible threat. As they follow protocol to investigate the change, they’re unable to figure out the root cause of the issue, and end up gathering other groups and scrambling to diagnose and fix. By the time they figure out that it’s just a firewall change, the service has been down for more than 12 hours. The teams agree to create a new rule: no firewall changes should be made after hours.
2. Alert Fatigue
The service desk for a large retailer receives alerts of a data breach. Without filters or rules in place, these alerts get lost among the many thousands of notifications the group receives every hour. The major incident alerts go unnoticed, buried under false alarms, automated alerts, and other notifications, preventing teams from acting proactively. Instead, the unsuspecting teams discover the problem days later, and only through the reports of confused customers and partners — not to mention angry executives. The company then has to notify its customers that their personal information may have been compromised, and a protracted public scandal causes its teams to change its major incident processes.
3. Poor Fundamentals
A global credit monitoring agency suffers a data breach but does not realize it for months, and must awkwardly alert its customers long after the fact that their personal information may have been compromised. In the aftermath, the company promotes websites intended to allow users to see whether they are affected by the breach. The agency’s lack of preparation becomes obvious when the websites prove totally ineffective and affected by viruses, making matters worse and causing further embarrassment. The company resolves to completely revamp its approach to security and incident management.
What Should You Do?
The key to achieving a successful DevSecOps implementation is to tackle communication as a core tenet of operations and bring structure to collaboration so that your organization can remain proactive and keep the right people informed of truly relevant information. IT teams tend to be paralyzed with too many alerts and notifications that prevent them from identifying and quickly fixing the important issues. Artificial intelligence-driven event analytics can help turn this data into immediate action and help your business to prioritize the restoration of business-critical services based on real data and not a wild guess. This is the structure and standardization necessary to prevent outages, manage major incidents, and rapidly engage resolution when necessary.