15.4 Stress Testing
Key Takeaways
- Stress testing explores severe but plausible scenarios that statistical VaR may understate because of short samples, normality assumptions, or broken correlations
- Enterprise-wide stress tests integrate market, credit, liquidity, and OpRisk effects on capital and earnings, unlike siloed desk-level shocks
- Stressed VaR and stressed ES re-estimate risk using a stressed window or stressed parameters; reverse stress testing works backward from a failure outcome to identify scenarios that breach viability
- Boards set appetite and challenge results; senior management owns the program; audit and independent validation provide assurance
- Basel stress-testing principles emphasize governance, proportionality, meaningful scenarios, robust infrastructure, and use of results in risk management—not a check-the-box exercise
Stress Testing
Stress testing asks what happens to earnings, capital, liquidity, and franchise value under severe but plausible shocks—and under structural breaks that historical VaR windows may never have sampled. VRM–8 connects rationale, enterprise-wide design, stressed risk measures, reverse stress tests, governance, and Basel’s high-level principles.
Why Stress Test?
Day-to-day risk metrics (VaR, sensitivities, ratings-based credit capital) are calibrated to recent history and model assumptions. They can fail when:
- Correlations spike toward 1 in crises (diversification vanishes).
- Liquidity evaporates and exit assumptions break.
- Nonlinear products gap through hedges.
- Credit migrations and defaults cluster far beyond mean EL.
- Operational or conduct events coincide with market stress.
Stress testing is therefore a complement, not a replacement: it explores joint tails, management actions, and capital trajectories that a single 99% one-day VaR number cannot show. Supervisors also use stress tests as a macroprudential and microprudential tool (e.g., CCAR/DFAST-style exercises in the U.S., EBA/ECB EU-wide tests, Bank of England ACS)—FRM expects conceptual familiarity, not jurisdiction-specific form trivia.
Enterprise-Wide Stress Versus Other Measures
| Tool | Typical scope | Question answered |
|---|---|---|
| Desk VaR / limits | Trading book factors | Local P&L sensitivity to market moves |
| Credit EC / IRB | Credit portfolio | Capital for default/migration risk |
| Liquidity ratios / LCR-NSFR style metrics | Funding & HQLA | Survival under runoff assumptions |
| Enterprise-wide stress test | Firm P&L, RWA, capital, liquidity together | Can the firm survive a multi-risk scenario path? |
Enterprise-wide stress testing links macroeconomic scenarios to credit losses, market P&L, fee income, OpRisk overlays, risk-weighted assets, and capital ratios over a multi-quarter or multi-year horizon. Narrow shocks (parallel +100 bp on a rates desk) are useful but incomplete: they miss feedback loops such as rating downgrades raising funding costs, which force asset sales, which further depress prices.
Stressed VaR and Stressed Expected Shortfall
Stressed VaR (sVaR) estimates VaR using model inputs from a continuous stressed historical period (for example, a 12-month window spanning 2007–2009) rather than the recent calm window. Basel market-risk frameworks historically required sVaR alongside current VaR to keep capital from collapsing in benign markets.
Stressed expected shortfall (ES) applies the same idea to ES (average loss beyond VaR), aligning with FRTB’s shift toward ES while retaining the need for stressed calibration. Conceptually:
Current VaR/ES → uses recent volatility and correlation Stressed VaR/ES → uses stressed volatility/correlation (or stressed P&L history)
Worked comparison sketch
A equity desk’s current 10-day 99% VaR is USD 12 million using the last year of data (realized vol ≈ 12%). Revaluing the same positions on returns from a stressed year with realized vol ≈ 35% and higher pairwise correlations produces stressed VaR ≈ USD 40 million. Capital add-ons keyed to sVaR prevent the desk from looking “low risk” merely because the recent sample was quiet. Exact multipliers depend on regulatory formulas; the exam point is the stressed window / stressed parameters logic.
Scenario and Model Challenges
Designing scenarios is hard:
- Severity versus plausibility — too mild fails the purpose; too extreme is dismissed as science fiction.
- Consistency — GDP, unemployment, FX, spreads, and property prices must cohere (a full macro narrative).
- Second-round effects — fire sales, rating triggers, contingent facilities drawing, and behavioral assumptions for deposits.
- Model risk — PD/LGD models estimated in expansions misstate downturn losses; market models miss jumps; OpRisk overlays are judgmental.
- Data and systems — enterprise stress needs reconciled exposures across legal entities, currencies, and products.
- Management actions — which mitigations are realistic under stress (deleveraging, dividend cuts, new issuance) versus wishful thinking?
Good programs document assumptions, run sensitivity to key elasticities, and compare model output to historical crisis benchmarks.
Reverse Stress Testing and Regulatory Examples
Reverse stress testing starts from a defined adverse outcome—breach of capital ratio, failure of the business plan, or resolution trigger—and works backward to identify scenarios that could cause that outcome. It answers: “What would have to happen for us to fail?” rather than “What is the P&L in this pre-specified scenario?”
Uses:
- Reveal hidden concentrations and fragile assumptions.
- Challenge official scenarios that never threaten viability.
- Support recovery and resolution planning.
Regulatory examples (high level): supervisors prescribe baseline/adverse/severely adverse macro paths and require projected capital ratios, sometimes with qualitative review of governance and controls. Banks must explain results, capital actions, and shortcomings. Reverse stress tests are often expected as part of ICAAP/ILAAP-style internal assessments even when not the centerpiece of the public supervisory exercise.
Roles: Board, Senior Management, and Audit
| Role | Responsibilities in stress testing |
|---|---|
| Board | Set risk appetite; approve the stress program framework; challenge results and capital plans; ensure resources and independence |
| Senior management | Own scenario design execution; ensure data quality; integrate results into limits, strategy, and contingency funding; escalate breaches |
| Risk function | Methodologies, aggregation, reporting; independent from front office |
| Internal audit / independent review | Assess design effectiveness, validation status, and whether results are actually used—not merely produced |
If stress results never change limits, dividends, or business appetite, the program fails the use test regardless of model sophistication.
Policies, Validation, and Independent Review
A sound stress-testing policy defines: scope (legal entities, risk types), frequency, scenario library, model inventory, data lineage, approval authorities, and escalation thresholds. Validation covers conceptual soundness of satellite models (PD, LGD, PPNR, market shocks), benchmark comparisons, and outcome analysis where feasible. Independent review (validation team and/or audit) should not be the same people who built the models. Findings must feed remediation with timelines.
Basel Stress-Testing Principles (High Level)
Basel Committee guidance on stress testing (principles for banks and supervisors) emphasizes themes FRM candidates should recognize:
- Stress testing should be a firm-wide risk-management tool, integrated into governance and decision-making—not a compliance silo.
- Board and senior management responsibility for the program’s effectiveness.
- Proportionality — intensity commensurate with size, complexity, and risk profile.
- Meaningful, relevant scenarios covering material risks and multiple horizons; include reverse stress tests.
- Robust infrastructure and data to produce timely, reliable results.
- Regular review and update of scenarios, models, and assumptions; independent challenge.
- Supervisory expectations that results inform capital and liquidity adequacy assessments.
(Exact principle numbering evolves across BCBS papers; learn the themes, not rote IDs.)
Putting Stress Testing on the Exam
When a stem contrasts VaR with stress tests, emphasize joint tails, model breaks, and multi-period capital paths. When it mentions sVaR/sES, point to stressed calibration windows. When it asks about reverse stress, work backward from failure. When it asks who does what, map board (appetite/challenge), management (execution/use), and audit/validation (assurance). Stress testing is where Valuation & Risk Models meets governance—and where “severe but plausible” must still be decision-useful.
Enterprise-wide stress testing differs from desk-level VaR primarily because it:
Stressed VaR is best described as:
Reverse stress testing is distinctive because it:
In an effective stress-testing governance framework, which pairing is most accurate?