Incident response is the planned process an organisation follows to detect, contain, investigate and recover from a security incident. It ends with lessons that strengthen defences.
DevSecOps is the practice of building security checks into everyday software delivery. Code, dependencies and infrastructure are tested automatically on every change instead of being reviewed only before release.
Mean time to recovery (MTTR) is the average time it takes to restore a service after a failure or incident begins. It shows how quickly a team detects, responds to and fixes problems.
SIEM, or security information and event management, is a platform that collects and correlates logs from many systems to detect threats. It also supports investigations and compliance reporting.
An incident postmortem is a written review held after an outage or serious failure. It records what happened, why it happened and how the response went, then commits to specific changes that make a repeat less likely.
An on-call rotation is a schedule that assigns engineers, in turn, to respond to production alerts and incidents outside or during normal hours. Someone is always available to restore service.
A clear proven process, that delivers
You've seen our ideas - now go deeper.
Discover more insights, guides, and engineering practice.