5 Model Classification Blind Spots to Watch in 2026

by Stefani Wendel 6 min read March 20, 2026

Model risk management meeting

Model inventories are rapidly expanding. AI-enabled tools are entering workflows that were once deterministic and decisioning environments are more interconnected than ever. At the same time, regulatory scrutiny around model risk management continues to intensify.

In many institutions, classification determines validation depth, monitoring intensity, and escalation pathways while informing board reporting. If classification is wrong, every downstream control is misaligned. And, in 2026, model classification is no longer just about assigning a tier, but rather about understanding data lineage, use case evolution, interdependencies, and governance accountability in a decentralized, AI-driven environment.

We recently spoke with Mark Longman, Director of Analytics and Regulatory Technology, and here are some of his thoughts around five blind spots risk and compliance leaders should consider addressing now.

1. The “Set It and Forget It” Mentality

The Blind Spot

Model classification frameworks are often designed during a regulatory remediation effort or inventory modernization initiative. Once documented and approved, they can remain largely unchanged for years. However, model risk management is an ongoing process.

“There’s really no sort of one and done when it comes to model risk management,” said Longman.

Why It Matters

Classification is not merely descriptive, it’s prescriptive. It drives the depth of validation, the frequency of monitoring, the intensity of governance oversight and the level of senior management visibility.

As Longman notes, data fragmentation is compounding the challenge. “There’s data everywhere – internal, cloud, even shadow IT – and it’s tough to get a clear view into the inputs into the models,” he said.

When inputs are unclear, tiering becomes inherently subjective and if classification frameworks are not reviewed regularly, governance intensity can become misaligned with real exposure. Therefore, static classification is a growing risk, especially in a world of rapidly expanding AI use cases.

In a supervisory environment that continues to scrutinize model definitions, particularly as AI tools proliferate, a dynamic, periodically refreshed classification process can demonstrate institutional vigilance.

2. Assuming Third-Party Models Reduce Governance Accountability

The Blind Spot

There is often an implicit belief that vendor-provided models carry less governance burden because they were developed externally.

Why It Matters

Vendor provided models continue to grow, particularly in AI-driven solutions, but supervisory expectations remain firm.

“Third-party models do not diminish the responsibility of the institution for its governance and oversight of the model – whether it’s monitoring, ongoing validation, just evaluating model drift” Longman said. “The board and senior managers are responsible to make sure that these models are performing as expected and that includes third-party models.”

Regulators consistently emphasize that institutions remain responsible for the outcomes produced by models used in their decisioning environments, regardless of origin. If a vendor model influences credit approvals, pricing, fraud decisions, or capital calculations, it directly affects customers, financial performance and compliance exposure.

Treating third-party models as inherently lower risk can also distort internal tiering frameworks. When vendor models are under-classified, validation depth and monitoring rigor may be insufficient relative to their true impact.

3. Limited Situational Awareness of Model Interdependencies

The Blind Spot

Modern decisioning environments are interconnected ecosystems. Forecasting models may influence reserve calculations. Marketing models may be repurposed across product lines. Data transformations may feed multiple downstream models simultaneously.

Why It Matters

Risk often flows across interdependencies. When upstream models degrade in performance or introduce bias, downstream models inherit that exposure. If multiple material decisions depend on the same data transformation or feature engineering process, concentration risk emerges. Without visibility into these dependencies, tiering assessments may underestimate cumulative risk, and monitoring frameworks may fail to detect systemic vulnerabilities.

“There has to be a holistic view of what models are being used for – and really somebody to ensure there’s not that overlap across models,” Longman said.

Supervisors are increasingly interested in understanding how model risk propagates through business processes. When institutions cannot articulate how models interact, it raises broader concerns about situational awareness and control effectiveness. Therefore, capturing interdependencies within the classification framework enhances more than documentation. It enables more accurate tiering, more targeted monitoring and more informed governance oversight.

4. Excluding Models Without Defensible Rationale

The Blind Spot

Gray-area tools frequently sit outside formal inventories: rule-based engines, spreadsheet models, scenario calculators, heuristic decision aids, or emerging AI tools used for analysis and summarization. These tools may not neatly fit legacy definitions of a “model,” and so they are sometimes excluded without robust documentation.

Why It Matters

