Reports / Security

Where Security Tools Stop

70 diagrams and 50 benchmark profiles. Map the work from finding an issue to reviewing a repair and keeping the evidence.

In this article (8 sections)

A useful security comparison starts with the work your team needs to finish. Finding a vulnerable package, reproducing an attack path, preparing a code change and deploying an operating-system update are different jobs. A single score can hide those differences.

The agent workflow

From a question
to a reviewable change.

Six handoffs explain the work. Choose a stage to inspect its purpose and output.

Stage 01 / A bounded assignment

Which repository, revision and actions are in bounds?

An agent needs a concrete job and the environment to do it. Repository access, test permissions and the intended result define the work.

  • Repository and revision
  • Permitted tools
  • Review boundaries

This is a workflow explanation. It is not a replay of a completed customer scan or a measured product comparison.

Start with the job

Write down the decision you need to make before choosing a tool. If you own the application, you may need a reviewable change and a test of the behavior it addresses. If you operate software another vendor maintains, the job may instead be deploying an available update and confirming the affected systems received it.

The handoff matters as much as the finding. Ask which work the product completes, which work another system performs, and which decisions stay with your team. A good fit can include a human approval step. What matters is that the boundary is explicit.

Follow the seven handoffs

  • Find: identify a relevant issue in the repository or environment.
  • Understand: explain the reachable behavior and the assumptions behind it.
  • Prioritize: distinguish what requires action from what can wait.
  • Propose a fix: produce a change someone can inspect.
  • Deploy: identify who approves, merges and releases it.
  • Retest: exercise the relevant behavior against the proposed change.
  • Retain evidence: keep the revision, test scope and outcome together.

Use these stages as questions, not as a demand that every product own every step. A focused scanner can be a useful part of a workflow. An endpoint patching system can be a good fit for deployed software without being an application-code repair tool.

Research model / November 5, 2026

The handoffs between stages

The source model follows handoffs across a repair workflow. Its marks are research classifications, and Cefense appears as a design profile. Use the diagram to ask where your team takes over.

Archived research. Cefense profiles describe design intent, not a measured run.

The diagram loads as you approach it.

Original research and assumptions
Research model / November 5, 2026

The shape of application security coverage

The shape of a profile depends on the job and the source rubric. These are archived assessments, not measured current capability or product quality.

Archived research. Cefense profiles describe design intent, not a measured run.

The diagram loads as you approach it.

Original research and assumptions

Read the research as a model

The November 5, 2026 source analysis contains 514 tool profiles and 70 diagrams. Its full, partial and no-credit classifications are the original author’s judgments. They are not independent lab results, and no credit is not proof that a vendor lacks a feature. Product editions, configuration, integrations and supported environments can change the answer.

Our fit check makes those assumptions visible. You can choose priorities, narrow the security domain and compare a profile stage by stage. Cefense’s profile is labelled as design intent. Measured scanner results remain a separate record with their own cases and limits.

Compare the work behind the categories

A market map can group products by the work they address without establishing a winner. A family tree reflects the features and weights the author chose. It does not create a new product category or demonstrate that a neighbouring product lacks a capability.

Research model / November 5, 2026

Related tools, grouped by coverage

The source groups related workflow profiles. Cefense’s design sits near established application-security products; the grouping is an interpretation of this source model.

Archived research. Cefense profiles describe design intent, not a measured run.

The diagram loads as you approach it.

Original research and assumptions
Research model / November 5, 2026

Handoffs across different categories

Follow the transitions between stages to see where the source assigns work to another tool or to the team. The classifications have not been independently validated against each current product edition.

Archived research. Cefense profiles describe design intent, not a measured run.

The diagram loads as you approach it.

Original research and assumptions
Research model / November 5, 2026

Stage-by-stage coverage within each group

Different groups address different jobs. Counts describe the 514 profiles in the archived model, not an independently tested estimate of market coverage.

Archived research. Cefense profiles describe design intent, not a measured run.

The diagram loads as you approach it.

Original research and assumptions

Test the assumptions behind a score

Changing the weights tests sensitivity to a scoring model. It does not turn assumed stage credit into measured performance. A simulated lead remains conditional on the original classifications, the selected competitors and the weighting procedure.

Research model / November 5, 2026

Sensitivity to alternative scoring weights

The source explores alternative scoring weights. This is a simulation of its own rubric, with Cefense represented by design intent. It is not a series of independent product trials.

Archived research. Cefense profiles describe design intent, not a measured run.

The diagram loads as you approach it.

Original research and assumptions

Choose the benchmark for the question

Finding an issue, reproducing it, repairing it and preserving legitimate behavior need different tests. Inspect the task, environment, sample, grading and publication date before treating two percentages as comparable.

Research model / November 5, 2026

Published benchmark references in the source

Published benchmark references in the source archive cover different questions. The view does not publish Cefense performance on these protocols.

Archived research. Cefense profiles describe design intent, not a measured run.

The diagram loads as you approach it.

Original research and assumptions
Research model / November 5, 2026

Six dimensions of the source's benchmark assessment

The source assesses benchmarks along six dimensions. These are the author’s quality judgments, not a product leaderboard or a Cefense result.

Archived research. Cefense profiles describe design intent, not a measured run.

The diagram loads as you approach it.

Original research and assumptions
Explore all 50 benchmark profiles and their stage coverage
The benchmark library

Different tests.
Different questions.

All 50 benchmark profiles from the November 5 research archive. Use the stage map to understand which part of a security workflow each test is designed to examine.

Cefense

Our recorded development results appear first in the measured report. The library below describes external protocols; a Cefense result on one protocol cannot be transferred to another.

