Refusal Map: which models still do legitimate defensive security work
Open benchmark and routing proxy showing which models refuse real defender tasks. Pentesters and small MSSPs pay.
Competitive · Frontier guardrails now block defenders
Written for: Solo builder
Next step
This week, write 50 defensive tasks with pass and fail criteria, run them against four APIs and one local model, and publish the refusal table on GitHub. Then post it to r/netsec and the Hacker News security crowd.
Why now
The Decoder reports that guardrails meant to stop attackers are now blocking defenders, and the market is splitting into general models that refuse and specialist cyber models that don't (Orion-1, OpenAI Daybreak at SentinelOne, Cohere buying AISLE). Patch demand is huge: Bank of America hired 1,000 contractors to fix flaws Mythos exposed. Nobody publishes a neutral, task-level map of which model will actually do 'write a detection rule for this PoC' or 'triage this CVE in my repo'. That gap is buildable in two weeks.
What became possible
General frontier models have locked down cyber capabilities hard enough that defenders get refused. At the same time, purpose-built defender models like Artemis Security's Orion-1 exist, and Gemini 4 Argon found over twice as many vulnerabilities as baseline models in Wiz's shadow tests.
Two ways in
- Refusal Map leaderboard
Open-source harness with around 200 clearly legitimate defensive tasks (YARA and Sigma rules, PoC explanation for patching, log triage, CVE reachability in sample repos). It runs them against every major API and open-weight model and publishes refusal and quality rates weekly.
- Customer
- Security engineers choosing a model for their team; bug bounty hunters
- Model
- Free public leaderboard as the wedge, with paid private runs on your own task set at $49 a month
- Defender Router
OpenAI-compatible proxy that detects a refusal and retries the same unmodified prompt on the next model in a user-chosen list, such as a local open-weight model or a defender-specific API. It logs every hop for the client report. No jailbreak prompts, ever.
- Customer
- Small pentest shops and MSSP analysts
- Model
- $29 a month per seat, self-serve, with a free self-hosted tier
Competition
Some figures here, including model names, refusal percentages and launch dates, came from secondary coverage I could not check against primary sources.
Full competition notes (9 competitors)
Part of the problem is already being solved: the main labs now attack refusals directly. OpenAI's Trusted Access for Cyber and Anthropic's three-tier Cyber Verification Program (October 2026) both reduce friction for verified defenders, and Anthropic explicitly lets small firms and individual researchers apply. On the leaderboard side, Artificial Analysis appears to have launched a Cyber Index in September 2026 that reports refusal rates on defensive tasks. With its reach, a generic "which model refuses" chart is hard to win head-on. I found no maintained, open, weekly leaderboard limited to defender tasks such as YARA and Sigma rules, PoC explanation, log triage and CVE reachability. Nobody seems to report results per verification tier (unverified vs TAC vs CVP Defense vs Red Team), and nobody separates API content-filter blocks from model refusals. A practitioner-built open harness that covers exactly those points and is reproducible could become the neutral reference. That matters because the labs report little about over-refusal themselves: a Cloud Security Alliance guide notes most providers publish no over-refusal figures. I found no product for the router specifically. Existing gateways (Portkey, Bifrost, HydraLLM, Lunar) fall back only on HTTP status codes, not on detected refusals. But the moat is thin: refusal detection is easy to add to those gateways, and verification programs shrink the problem for anyone willing to get vetted. The best angle is probably to package it for small MSSPs and pentest shops as an audit trail. That means per-hop logs fit for client reports, routing to local open-weight or vetted-tier endpoints, and refusal-rate data from the leaderboard to decide routing order. The leaderboard then works as the distribution channel and the router as what customers pay for. Some figures here, including model names, refusal percentages and launch dates, came from secondary coverage I could not check against primary sources.
- Artificial Analysis Cyber Index
This is the closest threat to the leaderboard idea. A secondary report says it is a public leaderboard launched in September 2026 that shows refusal rates alongside defensive code-security performance across frontier models, with incident response planned later. Artificial Analysis already has the brand and the traffic. I only saw it through secondary coverage, so the exact model names and numbers are unverified.
- Defensive Refusal Bias (Scale AI, ICLR 2026 workshop)
An academic study of 2,390 defensive prompts taken from a collegiate cyber defense competition. Refusals were highest for system hardening (43.8%) and malware analysis (34.3%), and stating authorization made refusals more likely. It validates the problem, but it is a one-time paper, not a weekly tracker.
- defenders-dilemma
A small single-author GitHub repo that measures refusals on incident-response artifacts across five models. It separates API-level content-filter blocks from model refusals. It is a proof of concept, not a maintained product.
- cyber-refusal-eval
A hobby repo with a multi-turn eval of how cyber refusals decay over a conversation. It shows individuals are starting to build harnesses.
- CyberSecEval 2 (Meta)
An established open benchmark from 2024 that includes a false refusal rate metric on borderline cyber prompts. It is dated and not run as a live leaderboard, but it is the reference people will compare against.
- OpenAI Trusted Access for Cyber / GPT-5.4-Cyber
Big-lab feature that cuts the refusals themselves. Verified defenders get versions of the models with less safeguard friction, and higher tiers can use a permissive cyber-tuned variant. This weakens the router's value for customers who get verified.
- Anthropic Cyber Verification Program
Expanded in October 2026 to Defense, Red Team and Specialized tiers. Small security firms and individual researchers are explicitly eligible, and the program cuts automated blocks on malware analysis and vulnerability work. This is a direct substitute for refusal routing among Anthropic users.
- WhiteRabbitNeo (Kindo)
An uncensored open-weight security model built on Qwen. It is the kind of fallback target the router would send to, and it shows pentesters already get around refusals by self-hosting.
- Portkey / Bifrost / HydraLLM gateways
Mature OpenAI-compatible gateways with fallback chains and logging, but they fall back on HTTP status codes, not on detected refusals. Adding refusal detection to them would take little work, so they are the likely fast followers for the router.
Checked 2026-10-15
Risks
- Providers may treat refusal routing as guardrail evasion and cut off API keys
- Orion-1 and Daybreak access may stay enterprise-gated, which leaves only open-weight fallbacks
- The task set needs careful curation so the benchmark itself doesn't become a misuse cookbook
- Labs may loosen policies for verified defenders and remove the pain
Strong tech readiness and team fit; market pull is the weak point (6).
tech 8 · pull 6 · space 7 · fit 8 · build 8
Exposed
Companies that could benefit or be threatened. News and context, not investment advice.
Momentum of its main topic
Sources
- AI guardrails designed to stop hackers are now blocking defenders, and Orion-1 aims to fill the gapThe Decoder
- Using Gemini 4 Argon to protect against Cyber attackersGoogle DeepMind
- SentinelOne cuts malware analysis from weeks to hoursOpenAI
- Bank of America hired 1,000 contractors to patch software flaws exposed by Anthropic's MythosCNBC
- Cohere moves to buy AI cybersecurity startup AISLEInvesting.com
Status history
- 2026-10-15 Flagged as buildable