Papers for

security operation teams

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Adaptive zero trust response balances security and system continuity

Zero Trust-Enabled Adaptive Incident Response using Hierarchical Reinforcement Learning

Abstract: Modern enterprises increasingly operate through complex information systems (IS) enabled by cloud computing, remote and hybrid work practices, and digitally integrated supply chains. These structural shifts have expanded organizational attack surfaces and weakened traditional perimeter-based trust assumptions, giving rise to new and persistent forms of cyber threats. In response, adversaries have shifted toward identity-centric, trust-based intrusion techniques that exploit legitimate access within organizational systems. This evolution has created a pronounced speed asymmetry, whereby attackers can adapt and act at machine speed while defenders remain constrained by reactive or rule-based incident response (IR) processes. Drawing on design science research, we propose ZT-AIR, an adaptive IR artifact that uses zero trust architecture as its design theory and hierarchical reinforcement learning as its kernel theory. ZT-AIR learns context-aware trust decisions, separates strategic prioritization from tactical execution, encodes zero-trust controls as actions, and jointly optimizes security effectiveness and operational continuity. Experimental results across diverse adversarial strategies, network scales, and defense environments show that ZT-AIR achieves a strong balance between security and continuity through frequent, minimally disruptive interventions. Practitioner validation further confirms the design's practical viability. This study contributes to IS research by extending computational design science from threat identification to response execution, theorizing zero trust architecture for adaptive IR, and deriving reusable design principles for adaptive decision support artifacts.

Wed 28 OctCryptography and Security
The gist
Modern companies face fast and smart cyber attackers that exploit trusted access within their systems. The authors designed a system called ZT-AIR that learns how to quickly decide what security actions to take without disrupting normal operations. It uses a layered learning approach to separate planning from action and adapts its responses based on context. Tests show it manages to keep systems safe while avoiding unnecessary interruptions.
Open → 2610.38146v1

Lstm detects unusual behavior in webassembly to spot attacks

WADE: An LSTM-Based Anomaly Detection Engine for WebAssembly Applications

Abstract: WebAssembly (Wasm) enables near-native performance for web applications through a portable and sandboxed execution model. However, its limited runtime protection mechanisms (e.g., the lack of stack canaries and address space layout randomization (ASLR)) leave Wasm applications vulnerable to traditional attacks. We present WADE (WebAssembly Anomaly Detection Engine), a system that detects anomalous runtime behaviors in browser-executed WebAssembly applications. WADE monitors function-level execution traces collected under benign conditions and trains a Long Short-Term Memory (LSTM) network to learn the normal execution behavior of each application. At runtime, the model flags deviations from these learned patterns as potential attacks. Unlike signature-based approaches, WADE builds application-specific behavioral models, enabling detection of both known and previously unseen attacks without per-vulnerability signatures. We evaluate WADE on a dataset of 67 WebAssembly applications spanning ten vulnerability classes, achieving zero false negatives and a 0.42% false positive rate.

Thu 22 OctCryptography and SecurityMachine Learning
The gist
WebAssembly runs web apps fast but lacks some protections against hacking methods. The authors created WADE, a system that watches how WebAssembly apps normally behave and learns these patterns using a type of AI called LSTM. When the app acts differently from learned normal behavior, WADE raises an alert. This method can catch new attacks without needing to know their details in advance. Tests showed WADE can detect all attacks with very few false alarms.
Open → 2610.31984v1

Execweave links software actions to system events for clearer traces

ExecWeave: Cross-Layer Execution Provenance for Observable Agentic Software

Abstract: Agentic software invokes tools, launches processes, accesses files, and communicates with local or remote services. Application traces describe logical operations, whereas operating-system telemetry records machine activity without necessarily identifying the responsible agent action. Relating these evidence planes is a reconstruction problem: a plausible but unsupported association can assign an effect to the wrong principal. We present ExecWeave, a local-first system that materializes provider semantics and independently observed runtime events into a typed execution graph. The implementation retains separate source artifacts, distinguishes logical occurrences from repeated evidence, and records attribution, inference, and causal-status metadata. An optional command-to-process correlator emits a non-causal inferred bridge only when its bounded search yields one compatible observed process; uniqueness within this observed candidate set is not a guarantee of causal correctness. OS-observed file and network effects acquire a semantic tool or agent principal only through an observed process plus a justified command-to-process association; session-correlated file-system events do not by themselves provide that principal. Source code is available at https://github.com/Irish-kw/ExecWeave.

