Update README.md
Browse files
README.md
CHANGED
|
@@ -1,100 +1,85 @@
|
|
| 1 |
-
---
|
| 2 |
-
configs:
|
| 3 |
-
- config_name: alert_triaging_tii
|
| 4 |
-
data_files:
|
| 5 |
-
- split: tp
|
| 6 |
-
path: data/alert_triaging_tii_tp.jsonl
|
| 7 |
-
- split: fp
|
| 8 |
-
path: data/alert_triaging_tii_fp.jsonl
|
| 9 |
-
|
| 10 |
-
- config_name: alert_triaging_cic
|
| 11 |
-
data_files:
|
| 12 |
-
- split: test
|
| 13 |
-
path: data/alert_triaging_cic_test.jsonl
|
| 14 |
-
|
| 15 |
-
- config_name: sia_dataset
|
| 16 |
-
data_files:
|
| 17 |
-
- split: test
|
| 18 |
-
path: data/sia_dataset_test.jsonl
|
| 19 |
-
|
| 20 |
-
license: apache-2.0
|
| 21 |
-
task_categories:
|
| 22 |
-
- question-answering
|
| 23 |
-
- text-classification
|
| 24 |
-
language:
|
| 25 |
-
- en
|
| 26 |
-
tags:
|
| 27 |
-
- cybersecurity
|
| 28 |
-
- incident-analysis
|
| 29 |
-
- LLM-benchmark
|
| 30 |
-
|
| 31 |
-
|
| 32 |
-
|
| 33 |
-
|
| 34 |
-
-
|
| 35 |
-
|
| 36 |
-
|
| 37 |
-
|
| 38 |
-
-
|
| 39 |
-
|
| 40 |
-
-
|
| 41 |
-
|
| 42 |
-
|
| 43 |
-
|
| 44 |
-
|
| 45 |
-
|
| 46 |
-
|
| 47 |
-
|
| 48 |
-
|
| 49 |
-
|
| 50 |
-
|
| 51 |
-
|
| 52 |
-
|
| 53 |
-
|
| 54 |
-
|
| 55 |
-
|
| 56 |
-
|
| 57 |
-
|
| 58 |
-
|
| 59 |
-
|
| 60 |
-
|
| 61 |
-
|
| 62 |
-
#
|
| 63 |
-
|
| 64 |
-
|
| 65 |
-
|
| 66 |
-
|
| 67 |
-
|
| 68 |
-
|
| 69 |
-
|
| 70 |
-
|
| 71 |
-
|
| 72 |
-
##
|
| 73 |
-
|
| 74 |
-
|
| 75 |
-
|
| 76 |
-
|
| 77 |
-
|
| 78 |
-
|
| 79 |
-
|
| 80 |
-
|
| 81 |
-
|
| 82 |
-
|
| 83 |
-
|
| 84 |
-
|
| 85 |
-
```
|
| 86 |
-
|
| 87 |
-
## Scenario Structure
|
| 88 |
-
|
| 89 |
-
Each JSON file contains two blocks:
|
| 90 |
-
|
| 91 |
-
**1. `metadata`** — scenario identification
|
| 92 |
-
- `scenario_name`: unique ID
|
| 93 |
-
- `alert_type` (TII/CIC only): `"True"` (TP) or `"False"` (FP)
|
| 94 |
-
|
| 95 |
-
**2. `sia_components`** — the LLM task
|
| 96 |
-
- `scenario`: natural language description of the incident
|
| 97 |
-
- `tools_available`: CLI tools the LLM agent can invoke
|
| 98 |
-
- `files_available`: linked PCAP file (`capture.pcap`)
|
| 99 |
-
- `directory`: set to `"(directory_of_the_file)"`
|
| 100 |
- `questions`: Q&A pairs (with `adversarial_tactic` in SIA_Dataset)
|
|
|
|
| 1 |
+
---
|
| 2 |
+
configs:
|
| 3 |
+
- config_name: alert_triaging_tii
|
| 4 |
+
data_files:
|
| 5 |
+
- split: tp
|
| 6 |
+
path: data/alert_triaging_tii_tp.jsonl
|
| 7 |
+
- split: fp
|
| 8 |
+
path: data/alert_triaging_tii_fp.jsonl
|
| 9 |
+
|
| 10 |
+
- config_name: alert_triaging_cic
|
| 11 |
+
data_files:
|
| 12 |
+
- split: test
|
| 13 |
+
path: data/alert_triaging_cic_test.jsonl
|
| 14 |
+
|
| 15 |
+
- config_name: sia_dataset
|
| 16 |
+
data_files:
|
| 17 |
+
- split: test
|
| 18 |
+
path: data/sia_dataset_test.jsonl
|
| 19 |
+
|
| 20 |
+
license: apache-2.0
|
| 21 |
+
task_categories:
|
| 22 |
+
- question-answering
|
| 23 |
+
- text-classification
|
| 24 |
+
language:
|
| 25 |
+
- en
|
| 26 |
+
tags:
|
| 27 |
+
- cybersecurity
|
| 28 |
+
- incident-analysis
|
| 29 |
+
- LLM-benchmark
|
| 30 |
+
pretty_name: SIABench
|
| 31 |
+
|
| 32 |
+
---
|
| 33 |
+
task_categories:
|
| 34 |
+
- question-answering
|
| 35 |
+
language:
|
| 36 |
+
- en
|
| 37 |
+
tags:
|
| 38 |
+
- cybersecurity
|
| 39 |
+
- incident-analysis
|
| 40 |
+
- LLM-benchmark
|
| 41 |
+
---
|
| 42 |
+
|
| 43 |
+
# SIABENCH — Security Incident Analysis Benchmark
|
| 44 |
+
|
| 45 |
+
SIABENCH is a benchmark for evaluating LLMs on cybersecurity incident analysis tasks, developed at **Concordia University's Security Research Centre** in collaboration with **Defence Research and Development Canada (DRDC)**, published at **PST 2025**.
|
| 46 |
+
|
| 47 |
+
## Dataset Structure
|
| 48 |
+
|
| 49 |
+
SIABENCH contains three sub-datasets accessible as separate configs:
|
| 50 |
+
|
| 51 |
+
| Config | Description | Splits |
|
| 52 |
+
|---|---|---|
|
| 53 |
+
| `alert_triaging_tii` | 100 alert triaging scenarios (TII-SSRC-23 source) | `tp` (50), `fp` (50) |
|
| 54 |
+
| `alert_triaging_cic` | Alert triaging scenarios (CIC source) | `tp`, `fp` |
|
| 55 |
+
| `sia_dataset` | 23 open-ended CTF forensics scenarios | `train` |
|
| 56 |
+
|
| 57 |
+
## Loading the Dataset
|
| 58 |
+
|
| 59 |
+
```python
|
| 60 |
+
from datasets import load_dataset
|
| 61 |
+
|
| 62 |
+
# Load alert triaging (TII)
|
| 63 |
+
tii = load_dataset("SIABench/SIA_Dataset", "alert_triaging_tii")
|
| 64 |
+
|
| 65 |
+
# Load alert triaging (CIC)
|
| 66 |
+
cic = load_dataset("SIABench/SIA_Dataset", "alert_triaging_cic")
|
| 67 |
+
|
| 68 |
+
# Load CTF investigation scenarios
|
| 69 |
+
sia = load_dataset("SIABench/SIA_Dataset", "sia_dataset")
|
| 70 |
+
```
|
| 71 |
+
|
| 72 |
+
## Scenario Structure
|
| 73 |
+
|
| 74 |
+
Each JSON file contains two blocks:
|
| 75 |
+
|
| 76 |
+
**1. `metadata`** — scenario identification
|
| 77 |
+
- `scenario_name`: unique ID
|
| 78 |
+
- `alert_type` (TII/CIC only): `"True"` (TP) or `"False"` (FP)
|
| 79 |
+
|
| 80 |
+
**2. `sia_components`** — the LLM task
|
| 81 |
+
- `scenario`: natural language description of the incident
|
| 82 |
+
- `tools_available`: CLI tools the LLM agent can invoke
|
| 83 |
+
- `files_available`: linked PCAP file (`capture.pcap`)
|
| 84 |
+
- `directory`: set to `"(directory_of_the_file)"`
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 85 |
- `questions`: Q&A pairs (with `adversarial_tactic` in SIA_Dataset)
|