Join HITRUST and Sidekick Security for our pivotal webinar to explore why Third-Party Risk Management (TPRM) strategies often fail despite heightened focus and investment. This session will dissect systemic flaws, like reliance on static security questionnaires and inconsistent risk assessments, that prevent effective third-party risk management across industries. We will discuss the need for a paradigm shift towards proactive, innovative, and integrated TPRM strategies that align compliance with real-world threat mitigation. Learn how to advance beyond conventional methods to adopt dynamic, scalable solutions for a resilient third-party risk framework.
If you liked this webinar, you may also be interested in:
Nov 20, 2026
“Check the box” TPRM isn’t reducing the risk, and attackers know it
Third parties are once again at the center of major cybersecurity headlines. JPMorgan, Visa, and Mastercard have each reported cybersecurity incidents involving third-party service providers. JPMorgan said attackers accessed certain marketing data held by vendors, potentially including customer names and email addresses. Importantly, the incidents did not require attackers to compromise the companies’ core systems or payment networks directly. The third party itself created the pathway to each of the financial service organization’s information.
At nearly the same time, in a November 13 FBI FLASH, the FBI issued a warning about the ARTEX autonomous penetration testing framework. ARTEX is “an open-source, large language model-driven agentic platform that threat actors have weaponized to automate multiple phases of cyber intrusions, from reconnaissance through data exfiltration”. In some observed incidents, attackers progressed from initial targeting to privileged access in less than three hours.
The FBI specifically identifies partner and supplier systems among the environments at risk and describes supply-chain compromise as part of observed ARTEX activity. One campaign involving ConnectWise Cloud Backup led to attempted sign-ins against more than 2,250 downstream customers.
These stories are different, but the message for third-party risk management (TPRM) leaders is remarkably similar: attackers continue to look for the weakest path into an organization, and increasingly that path may run through a third party.
Attackers are moving at AI speed. Your questionnaires don’t.
The more significant change is less about fundamentally new vulnerabilities or an entirely new attack workflow and more about speed and scale. Familiar activities such as reconnaissance, exploitation, and lateral movement are being executed across vulnerable third-parties at an increasingly faster pace.
That creates an important resource-allocation question for TPRM programs: As attackers are moving faster, can organizations afford to keep spending so much of their finite time administering assurance rather than reacting to threats and focusing on risk?
While questionnaires can be a tool for gaining information about a third-party’s perceived security operations, collecting evidence is not the same as creating reliable assurance. TPRM teams spend substantial time distributing questionnaires, chasing responses, and interpreting artifacts before they can determine what the evidence actually says about risk. Hundreds of completed questionnaires may state that a process was followed without demonstrating that the controls most relevant to current threats have been evaluated with sufficient rigor.
If your TPRM program (and customers) are spending too much valuable time managing the questionnaire process, the result can be a program that produces a tremendous amount of activity without a commensurate reduction in risk.
That inefficiency becomes more consequential during a large-scale cyber event. When a new vulnerability or attack campaign is disclosed, organizations need to identify which vendors are potentially exposed and whether existing assurance provides enough confidence to support a decision. Managing the third-party attack surface therefore requires knowing which vendors matter most and whether the available assurance provides sufficient confidence that those controls are working.
The ARTEX threat makes that problem more visible as it compresses the threat timeline, demanding more efficiency from your TPRM program.
When some observed attacks can progress to privileged access in under three hours, a TPRM program cannot depend on an annual exercise to provide confidence about third-party security. Faster threats require TPRM programs to be far more deliberate about which activities reduce risk.
Third-party Risk Is a Real-World Risk problem
The incidents involving JPMorgan, Visa, and Mastercard are reminders that third-party risk does not end with the security of an organization’s own environment. A vendor that holds customer information, operates a connected system, or has trusted access can create exposure even when the organization’s core infrastructure remains secure. Customers do not necessarily distinguish between a company and its vendor when a cyberattack occurs.
Instead of viewing third-party assessment primarily as an administrative process, TPRM programs must align their assurance requirements with the risks and attack techniques they are actually trying to address. The controls assessed should have a defensible relationship to the threats facing the organization and its third-party ecosystem.
An effective TPRM program connects the chain between real-world threats and informed risk decisions.

