Extend Your Incident Response Program to DevOps With Security Automation

Extend Your Incident Response Program to DevOps With Security Automation

One of the biggest challenges facing security teams when it comes to incident response is complexity. The continual growth in volume and severity of cyberattacks has led to increased business process and technical complexity as different threat vectors have required security leaders to purchase point solutions with unique user interfaces, custom APIs and business logic.


According to a recent Enterprise Strategy Group (ESG) study, 35 percent of organizations use 26 or more disparate technologies for security analytics and operations from as many as 13 vendors. Although there have been more efforts by the industry to integrate security tools into a wider framework, this is often very vendor-specific, leaving the burden firmly on the security team. This, in turn, results in manual processes, increasing the room for error and slowing response times. In fact, only 23 percent of organizations cite significant use of automation tools to respond to security incidents, according to a Ponemon Institute report.


This increased sophistication of cyberattacks and data breaches — and the elevated business risk that comes with them — means that incident response is not a problem that can be addressed by security alone. A data privacy breach, for example, may involve security, IT, privacy, legal and PR teams. Challenges facing security teams are no longer confined to security, and thus, require more collaboration with IT and other parts of the organization.


At the same time, the entire IT department is facing similar challenges around complexity: an increase in hybrid multicloud environments, existing and outdated legacy applications, and a lack ..

Support the originator by clicking the read the rest link below.