# gnilrats602/sentinelone-queries architecture

> Architecture diagram of the GitHub repository gnilrats602/sentinelone-queries, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-05-15). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/gnilrats602/sentinelone-queries
- Repository: https://github.com/gnilrats602/sentinelone-queries

## Overview

1. **Repository purpose**
   - This is a **content repository** for SentinelOne Deep Visibility hunting queries, not an application or service.
   - Its main role is to act as a **structured catalog of detection logic** that can be consumed by other tools for ATT&CK mapping, query navigation, and hunting workflows.

2. **Primary artifact: YAML query documents**
   - The core unit is a `.yml` file describing one or more SentinelOne queries.
   - Each file is metadata-rich: title, description, author, operating system, query text, MITRE tactic/technique/subtechnique, tags, false positives, and references.
   - The schema is deliberately designed for **programmatic parsing** rather than manual-only reading.

3. **Directory-level organization by platform**
   - Queries are grouped by operating system under `queries/windows`, `queries/linux`, and `queries/apt`.
   - This creates the first architectural boundary: **platform-specific detection content** separated by target environment.
   - Consumers can filter the repository by OS before further classification or execution.

4. **Threat-model grouping**
   - The `queries/apt` folder holds campaigns and actor-oriented detections such as SolarWinds/SUNBURST-related content.
   - This is a second content boundary: **adversary/campaign-focused detections** alongside OS-centric techniques.
   - It complements the technique-centric Windows and Linux folders.

5. **MITRE ATT&CK alignment as a cross-cutting layer**
   - The README makes clear that the repository is meant to support **ATT&CK mapping**.
   - Tactic/technique/subtechnique fields provide a normalized taxonomy that external tooling can use to group, compare, and search detections.
   - This is the main semantic layer connecting otherwise independent query files.

6. **Query content and execution boundary**
   - The actual SentinelOne query syntax lives inside the `query` field of each YAML document.
   - The repository does not include an execution engine, scheduler, or API integration; it is **static source content**.
   - Any runtime interaction happens in downstream tools that read these files and submit queries to SentinelOne.

7. **Template-driven consistency**
   - `template.yml` serves as the canonical shape for new query entries.
   - This indicates a content-governance boundary: contributors should conform to a standard schema so downstream parsers remain stable.
   - The template likely reduces drift across files and supports automation.

8. **Data flow from authoring to consumption**
   - Content is authored or imported into YAML files, reviewed in the repo, and then consumed by other systems.
   - Typical downstream uses mentioned in the README are:
     - ATT&CK mapping
     - a query navigator
     - other hunting tools
   - The repository therefore functions as a **source-of-truth dataset** for query intelligence.

9. **Source lineage and curation state**
   - Many rules were converted from the older “SentinelOne ATTACK Queries” project.
   - The README notes that some descriptions, references, and false positives still need cleanup, so the repo contains both **curated** and **partially migrated** content.
   - This matters for diagramming because data quality is not uniform across all query files.

10. **External dependencies that shape the architecture**
   - The content is inspired by **SIGMA-style signatures** and uses **MITRE ATT&CK** as the classification model.
   - The detection language is SentinelOne Deep Visibility query syntax.
   - These external standards define the structure of the files and the expectations of the consuming tooling.

11. **What is not present**
   - There are no application services, databases, message queues, build pipelines, or deployment artifacts in the repository tree provided.
   - So the architecture diagram should emphasize a **documentation/content layer** rather than a system runtime.
   - The main components are repository structure, standardized YAML schema, and external consumers.

12. **How to draw it**
   - A good diagram would show:
     - the repo as a central **query content store**
     - folders as **platform/campaign partitions**
     - YAML files as **individual detection records**
     - downstream tools as consumers for **search, ATT&CK mapping, and query execution**
   - The most important boundary is between **static curated detection content** and **external systems that operationalize it**.

