Find shared dependencies and correlated failure
Connect vendors to data, identity, infrastructure, integration, knowledge and operating dependencies that can fail together.
Name the dependency
- Identify the shared component and every dependent vendor.
- Record a stable owner and evidence.
Test the failure path
- Define fallback and recovery target.
- A second vendor is not independent when both share the same dependency.
Retain the gap
- Keep missing fallback and untested recovery visible.
- Do not average critical exposure away.
Retain the portfolio record
The Vendor Portfolio Studio keeps vendor evidence, dependencies, renewals, controls and owner decisions connected. It does not renew, replace, terminate, purchase or message.