A vendor file can be complete in every checklist sense and still fail to show that anyone exercised oversight. Examiners increasingly ask the second question, not the first.
This piece covers what examiners now ask, how to read a SOC 2 report the way they do, and how to turn a pile of documents into evidence of oversight.
Image placeholder: Hero image, 1200 × 630. Devensa AI branded graphic for “Vendor Files That Prove Oversight, Not Paperwork”.
A vendor file proves compliance only when it shows oversight actually happened: diligence scaled to risk, verified controls, and monitoring across the relationship. Many files show only that documents were collected. In a Gartner survey of executive risk committee members, 33% reported regulatory action tied to a third-party risk management issue.1
Open a typical vendor file and you find a signed contract, a completed questionnaire, a SOC 2 report, an insurance certificate, and a sanctions screen. Each item is real. Together they can still prove nothing, because each describes a moment, and none shows that anyone read, questioned, or acted on it. The file passes internal review because reviewers check that documents exist, not what the documents reveal.
Third-party compliance, properly defined, is the ability to demonstrate that vendors were managed in proportion to their risk, for the life of the relationship, under a program that operates in practice. It is often reduced to onboarding paperwork. Prosecutors and regulators no longer accept that version.
The DOJ Criminal Division’s Evaluation of Corporate Compliance Programs, last updated in September 2024, asks whether third-party management allows vendors to be reviewed in a timely manner and how the company uses available data to evaluate vendor risk during the relationship.23 An onboarding file cannot answer that question.
Gartner research found that 83% of legal and compliance leaders identified third-party risks after due diligence and before recertification.4 A file built around the onboarding moment misses the period when risk tends to appear.
Verizon’s 2026 DBIR found a third party involved in 48% of breaches, up 60% in a year.5 In IBM’s 2026 breach data, supply chain compromise ranked first among 30 cost factors, adding $227,250 per breach.6 After an incident, the vendor file becomes an exhibit.
This is where the platform’s vCCO capability, an AI-powered vOfficer augmented by Devensa subject-matter experts where needed, is designed to focus: on whether the evidence in a vendor file demonstrates oversight, not only whether the file is full.
Image placeholder: Supporting chart or diagram for this section. Devensa AI branded.
A SOC 2 Type II report is strong evidence when it is read and weak evidence when it is only filed. Four parts deserve attention:
The seven elements of an effective compliance program in the U.S. Sentencing Guidelines (§8B2.1) translate directly to third parties: written standards that bind vendors through contract; oversight by accountable senior personnel; due care in delegating authority to agents and intermediaries; training and communication that reach vendor-facing staff; monitoring, auditing, and reporting channels that cover third parties; consistent enforcement, including consequences for vendors that breach terms; and response and remediation when a third-party issue surfaces.
Devensa AI scores this through TruMaturity™, the methodology and six governance domains shared across Devensa. On the platform, the TruMaturity™ Assessment is designed as an AI-mediated, adaptive assessment, triggered on first sign-in and roughly annually after that, with scores mapped to the five CMMI maturity levels. For vendor compliance, the levels read like this:
Devensa AI scores Compliance on the TruMaturity™ scale and keeps vendor evidence current between reviews, including reviewer findings, report expiration dates, and remediation. A virtual Chief Compliance Officer (vCCO) on the platform tracks obligations, owners, and follow-up for each critical vendor.
Beyond contracts and diligence documents, it should show the risk tier and rationale, reviewer findings, decisions and approvals, monitoring results, exceptions, and remediation over the life of the relationship.
It is strong evidence for the controls and period it covers. It does not cover carved-out subservice organizations, your own complementary user entity controls, or the time since the period ended.
The Evaluation of Corporate Compliance Programs asks whether third-party management is risk-based, timely, and continues through the relationship using available data, not only at onboarding.2
On a risk-based cycle, with critical vendors reviewed at least annually, and whenever a trigger event occurs, such as an incident, ownership change, or adverse finding.
Senior leadership and the board hold accountability, compliance designs the program, and business owners operate it for their vendors. If a regulator pulled one of your critical vendor files tomorrow, would it show a decision or only a document?
Devensa AI scores all six governance domains on TruMaturity™ and keeps the evidence behind each score current. Early access is open now.
Join the early access list: devensa.ai/early-access