~/talk

Effective Handling of Third-Party Supplier Incidents

Talkat BSidesSF 2025 · 2025-04-26..04-27· [security, devops-and-delivery]
links:none on file
slides:none on file

Advocates a concrete process: inventory critical vendors, bind SLAs in contracts, and use tooling that combines contracts, questionnaires and risk scores to prioritize remediation. Cites a Prevalent stat: 61% of organizations saw breaches, a 49% increase. Triggers include threat-intel continuous monitoring that feeds a two-step triage, immediate reactive vendor SAQ, and a severity matrix (P1/P2) that invokes a supply chain risk management committee to approve containment, remediation plans and formal risk-acceptance signoffs.

AI-written summary · about

  1. 0:00Introduction and setup
  2. 1:49About the speaker and topic
  3. 3:13Agenda and problem statement
  4. 5:18Responsibility for third-party incidents
  5. 7:04Role of supply chain management
  6. 8:52Third-party risk management team
  7. 11:45Supplier risk assessments and tooling
  8. 13:49Developing IR runbooks
  9. 15:58Threat intelligence and triage
  10. 17:21Incident analysis and vendor SAQ
  11. 19:05Business relationship officer role
  12. 21:18Containment controls and risk acceptance
  13. 23:07Supply chain risk management committee
  14. 25:35Decision flow for containment
  15. 27:40Risk-based decision criteria
  16. 28:21Vendor non-response handling
  17. 29:25Communication protocols
  18. 30:08Recovery and post-incident steps
  19. 31:15Key takeaways and closing
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.