Skip to main content

Cascading failure

A failure in which an initial disturbance at one subsystem propagates through one or more tightly coupled interfaces to affect additional subsystems, with each step reinforcing rather than containing the original disturbance, often driven by an unrecognized positive feedback loop running across interfaces that were never isolated from one another. (see Topic 3.6) treats cascading failure design in depth.

Defined in 4 GAGE programs, which carry 4 distinct definitions of it. The wording above is taught in Engineering Judgment and Professional Formation.

How each discipline defines it

The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.

Engineering Judgment and Professional Formation

A failure in which an initial disturbance at one subsystem propagates through one or more tightly coupled interfaces to affect additional subsystems, with each step reinforcing rather than containing the original disturbance, often driven by an unrecognized positive feedback loop running across interfaces that were never isolated from one another. (see Topic 3.6) treats cascading failure design in depth.

Certified AI Governance Professional (CAIGP)

A failure pattern in which one component's outage produces stress or failure in a dependent component, often surfacing as an outage that appears larger or more widespread than its original trigger.

Certified AI Practitioner: Workplace Foundations

OWASP's ASI08; a wrong or malicious agent action that propagates through a multi-step workflow or multi-agent system with escalating impact. The Snowball leg of REINS.

Certified Agentic AI Governance Professional (CAAGP)

a failure at an early step in a multi-step workflow that propagates, uncaught, through later steps rather than being detected and corrected.

Where it is taught

The exact lessons this term appears in. The first module of every program is free with a free account.

Where it shows up at work

A definition is where Cascading failure starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.

Plans for a vendor failure, an unsafe model change or a suspended service: rollback, manual fallback, data export and safe decommissioning.

One lesson on this page teach it as a primary outcome.

AI security fundamentalsSecurity and Resilience

Understands prompt injection, data poisoning, model theft, insecure integrations and excessive agent privileges, and the controls that reduce each.

One lesson on this page teach it as a primary outcome.

Designs tests for factuality, robustness, fairness, safety and abuse resistance with rubrics, baselines and thresholds, and says what a score misses.

One lesson on this page teach it as a primary outcome.

Roles that hire for it

Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.

How job descriptions say it

Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.

“business continuity”“exit plan”“ai security”“prompt injection”“data poisoning”“model theft”

Where the frameworks place it: DORA; NIS2; NIST AI RMF MANAGE 4; OWASP Top 10 for LLM Applications.

One interview question about it

Your AI vendor shuts down next month. What was in your continuity and exit plan, and what did you fail to plan for?

Asked of candidates for ai resilience, continuity and exit planning. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.

If you come from another field

Some backgrounds already carry this competency, and the readiness check gives credit for it.

Terms it appears with

Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.