Connecting that chain requires understanding:
- What access or information does this third party have? A vendor with privileged connectivity or access to sensitive data presents a very different risk than one with no logical connection or critical information.
- Which threats are relevant to that relationship? Supply-chain compromise, credential theft, exposed cloud services and vulnerable internet-facing applications may warrant different control expectations.
- Which controls materially reduce those risks? Assessment requirements should focus on controls with a meaningful relationship to the threat scenarios that matter.
- How much confidence do we have that those controls actually operate as expected? An assertion that a control exists is different from independent evidence that it has been implemented and is operating effectively.
- Does the assurance remain relevant as threats change? Assurance can quickly lose value when both the threat environment and technology landscape evolve rapidly.
When a significant cyber event occurs, TPRM teams should be able to use the above information to quickly determine which third parties warrant attention. A risk-aligned third-party approach can help organizations focus their effort on the controls and relationships that matter most.
ARTEX is the latest example, not the last
The FBI’s ARTEX warning and the other attacks affecting third-party providers should not be viewed as isolated events. They are recent examples of a persistent pattern: attackers look for weaknesses across an organization’s extended ecosystem, while AI allows them to do so increasingly faster and at greater scale. The next example may involve a different tool, vulnerability, or vendor, but the underlying TPRM challenge will remain the same.
Organizations cannot respond to every new threat by stopping routine vendor assessments and launching a separate manual investigation. Nor can they assume that an annual vendor questionnaire will provide the timely, comparable insight needed during a fast-moving event. TPRM programs need a repeatable operating model that supports both conducting rigorous assessments and quickly determining how emerging threats affect the third parties on which the organization depends.
Managing your third-party attack surface therefore requires more than demonstrating that vendors have been asked a set of questions. It requires knowing which risks matter, which controls address those risks, and whether the assurance you're relying on provides sufficient confidence that those controls are working.
Because when attackers target the third party standing between them and your environment, checking the box isn't the same thing as reducing the risk.
Learn how HITRUST modernizes TPRM programs
Want to learn how to evolve your TPRM program? Read our TPRM Top 10 Paper to understand this and other challenges, and how to react to them.
Attackers Are Targeting Your Third-Parties. Paperwork Is Not a Defense. Attackers Are Targeting Your Third-Parties. Paperwork Is Not a Defense.
Nov 17, 2026
What Should a Third-Party Risk Management Program Measure?
What Should a Third-Party Risk Management Program Measure?
A third-party risk management (TPRM) program should measure more than how many vendors have been assessed or how many reviews have been completed. It should help an organization understand where third-party risk exists, how much risk remains, and whether that risk is within established tolerance.
That requires looking beyond traditional activity metrics.
Vendor inventories, questionnaires, assessments, certifications, audit reports, and cyber scores all provide useful information. But an effective measurement model connects those inputs to the actual exposure created by third-party relationships.
A TPRM program should focus on measures beyond work volumetrics, such as:
- Coverage: What percentage of vendors are inventoried and assessed?
- Criticality: Which vendors create critical dependencies?
- Control effectiveness: How effective are the vendor's relevant security controls?
- Assurance confidence: How reliable and current is the evidence?
- Residual risk: How much risk remains after controls are considered?
- Risk tolerance: Which vendors fall outside established tolerance?
- Concentration: Where is third-party exposure concentrated?
- Remediation: How much vendor risk remains unresolved?
- Change: Which vendors' risk profiles are improving or deteriorating?
- Financial exposure: What potential business or financial impact does the portfolio create?
- Risk treatment: How much risk is accepted, mitigated, avoided, or transferred?
- Program efficiency: How long do reviews take and where is analyst effort going?
Why Traditional TPRM Metrics Don't Tell the Whole Story
Many TPRM programs are good at measuring activity.
They can report how many vendors have completed assessments, how many findings remain open, how long reviews take, and how many vendors fall into different risk tiers.
Those metrics are useful for managing a program, but they do not necessarily tell leadership how much third-party risk the organization is carrying.
The goal is to shift the question from "Did we assess our vendors?" to "What risk do those vendors create for the organization?"
Measuring Vendor Risk Starts with Exposure and Assurance
Not every third party creates the same level of risk.
Organizations first need to understand which vendors support critical operations, handle sensitive information, connect to important systems, or create other material dependencies. They can then evaluate whether the controls relevant to those risks are operating effectively.
But control effectiveness alone does not tell the whole story.
Organizations also need to consider the quality of the assurance supporting that conclusion. Evidence can differ in scope, testing methods, treatment of exceptions, and reporting formats, making assurance difficult to compare across vendors. HITRUST's TPRM guidance recommends establishing consistent criteria for evaluating assurance and increasing reliance on standardized, independently validated evidence. This gives organizations a more comparable and trustworthy foundation for evaluating vendor risk.
Together, criticality, control effectiveness, and assurance of confidence provide a stronger foundation for understanding how much risk remains.
Residual Risk Has to Connect to Risk Tolerance
Once an organization understands the risk a vendor creates and the controls that are in place to address it, the next question is whether the remaining risk is acceptable.
That is where residual risk and risk tolerance become particularly important.
A consistent measurement approach allows organizations to identify vendors that fall outside established tolerance and determine how those risks should be treated. Depending on the situation, the organization may choose to mitigate, accept, avoid, or transfer the risk.
This helps make TPRM decisions more consistent and defensible rather than relying primarily on individual reviewer judgment or whether a vendor passed a particular assessment.
TPRM Programs Also Need a Portfolio-Level View
Looking at vendors individually can hide risk that becomes significant across the organization.
Multiple vendors may depend on the same cloud provider, support the same critical business process, handle similar sensitive information, or share common control weaknesses.
Measuring concentration helps organizations identify those patterns.
TPRM programs should also monitor how the portfolio changes over time. Remediation efforts may reduce exposure, while new dependencies, changing services, outdated assurance evidence, or deteriorating controls may increase it.
Adding financial exposure gives leadership another way to understand the potential business impact associated with those risks.
Together, these measures provide a more complete picture of third-party risk than individual vendor ratings alone.
How HITRUST Modernizes Third-Party Risk Management
HITRUST's approach to third-party risk management focuses on moving beyond disconnected assessments and vendor-review activity toward a more standardized approach to understand risk and exposure.
Standardizing TPRM using HITRUST can reduce the time and effort required for vendor reviews while giving organizations greater confidence in their understanding of vendor risk. CHIME research commissioned by HITRUST found that 92% of respondents estimated that relying on a single validated certification could save at least eight hours per vendor assessment. By using standardized, independently validated assurance that can be reused across vendor relationships, TPRM teams can reduce repetitive review work and establish a more consistent foundation for evaluating risk.
That matters because security and risk leaders need more than metrics that their TPRM program is processing vendor reviews. They need to understand which third parties create significant risk, how reliable the supporting assurance is, whether the remaining exposure is acceptable, and where action is needed.
Instead of measuring success by the number of assessments completed, organizations can measure what ultimately matters: how effectively they understand and manage the risk created by their third-party ecosystem.
Ready to move beyond counting vendor assessments and really understanding your third-party risk exposure? Explore the TPRM Top 10 for insights into today’s most pressing third-party risk challenges.
What Should a Third-Party Risk Management Program Measure? What Should a Third-Party Risk Management Program Measure?
Nov 12, 2026
AI Governance and Risk Management for Regulated Industries
AI Governance and Risk Management for Regulated Industries
AI risk in regulated industries, like financial services, healthcare and life sciences, business services, and technology, is ultimately an implementation and sustainment challenge. Most organizations understand the need to govern AI risk, but turning that intention into clear ownership, consistent controls, and defensible evidence is much harder.
For regulated organizations, the challenge is compounded by the speed at which AI is developing, evolving regulatory requirements, inconsistent approaches to AI governance, and AI capabilities spanning internal and third-party technologies. But regulated industries also have an advantage: they already operate established security, privacy, and risk management programs.
Rather than creating an entirely separate AI governance program, organizations can build on those existing structures to bring AI under control while maintaining compliance and audit readiness.
Why AI Risk in Regulated Industries is Harder than it Looks
Managing AI risk in regulated industries is complicated by several issues: a lack of standardization for AI risk and security, unclear accountability, the pace of change with AI, and a regulatory environment that continues to evolve.
Organizations may be evaluating multiple AI governance frameworks while also considering existing obligations under programs and standards such as HIPAA, PCI DSS, FedRAMP, SOC 2, NIST, and ISO. At the same time, responsibilities for AI can span security, privacy, legal, compliance, risk, procurement, and technology teams.
That creates a practical question: Who is actually responsible for the risk?
Successful governance requires organizations to define who can approve AI use cases, who evaluates the associated risks, who monitors AI systems, and who is accountable when something goes wrong.
For U.S.-based organizations, the changing regulatory landscape adds another layer of complexity. Organizations may need to prepare for requirements affecting their operations without having a single, consistent domestic regulatory standard to follow as states like California, Texas, Colorado, Utah, and Illinois set their own regulations.
The goal should not be predicting every future change and requirement. It should be developing a defensible AI risk management approach that can adapt as requirements evolve.
The Shadow AI Problem Most Governance Programs Miss
One of the most immediate challenges for AI security for regulated industries is visibility.
Shadow AI can emerge when employees use generative AI tools or enable AI capabilities outside approved processes. That can introduce data handling, privacy, security, and regulatory risks before an organization has had the opportunity to evaluate them.
A governance program focused only on approved AI deployments can therefore miss some of the organization's most important exposures.
Before organizations can effectively govern AI, they need visibility into what is actually being used, including both sanctioned and unsanctioned AI.
Connecting AI Governance to Programs You Already Have
Effective AI governance for regulated industries does not necessarily require building another standalone compliance program.
In many cases, doing so can create unnecessary duplication. AI risks often overlap with areas organizations already manage, including data governance, identity and access management, third-party risk, incident response, privacy, and security.
Connecting AI to those existing domains can create a more consistent and auditable approach.
For example, AI agents with access to sensitive systems still require appropriate identities, permissions, and access controls. AI vendors still need to go through third-party risk processes. Sensitive information used in prompts or models still falls within data protection requirements.
Model risk management concepts that have long been used in financial services are also becoming relevant beyond banking. Practices such as model validation, documentation, performance monitoring, and defined ownership can help organizations establish greater accountability around enterprise AI.
Third-party AI risk deserves particular attention. AI functionality is increasingly embedded in SaaS products and other vendor technologies, which means organizations may be exposed to AI risk even when they are not developing or operating the underlying models themselves.
Integrating these risks into existing programs can help organizations reduce fragmentation while creating a clearer view of AI risk across the enterprise.
What Defensible AI Security Controls Look Like in Practice
Technology is only one part of effective AI governance.
As organizations evaluate AI governance platforms for regulated industries and AI security tools for regulated industries' enterprises, the focus should remain on whether the resulting controls are defensible.
In practice, that means controls should be:
- Documented: Requirements and responsibilities are tied to a recognized security or risk framework.
- Validated: Organizations can provide evidence that expected controls have actually been implemented.
- Maintained: Controls and supporting evidence remain current as AI use and risks change.
Accountability matters just as much. Organizations should clearly define who approves new AI use cases, who is responsible for model behavior and monitoring, and who owns the response when an AI-related issue occurs.
Audit readiness should also be continuous rather than something assembled immediately before an audit. Maintaining evidence of approvals, assessments, control implementation, monitoring, and remediation can help organizations demonstrate how AI risk is being managed over time.
How HITRUST Supports AI Governance in Regulated Industries
For organizations managing AI risk in regulated industries, the goal is not to add another disconnected program. It is to bring AI into a structured risk and assurance approach that works alongside existing obligations.
The HITRUST AI Risk Management Assessment helps organizations evaluate AI governance structures, risk identification, and the implementation of controls. The HITRUST AI Security Assessment addresses AI-specific security controls.
Together, they can help organizations approach AI governance for regulated industries as an extension of established security and risk management practices rather than a separate compliance exercise.
This matters because AI governance needs to hold up beyond an internal policy document. Security leaders, auditors, customers, regulators, and procurement teams may all need evidence that risks have been identified, responsibilities are clear, and appropriate controls are operating as expected.
Managing AI responsibly does not have to mean creating more complexity. For regulated organizations, the stronger approach is often to build on the security, compliance, and risk management foundation already in place, then extend it to address what is different about AI.
Ready to build greater trust into your approach to AI? Download the Building Trust in the Age of AI ebook.