Regulatory definitions of “model” have broadened over time. What creates risk is the absence of defensible reasoning and documentation.

Longman describes the risk clearly:

“Some [teams] are deploying AI solutions that are sort of unbeknownst to the model risk management community – and almost creating what you might think of as a shadow model inventory.”

Without visibility, institutions cannot confidently characterize use, trace inputs, or assign appropriate tiers, according to Longman. It also undermines the credibility of the official inventory during examinations.

A well-governed program can articulate why certain tools fall outside model risk management scope, referencing documented criteria aligned with regulatory guidance. Without that evidence, exclusions can appear arbitrary, suggesting gaps in oversight.

5. Inconsistent or Subjective Classification Frameworks

The Blind Spot
As inventories scale and governance teams expand, classification decisions are often distributed across reviewers. Over time, discrepancies can emerge.

Why It Matters

Inconsistency undermines both risk management and regulatory confidence. If two models with comparable use cases and impact profiles are assigned different tiers without clear justification, it signals that the framework is not being applied uniformly. AI adds even more complexity.

When it comes to emerging AI model governance versus traditional model governance, there’s a lot to unpack, says Longman: “The AI models themselves are a lot more complicated than your traditional logistic or multiple regression models. The data, the prompting, you need to monitor the prompts that the LLMs for example are responding to and you need to make sure you can have what you may think of as prompt drift,” Longman said.

As frameworks evolve, particularly to incorporate AI, automation, and new regulatory interpretations, institutions must ensure that changes are cascaded across the entire inventory. Partial updates or selective reclassification introduce fragmentation.

Longman recommends formalizing classification through a structured decision tree embedded in policy to ensure consistent outcomes across business units. Beyond clear documentation, a strong classification program is applied consistently, measured objectively, and periodically reassessed across the full portfolio.

BONUS – 6. Elevating Classification with Data-Level Visibility

Some institutions are extending classification discipline beyond models to the data layer itself. Longman describes organizations that maintain not only a model inventory, but a data inventory, mapping variables to the models they influence.

This approach allows institutions to quickly assess downstream effects when operational or environmental changes occur including system updates or even natural disasters affecting payment behavior.

In an AI-driven environment, traceability may become a competitive differentiator.

Conclusion

Model classification is foundational. It determines how risk is measured, monitored, escalated, and reported. In a rapidly evolving regulatory and technological environment, it cannot remain static.

Institutions that invest now in transparency, consistency, and data-level visibility will not only reduce supervisory friction – they will build a governance framework capable of supporting the next generation of AI-enabled decisioning.

Related Posts

New data indicate signs of increased VantageScore 4.0 adoption. Recent Experian Capital Markets data reporting points to gradual growth in VantageScore 4.0 adoption, and more loans beginning to appear in a larger share of GSE pools.

November 20, 2026 by Angad Paintal
What Is a Ransomware Attack? How to Prepare and Respond