Thu 15 OctCryptography and Security
The gist
When software runs, it does many things behind the scenes like opening files or talking to other computers. Computer systems record low-level activities but often don't show which part of the software caused them. The authors designed ExecWeave to connect what the software intends to do with what actually happens on the computer by creating a detailed graph of actions and their effects. This helps people understand exactly which software commands led to each system event, making it easier to trace and debug complex software behaviors.
Open → 2610.21146v1

Dark web CAPTCHA solver boosts success with local image tools

DarKnight: Retrieval-Guided Agentic Framework for Breaking Dark Web CAPTCHA Gates

Abstract: Cyber Threat Intelligence (CTI) investigators who monitor dark web marketplaces for leaked credentials and breach listings must pass the diverse CAPTCHAs that operators deploy to block automated collection. Existing solvers either need unscalable per-site fine-tuning or rely on commercial Vision-Language Model (VLM) APIs, which surrender operational sovereignty: provider policies, Tor-exit blocking, government regulation, or model updates outside the investigator's control can halt or alter the solver overnight, and per-call costs recur with every session and retry. We present DarKnight, a self-improving agentic framework designed to run on a single workstation GPU inside an investigator's Tor crawler and solve CAPTCHAs with small, locally hosted open-weight VLMs that no provider decision can withdraw, without per-market training or third-party services. For each CAPTCHA, DarKnight retrieves successful and failed past attempts on similar images (dual-signal RAG), composes an image-specific preprocessing pipeline, and learns from the site's pass/fail verdict. In a case study on four real-world dark web marketplaces, agentic tool selection outperformed parameter scaling. A deployable open-weight VLM with DarKnight reached 83.2\% on the most heavily defended market, 37.2 percentage points above its base model, outperforming even the frontier Claude Opus~5 (44%). DarKnight recovered 48.2% of baseline failures at a 7.6% degeneration cost, indicating that selective tool use can avoid much of the degradation caused by uniform preprocessing.

Wed 14 OctCryptography and SecurityComputer Vision and Pattern Recognition
The gist
CAPTCHAs are puzzles that websites use to stop automated bots from accessing information. On the dark web, investigators need to bypass these to gather cyber threat data. The authors created DarKnight, a system that uses small local AI tools to solve CAPTCHAs without relying on outside services. It learns from past successes and failures to improve over time, reaching much better solving rates than previous models. This helps investigators get around strict protections without losing control to third-party providers.
Open → 2610.19830v1

Small cybersecurity transformer screens files fast and accurately

CT0: Cybersecurity Transformer

Abstract: General-purpose frontier models are large, expensive to run, and increasingly reluctant to engage with authorised defensive- and offensive-security work. We ask the opposite question: how small can a cybersecurity-specialist transformer be while remaining genuinely useful to a security practitioner? We introduce CT0, a Cybersecurity Transformer architecture, and CT0-Micro, its first incarnation: a compact (~4B-parameter) model built on the open base model, whose backbone is specialised by two-phase on-policy distillation on our Cybersecurity AI (CAI) dataset. CT0 serves two modes from one set of weights: System 1 answers typed security decisions (is this file suspicious, is this request an attack, did the model just refuse) in a single forward pass without generating a token, System 2 is the usual tool-using agent, and a confidence gate spends generation only where the fast path is unsure. Specialisation lifts the agentic path: CT0-Micro solves 21.1% of cybench-subtask against 7.6% for its base, above every open model of comparable footprint and the densest cybersecurity capability per parameter we measured. The fast path is what the architecture buys: CT0-Micro screens eighty files per second for indicators of compromise, catches its own refusals at 96.5% accuracy in 47 ms where the model judging itself reaches 76.5% in 254 ms and misses half of them, flags jailbreak requests at AUROC 0.966 in 8 ms, and, generating only for the facts it is unsure about, extracts vulnerability facts more accurately than either mode alone at a fifth of the generative cost. All of it is built in about 314 RTX PRO 6000 GPU-hours and served from one workstation GPU, with no policy layer between operator and target. Across eighteen benchmarks and use cases run with one checkpoint and head, we report where the design helps, where it does not, and what it still lacks.

