Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Shared Dependencies, Shared Risk

Shared Dependencies, Shared Risk

A practical briefing on shared dependencies, risk aggregation and defensible management decisions. Through a fictional service scenario, these 12 slides show how a single identity dependency can connect apparently separate risks, why ordinal scores should not simply be added, and how to document evidence, treatment choices and review triggers.

By Manfredi Marrocco — Cybersecurity, GRC and IT Governance.
https://manfredimarrocco.blog/

Technical reference: https://csrc.nist.gov/pubs/ir/8286/c/r1/final

Manfredi Marrocco

November 13, 2026

Transcript

12 slides
  1. CYBERSECURITY & GOVERNANCE | Shared Dependencies, Shared Risk | A

    practical briefing for security, risk and business teams | Manfredi Marrocco · 1
  2. INSIGHTS / GRC | A portfolio blind spot | Several

    local risks may share a dependency. A green register does not by itself describe the combined scenario. | Manfredi Marrocco · 2
  3. INSIGHTS / GRC | Start from an objective | Choose

    a critical outcome such as fulfilling customer orders. Map the people, services and partners that enable it. | Manfredi Marrocco · 3
  4. INSIGHTS / GRC | A fictional example | An order

    platform, external support and warehouse access depend on one identity service. This is an illustration, not a client assessment. | Manfredi Marrocco · 4
  5. INSIGHTS / GRC | Map the pathway | Identity disruption

    → responders lose normal access → support and order processing are delayed. Verify every proposed dependency. | Identity failure | → | Responder access | → | Service impact | Manfredi Marrocco · 5
  6. INSIGHTS / GRC | The limits of scores | Ordinal

    scores do not automatically support arithmetic. Teams may use different time horizons or count the same loss twice. | Manfredi Marrocco · 6
  7. INSIGHTS / GRC | Separate scenarios | Common cause, direct

    propagation and coincident events are different relationships. State which one the analysis describes. | Manfredi Marrocco · 7
  8. INSIGHTS / GRC | Identify possible treatments | Compare resilience

    measures against the scenario: redundancy, independent recovery access and supplier participation. | Manfredi Marrocco · 8
  9. INSIGHTS / GRC | Assess trade-offs | A second application

    can share the original identity dependency. An emergency route adds privileges and needs governance. | Manfredi Marrocco · 9
  10. INSIGHTS / GRC | Record the choice | Document owner,

    assumptions, available evidence, residual uncertainty and a review trigger. | Manfredi Marrocco · 10
  11. INSIGHTS / GRC | Review after change | A new

    supplier, architecture or test result can alter the dependency. Update the decision when material assumptions change. | Manfredi Marrocco · 11
  12. INSIGHTS / GRC | Sources and attribution | Source: Four

    Green Risks and One Shared Failure — WordPress ID 575, scheduled 5 June 2027. | https://csrc.nist.gov/pubs/ir/8286/c/r1/final | Manfredi Marrocco · manfredimarrocco.blog | Manfredi Marrocco · 12

More Decks by Manfredi Marrocco

Other Decks in Technology