Main entry points: [`queries/windows`](https://github.com/gnilrats602/sentinelone-queries/tree/main/queries/windows) (Windows), [`README.md`](https://github.com/gnilrats602/sentinelone-queries/blob/main/README.md) (README), [`queries/linux`](https://github.com/gnilrats602/sentinelone-queries/tree/main/queries/linux) (Linux), [`queries/apt`](https://github.com/gnilrats602/sentinelone-queries/tree/main/queries/apt) (APT)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_content["Content store"]
  node_repo["Repo<br/>content catalog"]
  node_readme["README<br/>repo guide<br/>[README.md]"]
  node_template["Template<br/>yaml schema<br/>[template.yml]"]
  node_windows_dir[("Windows<br/>query partition")]
  node_linux_dir[("Linux<br/>query partition")]
  node_apt_dir[("APT<br/>campaign partition")]
  node_win_query1["PrintNightmare<br/>windows query<br/>[PrintNightmare.yml]"]
  node_win_query2["Kerberoasting<br/>windows query<br/>[kerberoasting.yml]"]
  node_win_query3["Sysmon Disable<br/>windows query<br/>[disable_sysmon.yml]"]
  node_linux_query1["Nix Sniffing<br/>linux query"]
  node_linux_query2["Firewall Off<br/>linux query"]
  node_apt_query1["Sunburst<br/>apt query"]
end

subgraph group_standards["External standards"]
  node_sentinelone{{"Deep Visibility<br/>query language"}}
  node_mitre{{"MITRE ATT&CK<br/>taxonomy"}}
  node_sigma{{"SIGMA style<br/>inspiration"}}
end

subgraph group_consumers["Downstream consumers"]
  node_attack_map["ATT&CK map<br/>analysis tool"]
  node_navigator["Query navigator<br/>browse tool"]
  node_hunt_tools["Hunting tools<br/>consumer tools"]
  node_sentinelone_exec["Query execution<br/>downstream runtime"]
end

node_repo -->|"documents"| node_readme
node_repo -->|"standardizes"| node_template
node_repo -->|"partitions"| node_windows_dir
node_repo -->|"partitions"| node_linux_dir
node_repo -->|"partitions"| node_apt_dir
node_windows_dir -->|"contains"| node_win_query1
node_windows_dir -->|"contains"| node_win_query2
node_windows_dir -->|"contains"| node_win_query3
node_linux_dir -->|"contains"| node_linux_query1
node_linux_dir -->|"contains"| node_linux_query2
node_apt_dir -->|"contains"| node_apt_query1
node_template -->|"shapes"| node_sentinelone
node_win_query1 -->|"annotated by"| node_mitre
node_win_query2 -->|"annotated by"| node_mitre
node_linux_query1 -->|"annotated by"| node_mitre
node_apt_query1 -->|"annotated by"| node_mitre
node_repo -.->|"inspired by"| node_sigma
node_readme -->|"enables"| node_attack_map
node_readme -->|"enables"| node_navigator
node_readme -->|"enables"| node_hunt_tools
node_hunt_tools -->|"submits"| node_sentinelone_exec
node_attack_map -->|"uses"| node_mitre
node_hunt_tools -->|"parses"| node_sentinelone
node_navigator -->|"filters"| node_windows_dir
node_navigator -->|"filters"| node_linux_dir
node_navigator -->|"filters"| node_apt_dir

click node_readme "https://github.com/gnilrats602/sentinelone-queries/blob/main/README.md"
click node_template "https://github.com/gnilrats602/sentinelone-queries/blob/main/template.yml"
click node_windows_dir "https://github.com/gnilrats602/sentinelone-queries/tree/main/queries/windows"
click node_linux_dir "https://github.com/gnilrats602/sentinelone-queries/tree/main/queries/linux"
click node_apt_dir "https://github.com/gnilrats602/sentinelone-queries/tree/main/queries/apt"
click node_win_query1 "https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/windows/PrintNightmare.yml"
click node_win_query2 "https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/windows/kerberoasting.yml"
click node_win_query3 "https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/windows/disable_sysmon.yml"
click node_linux_query1 "https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/linux/nix_network_sniffing.yml"
click node_linux_query2 "https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/linux/linux_firewall_disabled.yml"
click node_apt_query1 "https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/apt/sunburst_campaign.yml"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_repo,node_readme,node_template,node_windows_dir,node_linux_dir,node_apt_dir,node_win_query1,node_win_query2,node_win_query3,node_linux_query1,node_linux_query2,node_apt_query1 toneBlue
class node_sentinelone,node_mitre,node_sigma toneAmber
class node_attack_map,node_navigator,node_hunt_tools,node_sentinelone_exec toneMint
```

## Components

### Content store

Static detection content organized by platform and campaign.

- **Repo**: content catalog · Source-of-truth repository for SentinelOne Deep Visibility hunting queries.
- [README](https://github.com/gnilrats602/sentinelone-queries/blob/main/README.md): repo guide · Explains repository purpose, structure, and intended downstream uses. · `README.md`
- [Template](https://github.com/gnilrats602/sentinelone-queries/blob/main/template.yml): yaml schema · Canonical YAML shape for new query entries. · `template.yml`
- [Windows](https://github.com/gnilrats602/sentinelone-queries/tree/main/queries/windows): query partition · Technique-focused Windows detection content. · `queries/windows`
- [Linux](https://github.com/gnilrats602/sentinelone-queries/tree/main/queries/linux): query partition · Technique-focused Linux detection content. · `queries/linux`
- [APT](https://github.com/gnilrats602/sentinelone-queries/tree/main/queries/apt): campaign partition · Adversary- and campaign-oriented detections. · `queries/apt`
- [PrintNightmare](https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/windows/PrintNightmare.yml): windows query · Representative Windows hunting rule for a named technique or exploit pattern. · `queries/windows/PrintNightmare.yml`
- [Kerberoasting](https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/windows/kerberoasting.yml): windows query · Representative Windows credential-access hunting rule. · `queries/windows/kerberoasting.yml`
- [Sysmon Disable](https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/windows/disable_sysmon.yml): windows query · Representative Windows defense-evasion hunting rule. · `queries/windows/disable_sysmon.yml`
- [Nix Sniffing](https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/linux/nix_network_sniffing.yml): linux query · Representative Linux discovery or network-sniffing hunting rule. · `queries/linux/nix_network_sniffing.yml`
- [Firewall Off](https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/linux/linux_firewall_disabled.yml): linux query · Representative Linux defense-evasion or security-control tampering rule. · `queries/linux/linux_firewall_disabled.yml`
- [Sunburst](https://github.com/gnilrats602/sentinelone-queries/blob/main/queries/apt/sunburst_campaign.yml): apt query · Campaign-focused content for SolarWinds/SUNBURST-related activity. · `queries/apt/sunburst_campaign.yml`

### External standards

Schemas and taxonomies that shape the query documents.

- **Deep Visibility**: query language · SentinelOne query syntax embedded in each YAML record.
- **MITRE ATT&CK**: taxonomy · Cross-cutting tactic/technique/subtechnique classification layer.
- **SIGMA style**: inspiration · Signature-driven detection structure influencing the repository format.

### Downstream consumers

Tools and workflows that read the repository content.

- **ATT&CK map**: analysis tool · Downstream mapping workflow that groups and compares detections.
- **Query navigator**: browse tool · Downstream navigation and filtering workflow for hunting queries.
- **Hunting tools**: consumer tools · External tools that ingest YAML records for operational use.
- **Query execution**: downstream runtime · Operational submission of parsed queries to SentinelOne by external systems.

## Connections

- Repo → README: documents · Repository purpose and usage are explained here.
- Repo → Template: standardizes · Defines the canonical structure for new entries.
- Repo → Windows: partitions · Windows content is grouped separately.
- Repo → Linux: partitions · Linux content is grouped separately.
- Repo → APT: partitions · Campaign-oriented content is grouped separately.
- Windows → PrintNightmare: contains · Example query record within the Windows partition.
- Windows → Kerberoasting: contains · Example query record within the Windows partition.
- Windows → Sysmon Disable: contains · Example query record within the Windows partition.
- Linux → Nix Sniffing: contains · Example query record within the Linux partition.
- Linux → Firewall Off: contains · Example query record within the Linux partition.
- APT → Sunburst: contains · Example campaign-focused query record.
- Template → Deep Visibility: shapes · YAML records embed SentinelOne Deep Visibility query text.
- PrintNightmare → MITRE ATT&CK: annotated by · Queries carry ATT&CK tactic and technique metadata.
- Kerberoasting → MITRE ATT&CK: annotated by · Queries carry ATT&CK tactic and technique metadata.
- Nix Sniffing → MITRE ATT&CK: annotated by · Queries carry ATT&CK tactic and technique metadata.
- Sunburst → MITRE ATT&CK: annotated by · Campaign content is also ATT&CK-aligned.
- Repo → SIGMA style: inspired by · Repository structure follows signature-style detection conventions.
- README → ATT&CK map: enables · ATT&CK mapping is a stated downstream use.
- README → Query navigator: enables · Query navigation is a stated downstream use.
- README → Hunting tools: enables · Other hunting tools consume the catalog.
- Hunting tools → Query execution: submits · External tools operationalize queries against SentinelOne.
- ATT&CK map → MITRE ATT&CK: uses · Mapping workflow depends on ATT&CK taxonomy.
- Hunting tools → Deep Visibility: parses · Consumers read the embedded query syntax from YAML records.
- Query navigator → Windows: filters · Consumers can browse by platform partition.
- Query navigator → Linux: filters · Consumers can browse by platform partition.
- Query navigator → APT: filters · Consumers can browse by campaign partition.
