Design Partner Program
HAYROK RESEARCH · BENCHMARKS

Benchmark reports: how teams prove exposure, not just find it.

Three benchmarks, one question asked three ways: once a tool says something is risky, covered or exposed, how do security teams confirm it? Each report covers one domain, uses the same validation outcomes, and ends with a way to compare your own program.

FEATURED REPORTDETECTION
Detection Coverage Benchmark A detection rule isn't coverage until the behavior is observed.
→The gap between mapped and validated coverage→How teams catch detection drift→A self-assessment to compare your program
Open the full report Read →
3 benchmarks covering API security, detection coverage and identity risk HAYROK RESEARCH
61% of API scanner findings are never validated as exploitable or not API BENCHMARK
37 pts gap between mapped and validated ATT&CK detection coverage DETECTION BENCHMARK
66% of organizations don't validate identity-based attack paths IDENTITY BENCHMARK
ACROSS ALL THREE

Three Themes That Show Up in Every Benchmark

Different domains, the same pattern: the tool's signal and the proven outcome are not the same thing.

01 · SIGNAL ISN'T PROOF

Tools flag; few teams confirm

In each domain, the tool's output (a finding, a mapped rule, a risky permission) is treated as the answer. The benchmarks look at how often teams go one step further and prove it.

APIScanner finding vs proven authorization flawDETECTMapped rule vs observed alertIDENTITYRisky permission vs validated path
02 · POINT IN TIME

Validation happens too rarely

Where validation exists, it's often tied to an annual test or audit. Environments change weekly, so results age quickly.

APIRetesting after releasesDETECTReruns after pipeline changesIDENTITYRevalidation after role changes
03 · OUTCOMES

No shared language for results

Teams describe results differently across tools, which makes progress hard to report. Each benchmark uses the same outcome definitions to fix that.

APIExploitable, blocked, not reachableDETECTPrevented, detected, logged, missedIDENTITYValidated, blocked, theoretical
WHERE TO START

Which Benchmark Should You Read First?

Pick the question your leadership asks most often. We'll point you to the report that answers it.

START WITH API Security Validation Benchmark

It shows how teams move from scanner and inventory findings to proven authorization risk, and where that process usually stalls.

THEN READ Identity Risk Benchmark, for the identities those APIs trust.
Open the report →
HOW WE BENCHMARK

One Method Across Every Report

Each benchmark uses the same structure, so findings can be compared across domains. Full methodology and limitations are published inside each report.

01

Defined scope

Each report states which environments, organization sizes and time period it covers.

02

Consistent definitions

Validation outcomes use the same names and meanings across every benchmark.

03

Published limitations

Sample size, sources and known biases are listed inside each report.

04

Self-assessment

Every report ends with questions you can use to place your own program.

SHARED OUTCOMESValidatedReproducedAssessedTheoretical
NEW RESEARCH

Get each new benchmark when it's published.

One email per report. No sequences.

We'll only use your email to send new benchmark reports.