Module 10 of 10

Monitoring, Incident Response & Compliance

Lessons

About This Module

No set of preventive controls is perfect, so the last part of DevSecOps is knowing what is happening in production and being ready when something goes wrong. Monitoring shows you unusual activity as it happens, a tested incident response process keeps you calm and organized during an attack, and compliance shows others that your controls are real and working.

You'll start with security monitoring, including how logs are collected and analyzed in a SIEM. Then you'll learn the incident response lifecycle, from preparation through to lessons learned, and finish with compliance, using SOC 2 as an example of how frameworks turn security practices into something that can be audited.

This is the final module of the course. Once you have finished it, you can put everything together in the Projects section, where you apply what you have learned to build real DevSecOps work.

Lessons

4 videos
01

DevSecOps: Security, Monitoring, and Governance

An episode from Microsoft's AZ-400 DevOps series on security monitoring and governance in a DevSecOps workflow.

02

How SIEM Works

What a SIEM is and how security teams use it to monitor logs, detect threats, and investigate alerts.

03

Incident Response Lifecycle

The stages of incident response explained one by one, from preparation through to lessons learned.

04

SOC 2 Compliance Explained

An overview of SOC 2 compliance, why it matters to organizations, and the five trust services criteria it covers.