SOC-Agent-Traces-100K

Multi-step SOC investigation agent traces in session-trace format. Each record is a complete investigation session: an alert arrives, an analyst agent gathers evidence through nine read-only tools, and closes with a structured JSON triage report.

Instead of single-turn alert → answer pairs, every record captures the full reasoning trajectory:

alert → get_surrounding_events → get_process_tree → lookup_attack
      → search_sigma → get_asset_context → get_related_alerts
      → calculate_risk → retrieve_playbook → triage report

Use cases

• Agent SFT / tool-use training (chat-format traces with structured tool calls)
• Agent evaluation and replay benchmarks
• Triage-decision and confidence-calibration research
• Detection-engineering training data (ATT&CK + Sigma grounded)

Schema

Field	Type	Description
scenario_id	string	Unique scenario identifier
alert	JSON string	Alert object (id, title, severity, source, host, user, description)
environment	JSON string	Organization context (industry, security stack, asset focus)
ground_truth	JSON string	Verdict, ATT&CK techniques, root cause, IOCs
trace	JSON string	Full session as OpenAI-style messages with tool_calls
tool_calls	JSON string	Flattened list of tool invocations with argument/result summaries
evidence	JSON string	Decisive evidence items cited in the report
decision	string	escalate / monitor / close
confidence	float	Analyst confidence 0-1
success	bool	Whether the trace reaches the correct verdict
archetype	string	Scenario archetype (32 families)
verdict	string	malicious / benign
n_tool_calls	int	Number of tool invocations
n_messages	int	Number of session messages

Corpus statistics

• Total traces: 100000
• Verdicts: {"malicious": 89652, "benign": 10348}
• Decisions: {"monitor": 17203, "close": 7319, "escalate": 75478}
• Successful traces: {"False": 17200, "True": 82800}
• Avg tool calls / trace: 6.64 · avg messages / trace: 16.28

Archetype distribution

Archetype	Traces
rdp_bruteforce	6900
registry_persistence	6885
cloud_exfil	6861
process_injection	6853
browser_cred_theft	6837
phish_macro_powershell	6785
masquerade_binary	6633
ad_discovery	6545
wmi_remote	5913
smb_lateral	5693
log_clear	4948
dev_build	4260
dns_tunnel	3451
ps_download_cradle	3199
c2_beacon	3089
backup_spike	3018
cloud_account_anomaly	2226
pass_the_hash	2138
kerberoast	1949
edr_tamper	1019
vuln_scanner	1014
scheduled_task_persistence	614
new_service_change_window	591
admin_ps_maintenance	495
webshell	477
lsass_dump	432
sccm_deployment	379
av_selftest	293
onedrive_bulk_sync	211
ransomware_staging	205
windows_update	81
helpdesk_reset_flood	6

Tool usage

Tool	Calls
lookup_attack	108882
get_surrounding_events	100000
calculate_risk	100000
get_asset_context	97768
search_sigma	86208
get_process_tree	69737
retrieve_playbook	50904
get_related_alerts	49783
search_cve	477

Tools (all read-only simulations)

get_surrounding_events, get_process_tree, lookup_attack, search_sigma, get_asset_context, get_related_alerts, calculate_risk, search_cve, retrieve_playbook. No tool executes commands against real systems; every result is a deterministic lookup over the scenario's synthetic evidence store.

Trace format

trace follows the OpenAI chat-message convention: assistant messages carry tool_calls (id, function name, JSON arguments) and tool results arrive as role="tool" messages linked by tool_call_id. The final assistant message contains the triage report as a fenced JSON block with keys verdict, decision, confidence, techniques, summary, evidence_ids, recommended_actions.

Splits

Stratified by verdict and archetype: train 90% / validation 5% / test 5%. Traces with success=false (~12%) are flawed investigations (missed evidence step → wrong or weak conclusion) intended for contrastive training and evaluation; filter them out for SFT.

Generation methodology

Traces are synthesized by a reference investigation policy executing against a simulated SOC backend (per-scenario evidence stores over 32 attack and false-positive archetypes), with step jitter, dead-end lookups, and analyst persona variation. Ground truth is known by construction. All organizations, hosts, users, IPs, domains, and hashes are synthetic.

Companion assets

• Dataset (sibling): alirezaaminzadeh/soc-agent-traces-10k
• Fine-tuned agent: alirezaaminzadeh/soc-agent-traces-smollm3-3b
• Baseline classifiers: alirezaaminzadeh/soc-traces-baseline
• Live investigation demo: alirezaaminzadeh/soc-agent-traces

License

Apache 2.0. Knowledge-base records are condensed paraphrases of public MITRE ATT&CK, Sigma HQ, and NVD material.