Mon 12 OctCryptography and Security
The gist
Large AI models usually need lots of computing power and often avoid security tasks. The authors asked how small a specialized cybersecurity AI can be while still useful. They built CT0-Micro, a compact model that quickly spots suspicious files, detects attacks, and judges when it’s unsure. This model runs efficiently on a single workstation GPU and performs better on security tests compared to similar small models.
Open → 2610.16550v1

Llm agents show gaps investigating cyberattacks with varying logs

APTInvestBench: Evaluating Autonomous APT Investigation under Varying Telemetry

Abstract: Large language model (LLM) agents could help security operations centers (SOCs) investigate advanced persistent threats (APTs) by turning weak leads into evidence for intrusion scoping and response. Yet success under one telemetry setting does not establish robustness to changes in log collection, retention, or sampling. We introduce APTInvestBench, a benchmark for evaluating cross-telemetry robustness in autonomous APT investigation. It comprises 370 cases across seven SOC-inspired conditions, derived from 56 report-informed attack reconstructions with 16.4 million log records. Agents investigate unverified leads and submit reports with record-level citations. Fixed action-level support requirements track sufficient evidence across available logs, query returns, and formal citations, separating telemetry limitations from acquisition and reporting gaps. Across eleven LLMs, agents acquire sufficient evidence for 44.3% of recoverable attack actions on average, while formal citations support only 25.0%. More importantly, aggregate coverage can conceal substantial instability: from Full to endpoint-only telemetry, coverage declines by only 1.6 percentage points, yet 35.5% of previously covered actions lose sufficient citation support despite remaining recoverable. Across four frameworks, such losses persist even when registered supporting records remain unchanged. APTInvestBench provides reusable investigation environments and diagnostic evaluation for identifying these gaps and developing more reliable defensive agents.

Wed 30 SeptCryptography and SecurityArtificial Intelligence
The gist
Investigating complex cyberattacks relies on analyzing computer logs, but these logs can vary in type and detail. The authors created a test called APTInvestBench that checks how well AI agents find evidence of attacks when different types of logs are available. They found that although AI agents often find important attack details, their ability to properly support these findings with evidence can drop if the quality or type of logs changes. This work helps identify when and why AI tools might fail in real-world security investigations.
Open → 2609.38954v1

Computer-use agent safety improved by combining reasoning with tool checks

SCOUT: Synergizing Reasoning and Tool-Use for Computer-Use Safety

Abstract: Computer-use agents (CUAs), while capable of completing computer tasks in everyday and professional workflows, can cause unintended harm even under benign instructions and environments. However, detecting such harm remains challenging. First, it requires careful, task-specific reasoning: verifiers guided only by general safety criteria often overlook many important but subtle harmful behaviors. Second, it requires active investigation: past trajectory screenshots show what the agent did but not always what actually changed in the environment, so LLM-as-a-judge verifiers that rely on screenshots alone may be unable to determine the actual consequences of actions. To address these challenges, we introduce SCOUT, a two-stage agentic safety verifier that synergizes reasoning-intensive rubric generation with tool-intensive evidence gathering. First, our SCOUT rubric generator extensively reasons over the task and the agent's trajectory to determine what successful and safe execution should entail, generating task-specific completion and safety rubrics. Then, our SCOUT probing agent follows these rubrics to interact with the post-execution environment and collect grounded evidence for final safety and completion judgments. We evaluate our framework on two computer-use safety benchmarks. On AutoElicit-Bench, SCOUT achieves 75.4 unsafe F1 and 74.5 completion F1, outperforming LLM-as-a-judge verifiers and naive tool-use verifiers. SCOUT leads on OS-Blind with 76.4% unsafe detection accuracy. Test-time reflection reduces final unsafe execution rates from 30.2% to 17.2% on AutoElicit-Bench. Ablations and analysis show that tool-free rubric generation in SCOUT elicits substantially more reasoning and is crucial for safety detection across verifier backbones, especially non-frontier ones. A preliminary extension to coding tasks shows that SCOUT can support safety verification beyond computer-use.

Mon 28 SeptComputation and LanguageArtificial IntelligenceSoftware Engineering
The gist
Computer-use agents can follow instructions but sometimes cause accidental problems. The authors created SCOUT, a system that first thinks carefully about what a task should do safely, then uses tools to check what actually happened after the agent finished. This combined approach helps spot subtle harms better than previous methods that only looked at screenshots or used general safety rules. SCOUT was tested on computer task safety benchmarks and showed better accuracy in detecting unsafe behavior and confirming successful completion. It also showed promise for checking safety in coding tasks.
Open → 2609.36201v1

