For fifteen years, model risk management in US banking ran on one document. On April 17, 2026, the Federal Reserve, OCC, and FDIC jointly rescinded that document, SR 11-7, and replaced it with new interagency guidance, SR 26-2, that changes how banks are expected to build, validate, and monitor every quantitative model they run, according to
Sullivan & Cromwell's memo on the revised guidance The new framework applies most directly to banks above 30 billion dollars in total assets, and it replaces prescriptive checklists with a materiality based, risk scaled approach to model governance, as explained in
PwC's analysis of the update
Generative and agentic AI are explicitly carved out of the new guidance
for now, with a request for information on AI specific model risk expected later in 2026, but supervisors still expect banks to apply model risk thinking to any AI system that materially affects a business decision, as
CRA's insight on SR 26-2 makes clear.
Buried inside that shift is a change that model risk and MLOps teams are only starting to work through: how you validate a model matters more now, and where your validation data comes from is quietly becoming part of that answer.
Validation Just Got More Flexible and More Exposed
SR 26-2 removes the old mandatory annual validation review cycle, letting validation frequency vary based on a model's purpose, its materiality, and the scope of recent changes, according to
PwC's breakdown of the lifecycle changes
. It also streamlines how banks are expected to validate vendor and third party models, an area that used to force banks into awkward workarounds when a vendor would not expose model internals, as
Sullivan & Cromwell's memo
notes.
That flexibility comes with a catch
Fewer prescriptive rules means examiners lean more heavily on the quality of the evidence a bank produces to justify its own risk based choices. For a materiality assessment, a validation cadence, or a vendor model's output testing regime to hold up, the bank has to show its work, and that work depends entirely on the data used to run it.
This is where community bank guidance on AI governance gets specific in a way the interagency guidance leaves general. For a vendor large language model where a bank cannot validate the underlying weights, examiners now accept output based validation against a labeled benchmark set, tested on a regular cadence, as a substitute for validating internals directly, according to this detailed breakdown of SR 11-7 applied to AI at community banks. The benchmark set itself becomes the artifact an examiner will ask to see.
The Benchmark Set Problem Nobody Talks About
Building a labeled benchmark set sounds straightforward until you try to do it without real customer data. Most banks default to pulling a sample of real credit, fraud, or BSA AML cases from production, labeling the outcomes, and running new model versions against that set quarterly.
That approach creates two problems at once. First, a benchmark set built from a static production sample ages quickly. Fraud patterns, credit behavior, and money laundering typologies shift, and a benchmark frozen at one point in time increasingly measures a model against a world that no longer exists, which undermines the very outcomes analysis SR 26-2 asks for. Second, every benchmark set built from real customer data is itself now a governed asset. It has to be stored, access controlled, and accounted for under the same GLBA and cybersecurity expectations that apply to any other system holding nonpublic information, and it has to be refreshed and relabeled without ever letting a stale or biased sample quietly bake itself into your quarterly validation results.
The same governance gap shows up in fair lending testing.
Statistical testing of outcomes by protected class is now an explicit expectation for AI driven credit and customer facing tools, per
this community bank AI governance guide, and running that testing rigorously requires deliberately constructing edge cases and demographic distributions that a real production sample may not contain in sufficient volume to test statistically.
Why Synthetic Validation Data Fits This Moment?
A benchmark and validation dataset that is generated rather than extracted from production sidesteps both problems directly. It can be built to include the exact distribution of edge cases, protected class combinations, and rare event types a fair lending or fraud validation program needs, rather than waiting for those cases to occur naturally in real customer data and hoping there are enough of them to test against. And because it never contains a real customer record in the first place, it removes the nonpublic information governance burden that comes with storing and refreshing a production derived benchmark set quarter after quarter.
This is the exact problem SyntheholDB is built to solve for bank model risk and MLOps teams. SyntheholDB generates schema aware, relationally consistent synthetic databases for credit, fraud, and account data directly from your table structure, preserving the correlations between risk flags, transaction patterns, and account attributes that make a benchmark set meaningful, without ever ingesting a real customer record to build it.
For a quarterly output based validation cycle, that means a fresh, reproducible benchmark set can be regenerated from a documented seed every cycle, deliberately weighted to include the rare fraud, credit, or demographic edge cases a validation program needs to test against, instead of waiting for those cases to accumulate naturally in production. For a vendor LLM your team cannot inspect internally, that same synthetic benchmark set becomes the labeled evaluation set examiners expect to see, built once, refreshed on demand, and never carrying the GLBA and cybersecurity obligations that come with a production derived sample.
Every SyntheholDB generation ships with a fidelity score, a privacy label scan, and a referential integrity report, so when a model risk officer or an examiner asks how a given benchmark set was built and whether it holds any nonpublic information, the documentation exists before the question is finished being asked. Under a framework that now rewards banks for showing their reasoning rather than following a checklist, that kind of standing evidence is exactly what turns a defensible validation program into an easy one.
A Practical Next Step
Start by identifying which of your model validation and benchmark datasets are currently built from real customer records, and flag which of those feed into materiality assessments, fair lending testing, or vendor model output validation under your new SR 26-2 program. For any benchmark set where a synthetic, schema aware alternative can be built with deliberate edge case and demographic coverage, SyntheholDB removes the nonpublic information exposure and the staleness problem in a single change.
Try It Free
Synthehol AI and SyntheholDB is free to start, with no credit card required. Generate your first schema aware synthetic database or datasets in under 60 seconds.
Sign up here: https://synthehol.ai/
