Silicon Valley Bank
When known vulnerabilities remained unresolved as risk accelerated
The Federal Reserve found management failure, supervisory delay and 31 open safety-and-soundness findings when the bank failed.
Documented impact
Authoritative findings
The documented event
Silicon Valley Bank was closed on 10 March 2023 and the FDIC was appointed receiver. The Federal Reserve found that the bank's board and management failed to manage risk, supervisors did not fully appreciate vulnerabilities as the bank grew, and identified weaknesses were not remediated quickly enough. SVB Financial Group had 31 open safety-and-soundness supervisory findings when it failed, about triple the number at peer firms.
Hypothetical institutional scenario
How might the same control pattern appear?
Risk indicators and supervisory findings accumulate while growth, funding concentration and balance-sheet sensitivity accelerate faster than remediation and board challenge.
Stress-test questions
Questions for challenge and assurance
-
Risk committee
Do unresolved findings change risk appetite and constrain growth?
-
Operations
Is funding and interest-rate exposure aggregated quickly enough for decisions?
-
Audit
Who verifies remediation effectiveness rather than closure paperwork?
NFRisk practitioner interpretation
Control implication
NFRisk view: an issues inventory is not a control outcome. Governance must connect unresolved findings to changing exposure, escalation thresholds and decisions to constrain risk.
Evidence register
Primary and supporting sources
-
US Federal Deposit Insurance Corporation
FDIC Creates a Deposit Insurance National Bank of Santa Clara to Protect Insured Depositors of Silicon Valley Bank (opens in a new tab) 10 March 2023 · Authoritative primary source -
Board of Governors of the Federal Reserve System
Review of the Federal Reserve's Supervision and Regulation of Silicon Valley Bank (opens in a new tab) 28 April 2023 · Authoritative primary source
Publication note
A documented external event—not an NFRisk client engagement.
The named organisations are included because authoritative sources document the event. Their inclusion does not imply that they are or were NFRisk clients, that they endorse this analysis, or that NFRisk participated in the event or response. Framework relevance and NFRisk practitioner interpretation are analytical layers applied after the event.
Return to the Risk Scenario LibraryFrom scenario to mandate
Test the equivalent control assumption in your environment.
NFRisk can use this scenario as a starting point for a focused structural diagnostic, risk-architecture review or delivery-assurance discussion.