System One models show limits in automated agent security decisions

Evaluating System One Models for Agent Security Decisions: Reliability, Calibration, and Selective Automation

Abstract: Model-based judges support agent security by detecting prompt injections, assessing interaction risks, and screening harmful requests. System One models expose typed decisions with probabilities that software can use to allow, block, or escalate inputs, but whether these probabilities support reliable automated security decisions remains unclear. We evaluate Jev, Laya, Decider, and Bespoke Nimble against specialized classifiers and language-model judges, examining decision accuracy, probability calibration, and selective automation. We identify three main findings. (1) Strong overall performance and favorable average calibration can hide systematic failures on particular attack groups, including attacks that models confidently classify as safe. (2) Under strict limits on missed attacks, the evaluated policies allow few inputs automatically, and choosing separate allow and block thresholds increases automation mainly by blocking more inputs. Even policies that meet error limits during validation can exceed them on unseen inputs. (3) A second judge can detect some missed attacks, but it may also reject more benign inputs and repeat the first model's high-confidence errors. These findings show that model accuracy, probability calibration, and the behavior of the resulting decision policy must be evaluated together.

Sun 27 SeptCryptography and SecurityArtificial IntelligenceSoftware Engineering
The gist
Detecting harmful inputs to AI agents is hard, especially when models mistakenly treat attacks as safe. The authors tested several security judging systems and found that even if these models look accurate overall, they can confidently miss certain types of attacks. Using strict rules to block or allow input leads to rejecting many inputs automatically and still missing some attacks on new data. Adding a second model to catch errors helps but also blocks more safe inputs and repeats some mistakes. The authors emphasize checking model accuracy, confidence, and decision rules together to better secure AI agents.
Open → 2609.33401v1

Electromagnetic signals reveal hardware trojans tampering with kernel memory

Assessing Runtime Electromagnetic Detection of CPU Hardware Trojans Targeting Kernel Memory

Abstract: Side-channels are a promising approach for hardware trojan detection, as they can passively reveal malicious hardware activity without requiring additional circuitry or destructive analysis of the device under test. This work investigates the use of electromagnetic (EM) emanations for runtime detection of hardware trojan attacks. Using an open-source hardware trojan that implements an arbitrary memory-write primitive, we tamper with the kernel memory of a Linux system running on a RISC-V microarchitecture and perform a real-time baseline detection using the processor's EM emissions. Our results indicate that, under certain conditions, hardware trojans can be detected indirectly through the anomalous software behavior they enable.

Sat 19 SeptCryptography and Security
The gist
Hardware trojans are secret, malicious changes to computer chips that can cause harm. The authors studied if tiny electromagnetic signals given off by a computer’s processor could help detect such hidden changes while the computer runs. They tested this on a processor running Linux and found that these signals could indirectly show when a trojan caused unusual software actions. This method doesn’t require damaging the chip and can act in real time, making it a promising way to catch hardware problems.
Open → 2609.23186v1

File event stitching improves ransomware detection at first encrypted file

DEFEAT: Stitching Fragmented File I/O Contexts for Early Ransomware Detection

Abstract: Ransomware increasingly fragments its file operations across temporary and intermediate files, scattering the semantic context that links individual I/O events to an overarching encryption campaign. This fragmentation defeats existing detectors that reason over isolated file streams -- whether pattern-based methods that match rigid event sequences or learning-based methods that require accumulating statistical evidence across many files. We present DEFEAT, a framework that reconstructs this fragmented, scattered context by grouping causally related file events into File Event Gadgets (FEGs), semantically coherent units that capture the full intent behind sequences of file operations spanning multiple dynamically created files. Unlike provenance graphs (system-wide causal graphs that record relationships among all OS entities, such as processes, files, sockets, and registry keys, across the entire system), FEGs are scoped to the file-operation context of a single user asset, enabling lightweight, targeted analysis without whole-system instrumentation. Each FEG is modelled as an attributed control flow graph (ACFG) and embedded via a graph neural network for unsupervised clustering, enabling analysts to label entire behavioural clusters rather than individual samples, reducing annotation effort by 94%. Evaluated on a corpus of 97,816,471 file I/O events spanning 67 ransomware families, DEFEAT achieves 99.2% detection accuracy and outperforms state-of-the-art methods including UNVEIL, RWGuard, and Peeler by 6.57 to 7.56%. The framework operates at the granularity of a single file encryption: because each ACFG represents exactly one FEG (one user asset context), a cluster label can be assigned as soon as the first file operation completes, enabling detection at the first encrypted file.

