What happens when a dependency changes?

Cloud, software, AI, payments, chips and even domain names depend on other organizations. Explore documented cases where a dependency failed, access changed, infrastructure was withdrawn or organizations had to rebuild capabilities they previously relied on.

Explore what changed
Dependency
Filter by OSAF capability

Loading stories…

← Swipe / scroll to explore →

Different triggers. The same operational question.

The source of change varies. The management test converges on what the organization can still do.

ZTELegal order → critical supply restricted
AnthropicPolicy directive → model access changed
Delta / CrowdStrikeSupplier update → recovery burden concentrated
HuaweiUpstream control → supply options narrowed
SWIFT / IranLegal instruction → financial connectivity withdrawn
Domain controlIdentity layer changed → users lost the normal path

Every dependency story converges on one question

Could the organization still act?

Dependencies are not the problem. Untested dependency is.

OSAF turns external events into a practical management sequence: establish what is true, determine the demonstrated posture, then decide the next action.

Evidence
Posture
Action

Story title

What happened

Who
What
When
Where
Why it matters

Dependency → Trigger → Consequence → Question

    Outcome
    Capability
    Dependency
    Control domains

    Evidence and sources