Design Principles for the Construction of a Benchmark Evaluating Security Operation Capabilities of Multi-agent AI Systems
Organizations: Cyber Security Laboratory Pennsylvania State University, University Park
Abstract
As Large Language Models (LLMs) and multi-agent AI systems are demonstrating increasing potential in cybersecurity operations, organizations, policymakers, model providers, and researchers in the AI and cybersecurity communities are interested in quantifying the capabilities of such AI systems to achieve more autonomous SOCs (security operation centers) and reduce manual effort. In particular, the AI and cybersecurity communities have recently developed several benchmarks for evaluating the red team capabilities of multi-agent AI systems. However, because the operations in SOCs are dominated by blue team operations, the capabilities of AI systems & agents to achieve more autonomous SOCs cannot be evaluated without a benchmark focused on blue team operations. To our best knowledge, no systematic benchmark for evaluating coordinated multi-task blue team AI has been proposed in the literature. Existing blue team benchmarks focus on a particular task. The goal of this work is to develop a set of design principles for the construction of a benchmark, which is denoted as SOC-bench, to evaluate the blue team capabilities of AI. Following these design principles, we have developed a conceptual design of SOC-bench, which consists of a family of five blue team tasks in the context of large-scale ransomware attack incident response.
Figures & tables
| Ring | Pts | Meaning |
|---|---|---|
| Bullseye | 3 | Correct conclusion + evidence-backed justification |
| ( 2 concrete evidence objects where applicable). | ||
| Inner | 2 | Correct conclusion but missing one key justification element |
| (weak correlation, thin evidence, or vague tie). | ||
| Outer | 1 | Directionally plausible but underspecified |
| (e.g., “multi-host activity increasing” without anchors). |
| Field | Value / Interpretation |
|---|---|
| EventID | 7 (Sysmon ImageLoad event). |
| Provider.Name | Microsoft-Windows-Sysmon . |
| Provider.Guid | 5770385F-C22A-43E0-BF4C-06F5698FFBD9 . |
| Version | Event schema version ( 3 in this instance). |
| Level | Severity or verbosity level ( 4 ). |
| Task | Subcategory associated with this event ( 7 ). |
| Outcome/Action | Description | Available Points |
| Relevant Data Sources | 15 points total | |
| Irrelevant Data Source | Identifies a data source that is not part of the large-scale attack. | -2 points each |
| Inaccurate Relationship | Incorrectly identifies that information correlates between two or more data sources. | -1 points each |
| Threat Graph | 35 points total | |
| Node Accuracy | ||
| Incorrect Artifact | Identifies artifact (i.e., IP Address, Process ID) unrelated to large-scale attack. | -1 point each |
| { "stage_timestamp": "01/01/2025, 00:00:00 AM", "containment_actions": [ "Isolate ENG-WKS-12 and ENG-WKS-17 from the corporate LAN", "Block outbound SMB and HTTPS traffic from ENG-SRV-05 to 185.199.110.0/24" ], "action_targets": { "hosts": ["ENG-WKS-12", "ENG-WKS-17", "ENG-SRV-05"], "ips": [], "subnets": ["185.199.110.0/24"], "user_accounts": [], "user_groups": [], "services": [], "other": [] }, "reasoning_evidence": "Isolation and outbound blocking are selected to maximize security impact while minimizing operational disruption: both workstations are non-critical endpoints and blocking ENG-SRV-05 outbound traffic preserves service availability while halting lateral movement. Current data shows ENG-WKS-12 and ENG-WKS-17 exhibit rapid encryption and unauthorized C2 connections. ENG-SRV-05 is initiating anomalous SMB flows to a malicious subnet. If containment is delayed, ransomware will likely propagate across engineering hosts and enable further data exfiltration through ENG-SRV-05." } |
| Level | Points | Description |
|---|---|---|
| Fully correct | 20 | All actions exactly match the ground truth. |
| Partially correct | 10 | Actions address part of the ground truth but are incomplete or partially misapplied. |
| Incorrect or missing | -20 | Actions are completely wrong, absent, or mostly incorrect, increasing operational risk and potential consequences. |
| Level | Points | Description |
|---|---|---|
| Fully supported | 40 | Reasoning is clear, logical, and fully supported by evidence from the provided data sources. |
| Partially supported | 20 | Reasoning is somewhat clear but incomplete or partially unsupported by evidence. |
| Unclear or unsupported | -20 | Reasoning is unclear, illogical, or unsupported. |
AI Agent Security Benchmarks
AI agent security benchmarks measure how tool-using and autonomous systems handle attacks, privacy risks, authorization, and harmful actions.
See all 301 papers