Open Cefense’s measured evidence
50 benchmarks

The descriptions and stage marks are the archived author’s assessments. Product performance is not scored here. Code and benchmark availability may have changed since the snapshot.

End-to-end lifecycle

CyberGym-E2E

UC Berkeley RDI et al., 2026

Source assessment: Closest thing to a full find-prove-fix benchmark that exists

Scope to inspect: Memory-safety C/C++ only; disclosed, already-fixed bugs

01FindIncluded02UnderstandIncluded03PrioritizeUncredited04Propose a fixIncluded05DeployUncredited06RetestIncluded07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

End-to-end lifecycle

DARPA AIxCC Final

DARPA + ARPA-H, 2025

Source assessment: Most rigorous one-time test of autonomous find-and-patch

Scope to inspect: A competition, not a rerunnable leaderboard

01FindIncluded02UnderstandIncluded03PrioritizeUncredited04Propose a fixIncluded05DeployUncredited06RetestIncluded07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

End-to-end lifecycle

BountyBench

Stanford, 2025

Source assessment: Best web-app lifecycle benchmark; puts dollar values on results

Scope to inspect: Small; detection rates near the floor make ranking noisy

01FindIncluded02UnderstandIncluded03PrioritizeUncredited04Propose a fixIncluded05DeployUncredited06RetestIncluded07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

Patch / repair

SEC-bench

UIUC, NeurIPS 2025

Source assessment: Scalable and real; good for tracking patch skill

Scope to inspect: Patch passes if it compiles and the PoC stops crashing

01FindUncredited02UnderstandIncluded03PrioritizeUncredited04Propose a fixIncluded05DeployUncredited06RetestIncluded07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

End-to-end lifecycle

ZeroDayBench

2026

Source assessment: Best design against memorized fixes

Scope to inspect: 22 tasks is too few to separate close systems

01FindIncluded02UnderstandIncluded03PrioritizeUncredited04Propose a fixIncluded05DeployUncredited06RetestIncluded07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

Patch / repair

PatchBench

2026

Source assessment: Strictest patch grading published so far

Scope to inspect: Patching only

01FindUncredited02UnderstandIncluded03PrioritizeUncredited04Propose a fixIncluded05DeployUncredited06RetestIncluded07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

Reproduce / exploit

CyberGym

UC Berkeley, ICLR 2026

Source assessment: The most-cited AI cyber leaderboard

Scope to inspect: Top agent systems now report ~99%; it has little headroom left

01FindUncredited02UnderstandIncluded03PrioritizeUncredited04Propose a fixUncredited05DeployUncredited06RetestUncredited07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

Product test

MITRE ATT&CK Evals ER7

MITRE, Dec 2025

Source assessment: Best independent test for EDR/XDR

Scope to inspect: No ranking; Microsoft, Palo Alto and SentinelOne skipped 2025

01FindIncluded02UnderstandIncluded03PrioritizeUncredited04Propose a fixUncredited05DeployUncredited06RetestUncredited07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

Reproduce / exploit

CVE-Bench (exploitation)

UIUC, ICML 2025

Source assessment: Strong realism for offensive web testing

Scope to inspect: Offense only; nothing about fixing

01FindIncluded02UnderstandIncluded03PrioritizeUncredited04Propose a fixUncredited05DeployUncredited06RetestUncredited07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

Patch / repair

AutoPatchBench

Meta, CyberSecEval 4, 2025

Source assessment: Good functional-equivalence checking for patches

Scope to inspect: Fuzzing crashes in C/C++ only

01FindUncredited02UnderstandIncluded03PrioritizeUncredited04Propose a fixIncluded05DeployUncredited06RetestIncluded07Retain evidenceUncredited

Cefense on this exact protocol: no comparable result published in this record.

All 70 diagrams

The complete atlas remains available below, including historical context and evaluation design. Each view retains the source assumptions. Current agent workflow documentation is a separate comparison: specialist agents such as Codex Security also describe patch verification and retained artifacts.

The complete research library

Go deeper, one view at a time.

All 70 diagrams from the original research. The source model and its design assumptions remain distinct from Cefense’s measured benchmarks. For current product workflows, read the agent capability comparison.

Original research
Archived research view / November 5, 2026

The seven stages of a security repair

The marks show the original author’s classifications and assumptions. They are not independently measured product performance.

Diagrams open at a readable label size. Pan within the diagram for detail.

Loading diagram

70 views in this topic
Sources and scoring method

The original author assigned full, partial or no credit to seven stages. Its score weights are 10, 10, 10, 15, 20, 20, 15, summing to 100. These judgments are prompts for evaluation, not lab results. A source’s inclusion does not independently substantiate every profile. Cefense appears as a design profile and is not ranked as a measured benchmark result.

The catalogue above recalculates coverage only for the priorities you select. A tool’s intended domain remains essential: endpoint patching, cloud configuration and application-code repair solve different jobs.

Define a trial that can fail

  • Choose a representative repository and agree on the permitted test scope.
  • Record the starting revision and the behavior the tool is expected to detect.
  • Inspect the proposed change before approving any repository action.
  • Repeat the relevant test against the changed revision and check useful behavior still works.
  • Export the evidence and have another reviewer explain what it supports and what it leaves open.

Agree on what would count as a failed evaluation before the trial begins. A confident explanation, a suggested patch and a successful replay are separate pieces of evidence. Treating them separately makes the purchasing decision easier to defend.

Continue with Cefense’s measured benchmark record, the visual evaluation report or the guided fit check. The original research archive, current vendor documentation and measured experiments support different kinds of conclusions.

Back to contents