Graph-based policy constrains LLM agents for topology-aware incident response

Sentinel-RL separates network-graph analysis from language generation, using reinforcement learning to recommend constrained investigative actions while the LLM explains them.

PaperIndustrycs.CRarXiv:2609.04159v1
Uday Vallabhaneni · Cassie L. Cagwin · David J. Wild

Indiana University

Research Digest··2 min read
Vallabhaneni, Cagwin, and Wild built a security-operations architecture in which a graph encoder and reinforcement-learning policy analyze enterprise authentication activity instead of placing the full network state into an LLM’s context. On public cyber-security data and an Indiana University computing cluster, the system achieved 0.91 precision and 0.87 recall on labeled red-team events, with a median 6.3-second end-to-end response cycle.

What they did

The authors represented live authentication activity as a heterogeneous graph, whose different node and edge types capture entities such as hosts, users, and login events. A graph-attention encoder compressed the relevant subgraph into a fixed-size state, and a Proximal Policy Optimization policy converted that state into actions drawn from a constrained investigative set.

The LLM did not independently choose containment actions. It consumed the policy’s recommendations and generated analyst-readable explanations subject to a critic and human approval. The system was tested using the LANL Comprehensive, Multi-Source Cyber-Security Events dataset and deployed on the Indiana University Quartz HPC cluster with a Neo4j graph database.

Key findings

  • A two-phase Neo4j CREATE pipeline ingested a 24-million-edge authentication subgraph in 14.2 minutes on one 32-core node, about 24 times faster than the authors’ canonical MERGE-based pipeline.
  • Across 50 trials, the sliding-window alert engine triggered a threshold of 25 events within 10 seconds in no more than 2.5 seconds.
  • After 200 PPO training iterations, the policy reached a mean episodic return of 8.74 ± 0.31. On held-out labeled red-team events, it achieved 0.91 precision and 0.87 recall.
  • The integrated detect–investigate–recommend–human-approve loop had a median completion time of 6.3 seconds.

Why it matters

The work offers a concrete alternative to asking an LLM to reason directly over an enterprise-scale network graph. Moving topology-sensitive decisions into a graph model and constrained policy can make recommendations more auditable and structurally consistent, while retaining the LLM for explanation and analyst interaction.

Caveats

The reported evidence covers one public event dataset and one HPC deployment, rather than multiple production security operations centers. The abstract does not report comparisons with expert analysts, alternative graph policies, or unconstrained LLM-agent baselines, and held-out red-team labels may not capture the diversity, drift, and false-positive costs of live enterprise attacks. Containment also remains dependent on human approval rather than demonstrated safe autonomy.

§
newspaper

Research Digest

Articles published under the Zotpaper byline are synthesized from multiple source publications by our AI editor and reviewed by our editorial process. Each story combines reporting from credible outlets to give readers a balanced, comprehensive view.