Ransomware attacks can create challenges that extend far beyond an organization’s IT systems. When critical applications become unavailable or sensitive information is compromised, businesses may face operational disruption, financial losses and difficult decisions about how to support affected customers. While cybersecurity defenses are essential, organizations also need clear response procedures, coordinated communication and recovery plans. Understanding how ransomware attacks happen, their potential impact and the steps organizations can take to prepare can help businesses respond more effectively when an incident occurs. What is a ransomware attack? A ransomware attack is a type of cyberattack in which criminals use malicious software or extortion tactics to demand payment from an organization. Traditionally, ransomware encrypts files or systems, preventing authorized users from accessing information until a ransom is paid. Some attackers also steal sensitive data and threaten to release it unless their demands are met. These tactics may occur separately or together, creating challenges for organizations trying to restore operations and protect sensitive information. Paying a ransom does not guarantee that attackers will restore access, delete stolen information or refrain from making additional demands. How do ransomware attacks happen? Ransomware attacks often begin when cybercriminals gain unauthorized access to an organization’s systems or accounts. Once inside, attackers may attempt to expand their access, steal information or deploy malicious software. Common attack methods include: Phishing and social engineering: Deceptive emails or messages that trick employees into opening malicious attachments, visiting harmful websites or sharing login credentials Compromised credentials: Stolen passwords or authentication information used to access business systems and accounts Unpatched vulnerabilities: Security weaknesses in software, servers or network devices that attackers exploit Third-party access: Compromised vendors or connected systems that provide a potential entry point Malicious downloads: Harmful software installed through deceptive websites, compromised applications or unsafe downloads Understanding these methods can help organizations identify potential weaknesses and strengthen their security practices. How do ransomware attacks affect businesses and customers? The consequences of a ransomware attack depend on the systems affected, the information involved and the organization's ability to contain the incident. Business disruption and financial losses When critical systems become unavailable, organizations may experience interruptions to customer service, payment processing, internal operations or other essential functions. The financial impact can be significant. According to the FBI's 2025 Internet Crime Report, reported ransomware-related losses reached approximately $32.3 million, up from $12.5 million in 2024. These figures do not capture the full financial impact of ransomware incidents, including business interruption, recovery expenses and other indirect costs. Customer data exposure and fraud risks Some ransomware incidents involve the theft of sensitive information, potentially exposing customers to identity theft or fraud. If attackers obtain login credentials or personal information, organizations may also need to consider related threats, including account takeover. Customer trust and reputation Customers expect organizations to protect their information and communicate clearly when incidents affect them. Delayed or confusing communication may create additional uncertainty. A coordinated response can help organizations provide timely information and appropriate support to affected individuals. What should organizations do after a ransomware attack? When a ransomware incident is suspected, organizations should activate their incident response procedures and work with qualified professionals to assess and contain the threat. Important response steps include: Activate the response team: Bring together IT, cybersecurity, legal, privacy, communications and leadership teams as appropriate. Contain the incident: Identify affected systems and take steps to limit further unauthorized activity while preserving relevant evidence. Investigate the impact: Determine which systems and information may have been compromised, including whether sensitive data was accessed or removed. Evaluate notification requirements: Work with legal and privacy advisers to determine applicable regulatory, contractual and customer communication obligations. Support affected customers: Prepare clear communications and appropriate resources when personal information has been exposed. An established data breach response strategy can help organizations coordinate customer notification and support activities following an incident. How can organizations prepare for and recover from ransomware attacks? Organizations can prepare for ransomware attacks by combining security controls, tested backups, employee training and a documented incident response plan. Recovery planning should also address how teams will restore systems, assess data exposure and communicate with affected customers. Key preparedness measures include: Maintain secure backups: Keep protected backups and regularly test restoration procedures. Strengthen access controls: Implement multifactor authentication and limit access to sensitive systems. Update software: Address known vulnerabilities through consistent patch management. Train employees: Help staff recognize phishing attempts and suspicious activity. Monitor security threats: Use appropriate detection and monitoring tools to identify potential attacks. Test response plans: Conduct exercises that evaluate technical recovery, communication and decision-making responsibilities. Following an incident, recovery should focus on restoring systems safely, addressing remaining vulnerabilities and evaluating potential risks to affected individuals. Organizations may also need to consider whether compromised information could contribute to additional fraud. Depending on the circumstances, fraud prevention solutions may support broader identity risk management efforts. Security teams should also evaluate related threats, including automated bot attacks, when assessing potential misuse of compromised accounts or credentials. Once operations are restored, reviewing lessons learned can help organizations strengthen their security controls, response procedures and future preparedness. How can breach response planning help protect customers? Ransomware preparedness should account for both operational recovery and the potential impact on customers. If sensitive information is compromised, organizations may need to coordinate notifications, respond to customer questions and provide appropriate support. Experian® offers data breach resolution services that help organizations plan for and manage customer-facing aspects of a breach, including notification management and response support. By establishing response procedures before an incident, organizations can improve coordination and prepare to address customer needs when a breach occurs. Prepare for a more coordinated breach response Explore Experian's data breach response solutions and learn how to plan for customer notification and support. Explore data breach response solutions Download the 2027 Data Breach Response Guide

November 20, 2026 by Julie Lee
How GenAI Fraud Bots Fly Under the Radar (and How to Ground Them Before It’s Too Late)

Today’s AI-powered fraud bots are exceptionally good at mimicking human behavior. Learn why a modern defense strategy is key.

November 18, 2026 by Laura Burrows

Subscribe to our Newsletter

Enter your name and email for the latest updates.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Subscribe to our Newsletter

Don't miss out on the latest industry trends and insights!
Subscribe