Basic Prerequisites: 03 · Validation & Backtesting and 04 · Model-Risk Management.
1. Intuition & Practical Objective
The validation machinery of 03 is only as good as the process around it. This page names the four failure modes that defeat a technically correct framework, each with the first-principles reason and a runnable demonstration:
- Overfitting to validation data (selection bias). Once a validation or backtest set is used to choose a model, its error estimate is biased low - sometimes spectacularly. The validator becomes a trainer, and the trial loses its meaning.
- Benchmark error. A benchmark that shares the model’s flaw certifies the same wrong answer. Independence must be demonstrated, not assumed.
- Model drift / regime change. A model calibrated in one regime keeps returning a confident number while coverage decays silently. The number is stale but looks live.
- The model risk of VaR itself. The risk measure is an estimate with sampling error; the validation tests inherit that error. “Passing” a backtest is weak evidence, and the test is itself a model.
The unifying principle. Every one of these is a multiple-comparisons or non-stationarity failure: either you looked at the data too many times (1, 2, 4), or the data-generating process moved (3). Recognising which one you face tells you the fix.
2. Mathematical Ground Truth & Derivations
2.1 Selection bias (the expected maximum). Suppose you screen genuinely skill-less models, each giving an estimate (a -statistic under the null). If you keep the best, its reported statistic is , whose expectation grows like
So “the best of ” is by construction large even when nothing is real. Equivalently, to keep a family-wise error rate you must compare against the Bonferroni threshold , which exceeds the naive by a widening margin.
2.2 The deflated Sharpe ratio. Bailey & López de Prado convert 2.1 into a corrected significance test. With observations and trials, the sharpest -statistic must beat (the expected maximum under the null) before it is evidence at all. The probability of backtest overfitting is the rate at which the in-sample best fails out-of-sample; it rises with and falls with .
2.3 Calibration slippage under drift. If the model is calibrated on a period with volatility but the world moves to , the true exception rate becomes
For , : at , the expected exception rate is - a breach with no change in the code. This is exactly the number measured in the drift demonstration below.
2.4 The estimator’s own error. A VaR estimated from observations carries density-quantile standard error , which shrinks only as ( at , per the VaR hub). Both the reported VaR and the backtest that grades it are randomised by this - an under-appreciated source of spurious green zones.
3. Computational Implementation
(A) Selection bias - “the best of 1000 models”. Generate strategies, each days of pure noise (true skill zero), and screen by -statistic. Stdlib only, seeded.
The best of pure-noise strategies reports - a marginal -value of , which naively reads as “highly significant”. It fails the Bonferroni threshold . Meanwhile of the clear the naive bar and clear - all of them noise. The theoretical ( at ) tracks the simulated maximum () closely. This is why “we validated on a held-out set” is not sufficient: if the held-out set was used to select, it is no longer held out.
(B) Model drift. A VaR model calibrated on a calm regime () against a world that shifts to for the last days.
The same model, unchanged, goes from to exceptions - a degradation - exactly when a doubled volatility arrives. The closed form of §2.3 predicts ; the simulation returns . Drift is not a code bug and will not be caught by re-running tests on old data; it is caught by ongoing monitoring and by the regime-dependence of the estimates themselves.
4. Failure Modes & First-Principles Breakdowns
- Validation-set reuse → biased low. Every peek at the validation set spends a degree of freedom; the reported error falls below the truth (ESL §7.1: “the test set is kept in a vault”). Fix: nested/purged CV, a true holdout, or an explicit multiple-testing correction (Bonferroni, deflated Sharpe).
- The “many-model” illusion of robustness. Screening models and picking the winner manufactures apparent skill (§3A). Fix: pre-register the model, or report the deflated statistic, or size the search budget into the evidence.
- Benchmark error. A benchmark sharing data/code/structure with the model cannot challenge it (03 · §3B showed , indistinguishable). Fix: benchmark on different data or a different model class, and measure the correlation of their errors.
- Drift and non-stationarity. Models are conditional on a regime; when it changes, coverage decays silently (§3B). Fix: ongoing monitoring, rolling recalibration, volatility filtering (FHS/GARCH), EVT tails, and stress backtests.
- The estimator’s noise mistaken for signal. With the VaR has sampling error; two desks with identical risk report VaRs a quarter- apart, and a single year’s backtest cannot distinguish them. Fix: report confidence bands on the VaR and on the test, and require economic (not just statistical) significance.
- Gaming the validator. Optimising for the backtest (e.g., inflating VaR slightly, or widening the window) passes the test without improving the model - Goodhart’s law applied to validation. The cure is SR 11-7’s effective challenge: a party with the incentive and standing to ask “why did this change?“
5. References
- Hastie, Tibshirani & Friedman, ESL 2nd ed. (2009)
- Bailey, D. & López de Prado, M., The Deflated Sharpe Ratio: Correcting for Selection Bias, Backtest Overfitting and Non-Normality, Journal of Portfolio Management 40(5) (2014)
- Federal Reserve / OCC, SR 11-7 (2011) - “Validation is an important check during periods of benign economic and financial conditions, when estimates of risk and potential loss can become overly optimistic”; ongoing monitoring and benchmarking. Read in full from the corpus PDF.
- Derman, E., Model Risk (Goldman Sachs QSR, 1996) - “A model may be reasonable, but the world itself may be unstable… a good model today may be inappropriate tomorrow.” Read in full from the corpus PDF.
- Christoffersen, P. (1998)
- McNeil & Frey (2000)
6. Connected Graph Bridges
- Back: 04 · Model-Risk Management · 03 · Validation & Backtesting
- Forward: 06 · Advanced Extensions (BMA, KL, robust bounds) · Index Hub
- Sibling: Financial ML Pitfalls & Low SNR (backtest overfitting in ML) · Value at Risk & Expected Shortfall (estimation error)