Why DevSecOps Can't Exist Without Observability and AIOps

Logo
Presented by

Stephane Estevez EMEA Product Marketing Director, IT Markets, Splunk

About this talk

One of the essential goals of the DevOps methodology is to establish a more concise approach to software delivery, using a continuous integration/continuous deployment (CI/CD) approach. However, to streamline the cycle you need three additional elements: Security, Observability and AIOps. Since the start of 2020, many businesses have had no choice but to accelerate their digital transformation. Pre-COVID-19, just 18% of customer interactions were digital, which rapidly increased to 55% once the pandemic took hold. Applications have been modernized, and moved to microservices running on containers generating a lot of "unknown unknowns". This is why Observability is a must. Understanding these (now observable) environments is a data intensive exercise that requires artificial intelligence (AIOps), making sense of that data for DevOps, but also ensuring proper compliance and risk management. Join this session to explore the answers to: What are the key components of a DevSecOps architecture? Why is Observability critical for a successful DevSecOps approach? Is Security the fourth pillar of Observability? Why, without AI, is Observability just “data”?
Related topics:

More from this channel

Upcoming talks (0)
On-demand talks (291)
Subscribers (38824)
Splunk helps make organizations more resilient. Leading organizations use our unified security and observability platform to keep their digital systems secure and reliable. Organizations trust Splunk to prevent security, infrastructure, and application issues from becoming major incidents, absorb shocks from digital disruptions and accelerate digital transformation.