# AIVSS03 - Agent Cascading Failures

> A compromise in one agent propagates and amplifies across connected systems and SaaS integrations.

- **Category**: Owasp Aivss
- **Subcategory**: core_security_risks
- **Canonical URL**: https://designpattern.fyi/owasp_aivss/aivss03_cascading_failures/

---

## Description
'**Intent**: Prevent single-point failures from cascading through interconnected agent systems and integrations.

**Context**: In multi-agent networks, a failure or compromise in one agent can propagate through the system, causing widespread disruption as agents make decisions based on faulty upstream data. This creates a chain reaction across connected SaaS integrations and systems.

**Solution**: Implement circuit breakers between agents. Use bulkhead isolation patterns. Apply timeout limits. Monitor for error propagation. Design for graceful degradation. Implement health checks and automatic recovery. Isolate critical systems from agent failures.'



## Use Cases
Use when designing multi-agent architectures where agents depend on each other for data or task completion.





## Trade-offs


### Advantages

- Limits failure blast radius

- Enables graceful degradation

- Supports system resilience

- Prevents systemic collapse




### Considerations & Drawbacks

- Circuit breakers add complexity

- May cause partial functionality loss

- Recovery orchestration is complex







---
**Reference**: [Original Source](https://aivss.owasp.org/)