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.
From a question
to a reviewable change.
Six handoffs explain the work. Choose a stage to inspect its purpose and output.
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.
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.
The diagram loads as you approach it.
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.
The diagram loads as you approach it.
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.
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.
The diagram loads as you approach it.
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.
The diagram loads as you approach it.
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.
The diagram loads as you approach it.
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.
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.
The diagram loads as you approach it.
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.
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.
The diagram loads as you approach it.
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.
The diagram loads as you approach it.
Explore all 50 benchmark profiles and their stage coverage
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.
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 evidenceThe 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.
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
Cefense on this exact protocol: no comparable result published in this record.
Source assessment: Most rigorous one-time test of autonomous find-and-patch
Scope to inspect: A competition, not a rerunnable leaderboard
Cefense on this exact protocol: no comparable result published in this record.
Source assessment: Best web-app lifecycle benchmark; puts dollar values on results
Scope to inspect: Small; detection rates near the floor make ranking noisy
Cefense on this exact protocol: no comparable result published in this record.
Source assessment: Scalable and real; good for tracking patch skill
Scope to inspect: Patch passes if it compiles and the PoC stops crashing
Cefense on this exact protocol: no comparable result published in this record.
Source assessment: Best design against memorized fixes
Scope to inspect: 22 tasks is too few to separate close systems
Cefense on this exact protocol: no comparable result published in this record.
Source assessment: Strictest patch grading published so far
Scope to inspect: Patching only
Cefense on this exact protocol: no comparable result published in this record.
Source assessment: The most-cited AI cyber leaderboard
Scope to inspect: Top agent systems now report ~99%; it has little headroom left
Cefense on this exact protocol: no comparable result published in this record.
Source assessment: Best independent test for EDR/XDR
Scope to inspect: No ranking; Microsoft, Palo Alto and SentinelOne skipped 2025
Cefense on this exact protocol: no comparable result published in this record.
Source assessment: Strong realism for offensive web testing
Scope to inspect: Offense only; nothing about fixing
Cefense on this exact protocol: no comparable result published in this record.
Source assessment: Good functional-equivalence checking for patches
Scope to inspect: Fuzzing crashes in C/C++ only
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 visual archive
Read every diagram, chapter by chapter.
Open a chapter to read its large figures in sequence. All 70 original views remain available. Diagrams load as you approach them.
Current Codex Security documentation also describes patch verification and retained artifacts. Read these archived judgments alongside the current agent capability comparison.
Workflow essentials10 diagrams
The seven stages of a security repair
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Where workflow coverage falls away
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Coverage across the tool landscape
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The handoffs between stages
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The source model's headline comparison
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Stage coverage for application security
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Four questions for a proposed fix
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
What a useful evidence record contains
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Two paths from a finding to a reviewed change
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The work between security tools
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The selected profiles15 diagrams
The selected competitors under one model
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
A stage-by-stage competitor matrix
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
How far the selected profiles extend
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Work the model leaves with your team
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The output at the end of each workflow
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Finding coverage and finishing coverage
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Comparing the jobs tools are designed for
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The shape of application security coverage
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Profiles of the AI repair tools
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
How priorities change a ranking
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The contribution of each workflow stage
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
What proactive coverage includes
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The selected profiles at each stage
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Related tools, grouped by coverage
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
A separate profile for each competitor
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Scoring sensitivity3 diagrams
Sensitivity to alternative scoring weights
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Which weights move the comparison
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Comparing five sets of priorities
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The tool landscape26 diagrams
Stages covered by proactive tool groups
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Full, partial and uncredited stages
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
How the source classifies fix verification
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
How the source classifies retained evidence
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The overlap of fix, retest and evidence
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Verification within code security
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
A view of the source categories
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Handoffs across different categories
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Finding and finishing by category
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Later-stage coverage in the shortlist
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
All source profiles in one view
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Breadth and workflow depth
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Workflow coverage by tool group
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Ownership classifications in the source
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Workflow scope and ownership
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Finding, fixing and evidence
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The distribution of workflow profiles
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Stage-by-stage coverage within each group
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
How profile classifications change by stage
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Stages that occur together
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Category coverage, with stage totals
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
How finishing coverage is distributed
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Breadth and the source model's frontier
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The gap between finding and finishing
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Stage coverage across security areas
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Combining code-security profiles
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Historical context5 diagrams
Acquisition context in the source research
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
This archived context includes deal, legal or price assumptions that have not been revalidated. Inspect the original cited material before relying on them.
The diagram loads as you approach it.
The source research timeline
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
This archived context includes deal, legal or price assumptions that have not been revalidated. Inspect the original cited material before relying on them.
The diagram loads as you approach it.
Reporting context cited by the source
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
This archived context includes deal, legal or price assumptions that have not been revalidated. Inspect the original cited material before relying on them.
The diagram loads as you approach it.
Price and penalty assumptions in the source
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
This archived context includes deal, legal or price assumptions that have not been revalidated. Inspect the original cited material before relying on them.
The diagram loads as you approach it.
Buyer interests in the source research
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
This archived context includes deal, legal or price assumptions that have not been revalidated. Inspect the original cited material before relying on them.
The diagram loads as you approach it.
Evaluation design11 diagrams
Published benchmark references in the source
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Which parts of the workflow tests cover
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The source's benchmark assessment
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Realism and grading in the source model
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Workflow stages within benchmark types
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
The changing scope of security evaluations
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Product stages and evaluation stages
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
A proposed evaluation plan
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Benchmark selection in the source research
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
A stage map of the source's benchmark list
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
Six dimensions of the source's benchmark assessment
This view preserves the archived author’s model and assumptions. Cefense’s design profile is distinct from an independently measured result.
The diagram loads as you approach it.
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.
