TPRM PERFORMANCE
Can it do the work?
Investigate exposure, prioritize remediation, compare peers, and work through evidence gaps.
current suite
SECURITYSCORECARD RESEARCH
Can AI manage third-party risk without becoming part of the risk?
Measure capability and resilience in TPRM and supply-chain security. Explore the evidence, test your model, and help shape the standard.
Better standards. Built together.
THE EVIDENCE
Compare performance, security, and the conditions behind every result. All four tracks. Every measured configuration.
Current suite. Complete evidence. Release 2026.14 · 818 tasks · 62 disciplines. Completed admin evaluations publish automatically after validation; community runs require admin approval. Incomplete and earlier-suite runs are excluded. Loading verified results…
Recorded results at the same task checkpoints. This is a replay, not execution speed or live progress.
TPRM performance and agent security, side by side. Select a configuration to see its evidence.
Ten configurations in view · scroll for more
| # | Model / developer | Inference provider | Evidence |
|---|
Read the result in context. The inference provider is the service used to run the evaluation; it may differ from the model’s developer. Complete current-suite runs only. Reasoning, inference provider, prompt format and output budgets are visible in the evidence view. Identical configurations pool repeated runs. External validation and repeated-run reliability remain open research.
Completed runs. Recorded settings. Explicit review. Partial runs never become successful measurements.
INSIDE THE BENCHMARK
See the kind of judgment we test.
These are representative scenario summaries; scored answer keys and task scaffolding stay protected.
TPRM PERFORMANCE
Investigate exposure, prioritize remediation, compare peers, and work through evidence gaps.
SECURITY
Compare self-attestations and denials with the underlying vendor-risk evidence.
MODEL SECURITY
Assess model supply chains, serving exposure, artifacts, and recorded controls.
AGENT SECURITY
Measure resistance to injected instructions, escalating pressure, false authority, and needless refusal of legitimate work.
Current suite: release 2026.14. Each published run covers this exact admitted task set. The leaderboard reports each of the four tracks separately, including agent security.
THE STANDARD OF PROOF
A rank is only as useful as the test behind it.
Understand the evidence, the evaluation conditions, and the limits of the conclusion.
Start with a concrete risk decision and a task with a verifiable answer.
Relevant, answerable tasksUse a versioned synthetic portfolio so results refer to the same test material.
A shared research settingRecord the model’s investigation, configuration, and outcomes within the evaluation limits.
Traceable conditionsCheck correctness and completion. Publish the scope and limitations alongside the score.
Evidence before rankingThe expanded suite tests missing evidence, ambiguous decisions, instruction injection, escalating authority claims, and benign requests that may trigger safety refusals. Refusal is reported separately from an incorrect answer; refused tasks remain in the overall denominator.
Answers are checked against task-specific criteria, rather than an LLM judge’s opinion. Performance and robustness are reported separately.
One completed run shows an outcome. Repeated evaluations are needed to establish stability across attempts and model configurations.
Synthetic scenarios give us a common starting point. Enterprise practitioners and researchers can help test relevance beyond this portfolio.
Compare the same vendor question with and without adversarial pressure. Paired confidence intervals and multiple-comparison corrections distinguish observed differences from statistical noise.
Read task scores against chance and the most common answer in each family. Difficulty checks test whether harder tasks actually predict more failures.
Version 0.25 separates a 716-task development book from the 818-task confirmatory book. A recorded specification digest identifies the scoring rules. Confirmatory evidence requires the registered rules to remain unchanged.
Repeatability tools compare attempts and datasets. Silent responses and refusal indicators remain visible. Practitioner weighting is a research contribution, not an established consensus.
Challenge the task coverage, reproduce a result, or propose a harder case. Help strengthen the measurement as well as the models.
Overall: solved tasks divided by 818. Performance: solved performance tasks divided by 344. Security: 123 tasks. Model security: 15 tasks. Agent security: 336 tasks. Each track score is its solved tasks divided by its task count. Overall is the full-suite task solve rate, not a safety certification.
The displayed cohort is release 2026.14, benchmark v0.25.0, on a frozen synthetic portfolio. Each row represents a measured configuration; repeated complete unguided runs with matching settings are pooled. Reasoning settings vary; the detail view exposes the recorded value rather than assuming every model ran at high effort.
Some disciplines contain only one task. Small score differences should not be treated as established superiority. Confidence intervals shown in run details are Wilson intervals over measured task outcomes; they do not measure between-run variance or account for related tasks.
Open samples explain the task families. Hosted evaluations, contributions, and research documentation require Driftnet sign-in. Scored answer keys and task scaffolding stay protected. Fixed test material and grading rules support reproducible evaluation conditions; they do not guarantee identical model responses across runs.
Coming Soon LEARN. IMPROVE. RETEST.
The benchmark reveals where a model struggles. The Gym develops strategy guidance, then tests whether the same model can solve more tasks on separate evidence.
Learn from an evaluation. Develop reusable guidance. Compare the starting instructions and the proposed strategy on identical fresh validation tasks.
Identify where the model’s investigation can improve.
Add guidance to the instructions, not the model’s weights.
Measure both strategies on the same separate evidence.
Driftnet sign-in required · Gym access coming soon
This experiment did not meet the Gym’s promotion threshold (paired p = 0.50). The strategy was not promoted. A higher score in one small test does not establish repeatability or general improvement.
| Measurement | Fresh baseline | With strategy | Change |
|---|---|---|---|
| TPRM Performance | 7/20 · 35.0% | 9/20 · 45.0% | +10.0 pp |
| Security subset | 4/4 · 100.0% | 4/4 · 100.0% | 0.0 pp |
| All validation tasks | 11/24 · 45.8% | 13/24 · 54.2% | +8.3 pp |
What was compared: the same model and configuration, once with its starting instructions and once with the proposed strategy, on identical validation tasks. Unguided mode; inference-provider-default reasoning; 4,096 maximum output tokens per call.
Why this is not the original leaderboard score: the source evaluation covered 120 tasks. Only 15 of the 24 validation task IDs overlap with that run, and the underlying datasets differ. The Gym remeasured a baseline on the fresh validation dataset to make a paired comparison possible.
Evidence strength: two tasks were solved only with the strategy; none were solved only by the baseline. Exact two-sided paired McNemar p = 0.50. This is a single, limited experiment.
Scope: no model-security tasks were included. The four security tasks do not represent the full Model Robustness dimension. This earlier-release Gym experiment is separate from the current leaderboard; publishing an improved leaderboard entry would require a complete, independently reviewed confirmation evaluation.
BUILT BY SECURITYSCORECARD
A convincing answer is not enough when a supplier’s risk becomes your risk.
SecurityScorecard brings the perspective of third-party risk operations: assessing vendors, investigating exposure, challenging self-attestations, and prioritizing action. TPRM Benchmark turns those questions into measurable AI tasks.
The benchmark uses a frozen synthetic portfolio modeled on the structure of vendor-risk evidence. It gives researchers a shared test environment without exposing customer data.
Understand exposure and continuously monitor your vendor ecosystem.
02 / ASSESSMENTBring automation and risk intelligence into the assessment workflow.
03 / ACTIONPrioritize threats and drive continuous third-party risk reduction.
Built from domain expertise. Benchmark scores are research measurements, not product endorsements or deployment certifications.
AN OPEN INVITATION
For the teams building models.
The people studying them.
And the professionals who will rely on them.
Putting an AI agent into your vendor-risk program without testing it is like giving a new employee privileged access on day one and hoping for the best. The TPRM Benchmark answers two questions every security leader should be asking: can this model do the work, and can it be turned against me? If you can’t answer both, you don’t have an AI advantage. You have a new attack surface.
Dr. Aleksandr YampolskiyCEO and Co-Founder · SecurityScorecard
Our initial benchmark runs show open-weight models closing the gap with leading frontier models on supply chain security tasks, but several of those same models remain highly susceptible to adversarial attack. As AI increasingly takes on critical security functions, organizations need to know not just which models perform best at each task, but which ones hold up when someone is actively trying to manipulate them.
Dr. Mike MylreaCISO and Chief AI Officer · SecurityScorecard
You can't secure an attack surface you haven't measured, and TPRM Bench gives security teams a shared, transparent way to evaluate models on capability and attack resistance together. In our own Snyk research across 3,000 enterprise environments, 74.5% of those with a detected model, reference at least one that scores ‘high’ on an attacker goal under adversarial testing.
Manoj NairChief Technology & Innovation Officer · Snyk
There are many AI models on the market that deliver the results they promise, but very few adhere to the cybersecurity standards needed for real industry adoption, and that gap is exactly why we need an evaluation platform like this one. I think of a good benchmark like a race track: it shows you which models have real problems under the hood, and it reveals the true limits of what’s possible, which is what makes this work academically meaningful, about scientific discovery, not just about picking the best commercial model off the shelf. It also matters enormously for organizations trying to use AI in third-party risk workflows specifically. It’s not enough to know a model can complete the task. Done right, a benchmark like this is how you get the confidence to actually deploy AI in these workflows, knowing it does the job well and that its security can be trusted.
Dr. Yelena YeshaKnight Foundation Endowed Chair of Data Science and AI · Director, Machine Learning and AI program · Frost Institute for Data Science and Computing, University of Miami
TPRM Bench stands out by testing AI against real supply chain scenarios grounded in empirical security data. Its rigorous, reproducible framework helps bridge the gap between benchmark performance and real-world security as AI adoption in critical infrastructure accelerates.
Yevgeniy DodisProfessor of Computer Science · New York University; Fellow of the IACR
Preempting the next cyber attack means proving your defenses before they're put to the test. Trust in AI must be earned through continuous testing in realistic, production-like conditions. SecurityScorecard's TPRM Benchmark helps build that trust by measuring whether AI can perform critical tasks and resist manipulation. For security leaders, validating AI is essential for deciding how much autonomy to give agents and for pinpointing when humans need to remain in control.
Peter LeeCEO · SimSpace
AI is now part of both attacker and defender tooling, so unexpected model behavior can quickly become an incident for one side or an opportunity for the other. At GreyNoise, we've seen attackers' AI use leave identifiable tells, and we've seen defenders' models make mistakes analyzing packets and TTPs. Objective, transparent measurement like SecurityScorecard's TPRM AI Benchmark puts evidence of model performance on the table, so defenders can adopt AI with a clear view of its strengths and limits.
Corey BodzinChief Product Officer · GreyNoise
Connect a supported inference provider or a custom endpoint. Run a measured evaluation and submit your results for review.
Start an evaluation ↗Help test repeatability, challenge the scoring assumptions, and examine whether results distinguish meaningful differences in capability.
Join the research ↗Propose tasks and new tracks. Help establish whether the decisions and evidence gaps your analysts face are represented well.
Contribute a scenario ↗Inference usage is billed to your inference provider account. Reading results and methods requires no account.