Human Feedback Types
missingNone explicit
No explicit feedback protocol extracted.
"Large language models and LLM-based agents are increasingly used for cybersecurity tasks that are inherently dual-use."
HFEPX · Eval paper review
Noa Linder, Meirav Segal, Omer Antverg, Gil Gekker +4 more
Published
Feb 17, 2026
Citations
0
Trust level
Low
Usefulness score
0/100 (Low)
Extraction confidence
15% (Low)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Feb 18, 2026
This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.
Use this as background context only. Do not make protocol decisions from this page alone.
All signals on this page are inferred from the abstract only and may be inaccurate. Do not use this page as a primary protocol reference.
Best use
Background context only
Use if you need
Background context only.
What to verify
Read the full paper before copying any benchmark, metric, or protocol choices.
Main weakness
This paper looks adjacent to evaluation work, but not like a strong protocol reference.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
Large language models and LLM-based agents are increasingly used for cybersecurity tasks that are inherently dual-use. Existing approaches to refusal, spanning academic policy frameworks and commercially deployed systems, often rely on broad topic-based bans or offensive-focused taxonomies. As a result, they can yield inconsistent decisions, over-restrict legitimate defenders, and behave brittlely under obfuscation or request segmentation. We argue that effective refusal requires explicitly modeling the trade-off between offensive risk and defensive benefit, rather than relying solely on intent or offensive classification. In this paper, we introduce a content-based framework for designing and auditing cyber refusal policies that makes offense-defense tradeoffs explicit. The framework characterizes requests along five dimensions: Offensive Action Contribution, Offensive Risk, Technical Complexity, Defensive Benefit, and Expected Frequency for Legitimate Users, grounded in the technical substance of the request rather than stated intent. We demonstrate that this content-grounded approach resolves inconsistencies in current frontier model behavior and allows organizations to construct tunable, risk-aware refusal policies.
These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.
None explicit
No explicit feedback protocol extracted.
"Large language models and LLM-based agents are increasingly used for cybersecurity tasks that are inherently dual-use."
None explicit
Validate eval design from full paper text.
"Large language models and LLM-based agents are increasingly used for cybersecurity tasks that are inherently dual-use."
Not reported
No explicit QC controls found.
"Large language models and LLM-based agents are increasingly used for cybersecurity tasks that are inherently dual-use."
Not extracted
No benchmark anchors detected.
"Large language models and LLM-based agents are increasingly used for cybersecurity tasks that are inherently dual-use."
Not extracted
No metric anchors detected.
"Large language models and LLM-based agents are increasingly used for cybersecurity tasks that are inherently dual-use."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
Large language models and LLM-based agents are increasingly used for cybersecurity tasks that are inherently dual-use.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
No explicit human feedback protocol detected.
Evaluation mode is explicit
No clear evaluation mode extracted.
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
No benchmark/dataset anchor extracted from abstract.
Metric reporting is present
No metric terms extracted.