Systemic and correlated risk
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
find risks that sit between teams.
Planned topics
- Correlated failure: one cause hitting many services (shared database, certificate, DNS, vendor).
- Concentration: one team or one person that everything depends on; knowledge silos.
- Find them by mapping dependencies and reading incident histories for common causes.
- Reduce them with redundancy, diversity, decoupling, or shared ownership.
Draft outline details
Demonstration
a matrix of services against shared dependencies (identity provider, message broker, certificate authority, cloud region, one on-call engineer) with the heaviest columns highlighted.
Check your understanding
Name two kinds of systemic risk that are not technical components.
Show answer
A single team everything depends on; a knowledge silo.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.