Datasets:
Download layers/network_security/DATASET_CARD.md from ansulev/HolyCyber-Dataset: direct link, hf CLI and curl.
- Browser
- Download file 5.57 kB
-
https://huggingface.co/datasets/ansulev/HolyCyber-Dataset/resolve/main/layers/network_security/DATASET_CARD.md
- Command line
-
hf download hf://datasets/ansulev/HolyCyber-Dataset/layers/network_security/DATASET_CARD.md
-
curl -L -o DATASET_CARD.md https://huggingface.co/datasets/ansulev/HolyCyber-Dataset/resolve/main/layers/network_security/DATASET_CARD.md
HolyCyber — Layer: network_security
A focused dataset for the network_security domain of the HolyCyber corpus, built on its own from that domain's authoritative sources only.
Overview
- Rows: 2,383
- Groups (leakage units): 643
- Entities in the domain: 643
- Splits: test=251, train=1,886, val=246
- Task types: 6 | Subdomains: 5
- Row size (tiktoken cl100k, user+assistant): min 2,069 / median 2,338 / mean 2,398 / p90 2,566 / max 5,026 tokens
- Entity's own material: median 19% of an answer's tokens; 1,494 rows are below 25% (the balance is the labelled reference appendix)
- Total tokens: 5,713,268 | Rows below the 2,000-token floor: 0
- Canary: every row carries the decontamination canary
Record format
One JSON object per line; messages is a three-turn chat (system / user / assistant).
{"id": "6d408e38f3cb8dff", "row_key": "<domain>:<group_key>:<task_type>:<subdomain>:<part>",
"domain": "network_security", "subdomain": "...",
"task_type": "...", "difficulty": "intermediate", "group_key": "...",
"source": "...", "license": "...", "split": "train", "canary": "...",
"tokens": {"user": 180, "assistant": 2350, "total": 2530},
"core_share": 0.41, "appendix": true,
"references": [{"title": "...", "url": "..."}],
"messages": [{"role": "system", "content": "..."},
{"role": "user", "content": "..."},
{"role": "assistant", "content": "## ...\n..."}]}
| Field | Meaning |
|---|---|
id |
content hash of user+assistant, stable across rebuilds of the same row |
row_key |
stable identity across rebuilds (domain:group:task:subdomain:part) |
domain / subdomain |
this layer, and the slice of it the row covers |
task_type |
the question shape (detection, mitigation, mapping, ...) |
difficulty |
derived from the task shape, not guessed |
group_key |
the source entity; the unit of the train/val/test split |
source / license |
the authoritative source, and its licence |
tokens |
measured cl100k_base counts for user, assistant and total |
core_share |
share of the answer that is the entity's own material (1 - appendix) |
appendix |
whether the row carries a ## Reference: appendix |
references |
resolvable links for the entities cited in the answer |
canary |
decontamination marker |
What a row contains
Topic sections used in this layer's answers (structural labels such as Answer or Context and the appendix are excluded):
| Section | Rows |
|---|---|
| Summary | 2,007 |
| Detection strategies and analytics | 901 |
| Tracked users (groups, malware, tools) | 803 |
| Mitigations | 681 |
| Background | 553 |
| Scope note | 534 |
| Classification | 533 |
| Relevant mitigations | 454 |
| Sub-techniques | 84 |
| Introduction | 57 |
| Introduction (continued) | 28 |
| Related Work | 22 |
How this layer is built
- Base cells — the rows the source parsers emit for this domain (one per entity x task type x subdomain).
- Task shapes — the same entity asked a different defensive question (detection, mitigation, framework mapping, response), built only from other sections of that entity's own record. No new facts are introduced.
- Reference pack — a row still under the token floor is padded with compact descriptions of other entities of this domain, taken from this domain's own source text; the window rotates per row.
Every row therefore comes from this domain's sources only, clears the 2,000-token floor, and no two rows are the same.
Task types
| Task type | Rows |
|---|---|
| knowledge_explanation | 910 |
| control_mapping | 533 |
| detection_engineering | 371 |
| threat_attribution | 338 |
| mitigation_remediation | 227 |
| definition | 4 |
Subdomains
| Subdomain | Rows |
|---|---|
| protocol_abuse | 714 |
| traffic_analysis | 692 |
| c2_analysis | 379 |
| intrusion_detection | 370 |
| segmentation | 228 |
Sources
| Source | Rows |
|---|---|
| mitre-attack | 2,007 |
| arxiv-corpus | 193 |
| ietf-rfc | 173 |
| nist-publication | 8 |
| research-corpus | 2 |
Quality controls
- Exact duplicates removed: 0
- Near-duplicates removed: 0 (MinHash-LSH, Jaccard >= 0.90, same task type only)
- Quality gate: 4 rejected ({'unresolved_markdown_link': 2, 'unbalanced_code_fence': 2})
- Contaminated rows removed: 0 ({})
- Split integrity: group-level by
group_key; no group crosses a split
Intended use
Supervised fine-tuning / evaluation of a defensive cybersecurity assistant specialised in this domain. All rows are defensive, detection or analysis oriented; none contains functional exploit code or weaponised prompts.
from datasets import load_dataset
ds = load_dataset("json", data_files=dict(train="network_security/train.jsonl", validation="network_security/val.jsonl", test="network_security/test.jsonl"))
# rows whose answer is mostly the entity itself, not the appendix
core = ds["train"].filter(lambda r: r["core_share"] >= 0.5)
Limitations
1,494 of 2,383 rows are more than 75% labelled reference appendix: this domain's own records are shorter than the 2,000-token floor, so the row is completed with other entities' records. Mask the appendix when fine-tuning if you only want the core answer.
Paragraph-level reuse is measured in
research/AUDIT_REPORT.md; rows are unique but their appendix material is shared.