Fri 18 SeptCryptography and Security
The gist
Ransomware attacks hide by breaking their file operations into many small steps across multiple temporary files, making it hard to spot. The authors designed DEFEAT, a system that groups related file actions into one meaningful unit, capturing the attack's full intent. This lets DEFEAT detect ransomware very early, at the very first encrypted file, with high accuracy. It works without needing to monitor the entire system, focusing narrowly on each user file’s activity.
Open → 2609.21426v1

Machine learning improves detection of abused security software

Identifying Security Platform Product Abuse with Machine Learning

Abstract: Product abuse is an individually rare, but growing, problem across the SaaS industry. Highly sophisticated threat actors can misuse security platforms within customer environments or conduct bypass experiments on the product itself. Threat actors can leverage living-off-the-land (LOTL) attacks to avoid using cumbersome, frequently detected malware. Remediating this threat requires collecting multiple data modalities across different types of databases, addressing a cold-start problem in the intrinsic rarity of such sophisticated but dangerous events, and designing within the constraints of real-world deployment (e.g., cost, user behavior, performance, etc). To wit, we provide the first study of such a whole-system defense, especially with respect to a deployed and operational capability. Our results show an increase in product abuse coverage by 35\%, a 30\% reduction in monthly alerts, and adaptability to changes in malicious actors' behavior. We review both the constraints we considered in designing the system to meet operational requirements and a retrospective evaluation of the value of explainable features and counterfactual performance on previously identified attacks.

Fri 18 SeptCryptography and SecurityMachine Learning
The gist
Some bad actors use security software in sneaky ways to avoid being caught, which is a hard problem because it happens rarely and in many complex ways. The researchers studied how to spot this misuse by looking at many types of data and using machine learning models that adapt to new tricks. They built a system that can find 35% more abuse cases while reducing false alarms by 30%, which helps security teams focus on real threats. The system also explains why it makes decisions, which helps understand attacks better.
Open → 2609.21303v1

Verifiable approval cards stop browser AI security attacks

The Verifiable Action Card: Trustworthy Human-in-the-Loop Control for Secure Autonomous Agents

Abstract: Agentic browsers can execute security-sensitive actions under a user's authenticated session, making indirect prompt injection and deceptive confirmation interfaces a direct threat to action integrity. Existing human-in-the-loop (HITL) safeguards are insufficient when the approval prompt itself can be influenced by untrusted page content or model-generated text. We present the \emph{Verifiable Action Card} (VAC), an architectural defence that reconstructs approval information from the ground-truth pending browser action and trusted intent provenance, renders it out-of-band in the trusted browser chrome, and binds approval to the exact action re-verified at dispatch. VAC combines provenance fencing, a ground-truth action descriptor, default-deny confirmation, provenance-aware risk gating, and execution binding. We implement VAC in a complete agentic browser and evaluate it on a 24-scenario benchmark covering confused-deputy attacks, Lies-in-the-Loop dialog forging, indirect prompt injection, adaptive action substitution, provenance evasion, and legitimate tasks. Across the evaluated LLMs, attack success without VAC ranges from $68\%$ to $100\%$, whereas VAC reduces attack success to $0\%$ on every model, with $78\%$ legitimate-task completion and a $0\%$ false-block rate. These results show that grounding approval in the action that will actually execute provides architectural protection against security failures that prompt-level defences and conventional HITL confirmation cannot reliably prevent.

Wed 16 SeptCryptography and Security
The gist
Some internet browsers that use AI assistants can perform actions for users, but these can be tricked by fake or misleading approval messages. The authors created a new system called the Verifiable Action Card (VAC) that shows users clear, trustworthy details about what actions the browser will perform before asking for approval. By separating this approval from the webpage and linking it directly to the actual action, VAC prevents attackers from fooling users. Tests show VAC stopped all attempted attacks without blocking real user tasks.
Open → 2609.18411v1