PowerQuery

Sigma to SentinelOne

Paste a Sigma rule, get a PowerQuery (S1QL 2.0) hunt for SentinelOne Event Search. Free, no sign-up.

  1. Paste the ruleYAML in
  2. Pick your SIEMSentinelOne · PowerQuery
  3. Read the reportQuery, field map, gaps
certutil
Tab indents · Shift+Tab outdents · Esc then Tab leaves the fieldValid Sigmaprocess_creation · windows29 lines · 968 B
Splunk logo An information technology company based in California, United States Splunk2
Microsoft3
Elastic3
CrowdStrike1
SentinelOne1
Palo Alto Networks1
Carbon BlackCarbon Black2
Google Security OperationsGoogle1
IBM1
Sumo Logic1
Rapid71
Graylog1
OpenSearch2
Grafana1
DFIR2
dataSource.name = 'SentinelOne' and event.type = 'Process Creation' and ((tgt.process.image.path matches '\\\\certutil\\.exe$' or tgt.process.image.originalFileName in:anycase ('CertUtil.exe')) and (tgt.process.cmdline contains ('-encode', '/encode')))
1 line · 252 B2/2 conditions

Notes — not part of the query

Target: SentinelOne (PowerQuery) — engine 1.0.1 — 2026-09-09

Profile: windows / process_creation → SentinelOne

Coverage: 2/2 conditions

huntrule.com — sigma 7c1e0a34-2b5f-4d18-9a63-0c8b1f4e5a71 — HuntRule Team — NOASSERTION

Verify against your own telemetry before deploying.

SentinelOne STAR custom-detection rule JSON

{
  "data": {
    "name": "Base64 Encoding Via Built-In Windows Utility",
    "description": "A sample rule for the huntrule.com converter. Detects a built-in utility being asked to\nbase64-encode a file, which is a common way to stage data before moving it off a host.\nThe flag is written out in both its dash and slash spellings, because the utility\naccepts either and a rule that names only one misses half the invocations.\n\n[huntrule] Generated from Sigma rule 7c1e0a34-2b5f-4d18-9a63-0c8b1f4e5a71 (\"Base64 Encoding Via Built-In Windows Utility\") by huntrule.com on 2026-09-09. Engine 1.0.1. mitre_tactics=[TA0009] mitre=[T1560.001] REVIEW BEFORE DEPLOYING.",
    "queryType": "events",
    "queryLang": "2.0",
    "severity": "Medium",
    "status": "Active",
    "expirationMode": "Permanent",
    "treatAsThreat": "UNDEFINED",
    "networkQuarantine": false,
    "s1ql": "dataSource.name = 'SentinelOne' and event.type = 'Process Creation' and ((tgt.process.image.path matches '\\\\certutil\\.exe$' or tgt.process.image.originalFileName in:anycase ('CertUtil.exe')) and (tgt.process.cmdline contains ('-encode', '/encode')))"
  },
  "filter": {
    "tenant": true
  }
}

New STAR rules land as Draft regardless of the requested status; enable via PUT /web/api/v2.1/cloud-detection/rules/enable and allow up to ~60 minutes of activation lag.

POST /web/api/v2.1/cloud-detection/rules17 lines · 1.2 KB

Verify this query against your own telemetry before deploying it — a converted rule is a starting point, not a tuned detection.

No account needed for this, and none for reading the library. Every rule shows the reporting behind it, the telemetry it needs and the ATT&CK technique it covers. Sign in to keep the ones you use.

Conversion reportwindows / process_creation → SentinelOne3 fields mappedClean

Every condition converted cleanly to SentinelOne PowerQuery.

Profile

Matched on product + category

Field map

Sigma fieldTarget fieldSource
CommandLinetgt.process.cmdlinegithub.com
Imagetgt.process.image.pathgithub.com
OriginalFileNametgt.process.image.originalFileNamegithub.com

Coverage

  1. selection_imgexpressed
  2. selection_cliexpressed

2 / 2 conditions expressed

Engine 1.0.12026-09-09Rule licensed NOASSERTION

Worked examples on SentinelOne

Real published rules run through the same engine as the tool above — including the ones it cannot take whole.

  1. Base64 Encoding Via Built-In Windows Utilitywindows / process_creationClean

    Sigma

    title: Base64 Encoding Via Built-In Windows Utility
    id: 7c1e0a34-2b5f-4d18-9a63-0c8b1f4e5a71
    status: experimental
    description: |
        A sample rule for the huntrule.com converter. Detects a built-in utility being asked to
        base64-encode a file, which is a common way to stage data before moving it off a host.
        The flag is written out in both its dash and slash spellings, because the utility
        accepts either and a rule that names only one misses half the invocations.
    author: HuntRule Team
    date: 2026-08-01
    tags:
        - attack.collection
        - attack.t1560.001
    logsource:
        category: process_creation
        product: windows
    detection:
        selection_img:
            - Image|endswith: '\certutil.exe'
            - OriginalFileName: 'CertUtil.exe'
        selection_cli:
            CommandLine|contains:
                - '-encode'
                - '/encode'
        condition: all of selection_*
    falsepositives:
        - Administrative scripts that legitimately encode files
    level: medium
    

    SentinelOne · PowerQuery

    dataSource.name = 'SentinelOne' and event.type = 'Process Creation' and ((tgt.process.image.path matches '\\\\certutil\\.exe$' or tgt.process.image.originalFileName in:anycase ('CertUtil.exe')) and (tgt.process.cmdline contains ('-encode', '/encode')))

    Every condition converted cleanly to SentinelOne PowerQuery. 2/2 conditions

  2. PowerShell Download Cradle On The Command Linewindows / process_creationClean

    Sigma

    title: PowerShell Download Cradle On The Command Line
    id: 1f9d4c02-6a77-4e5b-8c31-2d0af7b96e48
    status: experimental
    description: |
        A sample rule for the huntrule.com converter. Detects the download-and-run pattern where a
        remote payload is fetched and executed in one command. It exercises a value list under a
        single field, which every backend has to expand into its own OR form.
    author: HuntRule Team
    date: 2026-08-01
    tags:
        - attack.execution
        - attack.t1059.001
    logsource:
        category: process_creation
        product: windows
    detection:
        selection_fetch:
            CommandLine|contains:
                - '.DownloadString('
                - '.DownloadFile('
                - 'Invoke-WebRequest '
                - 'Invoke-RestMethod '
        selection_run:
            CommandLine|contains:
                - '| IEX'
                - 'IEX ('
                - 'Invoke-Expression'
        condition: all of selection_*
    falsepositives:
        - Installers and package managers that fetch and run their own payloads
    level: high
    

    SentinelOne · PowerQuery

    dataSource.name = 'SentinelOne' and event.type = 'Process Creation' and ((tgt.process.cmdline contains ('.DownloadString(', '.DownloadFile(', 'Invoke-WebRequest ', 'Invoke-RestMethod ')) and (tgt.process.cmdline contains ('| IEX', 'IEX (', 'Invoke-Expression')))

    Every condition converted cleanly to SentinelOne PowerQuery. 2/2 conditions

  3. Registry Import With A Suspicious Pathwindows / process_creationClean

    Sigma

    title: Registry Import With A Suspicious Path
    id: 5b3a8e91-4c26-4f70-b1d8-6e97c30a2f5d
    status: experimental
    description: |
        A sample rule for the huntrule.com converter. Detects a registry import whose argument does
        not look like an ordinary file path. It exercises a regular expression alongside a `not`
        filter, so the report has both a regex to check against the target's engine and a negated
        branch to place.
    author: HuntRule Team
    date: 2026-08-01
    tags:
        - attack.defense-evasion
        - attack.t1112
    logsource:
        category: process_creation
        product: windows
    detection:
        selection_img:
            - Image|endswith: '\regedit.exe'
            - OriginalFileName: 'REGEDIT.EXE'
        selection_cli:
            CommandLine|contains: '.reg'
            CommandLine|re: ':[^ \\]'
        filter_flags:
            CommandLine|contains|windash:
                - ' -e '
                - ' -a '
        condition: all of selection_* and not filter_flags
    falsepositives:
        - Scripted registry maintenance
    level: high
    

    SentinelOne · PowerQuery

    dataSource.name = 'SentinelOne' and event.type = 'Process Creation' and ((tgt.process.image.path matches '\\\\regedit\\.exe$' or tgt.process.image.originalFileName in:anycase ('REGEDIT.EXE')) and tgt.process.cmdline contains '.reg' and tgt.process.cmdline matches:matchcase ':[^ \\\\]' and (not (tgt.process.cmdline contains (' -e ', ' /e ', ' –e ', ' —e ', ' ―e ', ' -a ', ' /a ', ' –a ', ' —a ', ' ―a '))))

    Every condition converted cleanly to SentinelOne PowerQuery. 3/3 conditions

  4. File Copy Through The Print Utilitywindows / process_creationClean

    Sigma

    title: File Copy Through The Print Utility
    id: 3e6c17b8-9f40-4a2d-85e1-7b4d0c9a6f23
    status: experimental
    description: |
        A sample rule for the huntrule.com converter. Detects the print utility being used to copy an
        executable rather than to print. It exercises `startswith` together with `contains|all`, where
        several substrings must all appear in one field.
    author: HuntRule Team
    date: 2026-08-01
    tags:
        - attack.defense-evasion
        - attack.t1218
    logsource:
        category: process_creation
        product: windows
    detection:
        selection:
            Image|endswith: '\print.exe'
            CommandLine|startswith: 'print'
            CommandLine|contains|all:
                - '/D'
                - '.exe'
        filter_self:
            CommandLine|contains: 'print.exe'
        condition: selection and not filter_self
    falsepositives:
        - Printing a file whose name ends in .exe
    level: medium
    

    SentinelOne · PowerQuery

    dataSource.name = 'SentinelOne' and event.type = 'Process Creation' and (tgt.process.image.path matches '\\\\print\\.exe$' and tgt.process.cmdline matches '^print' and tgt.process.cmdline contains '/D' and tgt.process.cmdline contains '.exe' and (not (tgt.process.cmdline contains 'print.exe')))

    Every condition converted cleanly to SentinelOne PowerQuery. 2/2 conditions

  5. Scheduled Task Created From A Temp Pathwindows / process_creationClean

    Sigma

    title: Scheduled Task Created From A Temp Path
    id: 9d24a3ee-8a1b-4f26-b90f-4a71e2c85d17
    status: experimental
    description: |
        A sample rule for the huntrule.com converter. Detects schtasks.exe registering a task whose
        command line points into a temp directory, a common persistence shape. It exercises the
        bread-and-butter Sigma form — several selections ANDed by the condition — with no exotic
        modifiers, so it converts on every shipped target.
    author: HuntRule Team
    date: 2026-08-11
    tags:
        - attack.persistence
        - attack.t1053.005
    logsource:
        category: process_creation
        product: windows
    detection:
        selection_img:
            Image|endswith: '\schtasks.exe'
        selection_create:
            CommandLine|contains: '/create'
        selection_path:
            CommandLine|contains:
                - '\AppData\Local\Temp\'
                - '\Windows\Temp\'
        condition: all of selection_*
    falsepositives:
        - Installers registering update tasks from their extraction directory
    level: medium
    

    SentinelOne · PowerQuery

    dataSource.name = 'SentinelOne' and event.type = 'Process Creation' and (tgt.process.image.path matches '\\\\schtasks\\.exe$' and tgt.process.cmdline contains '/create' and (tgt.process.cmdline contains ('\\AppData\\Local\\Temp\\', '\\Windows\\Temp\\')))

    Every condition converted cleanly to SentinelOne PowerQuery. 3/3 conditions

  6. LSASS Memory Dump Via Comsvcswindows / process_creationClean

    Sigma

    title: LSASS Memory Dump Via Comsvcs
    id: 6a95c2d4-1e08-4f7b-9d52-8c41e7b30a96
    status: experimental
    description: |
        A sample rule for the huntrule.com converter. Detects the comsvcs.dll MiniDump export being
        invoked through rundll32 to dump process memory, a common LSASS credential-theft technique.
        It exercises `endswith` against the image path together with `contains|all` on one field.
    author: HuntRule Team
    date: 2026-08-10
    tags:
        - attack.credential-access
        - attack.t1003.001
    logsource:
        category: process_creation
        product: windows
    detection:
        selection_img:
            Image|endswith: '\rundll32.exe'
        selection_cli:
            CommandLine|contains|all:
                - 'comsvcs'
                - 'MiniDump'
        condition: all of selection_*
    falsepositives:
        - Administrators legitimately capturing a process dump with comsvcs
    level: high
    

    SentinelOne · PowerQuery

    dataSource.name = 'SentinelOne' and event.type = 'Process Creation' and (tgt.process.image.path matches '\\\\rundll32\\.exe$' and tgt.process.cmdline contains 'comsvcs' and tgt.process.cmdline contains 'MiniDump')

    Every condition converted cleanly to SentinelOne PowerQuery. 2/2 conditions

What to know about SentinelOne PowerQuery

This target emits PowerQuery — the S1QL 2.0 language that SentinelOne's Event Search, Deep Visibility Enhanced and the Singularity Data Lake query APIs all accept. It deliberately does not emit legacy S1QL 1.0: SentinelOne closed that dialect to new custom detection rules in February 2026 and removes it entirely in February 2027, and a 1.0 operator pasted into a 2.0 rule is stored and silently never fires. Every query is scoped to the native EDR source with dataSource.name = 'SentinelOne' plus the documented event.type for the rule's log source, so it does not scan third-party OCSF data where the EDR fields are simply null.

PowerQuery inverts two habits most query languages share, and both are handled here rather than left to bite. Equality and in are case-sensitive while contains and matches are case-insensitive, so Sigma's case-insensitive equality becomes in:anycase and a |cased comparison becomes =. And there is no startswith, endswith or value wildcard at all: those become anchored matches regular expressions with the literal properly escaped, never a contains with an asterisk in it — which matches a literal asterisk and nothing else.

Because a mistyped SentinelOne field never raises an error — it evaluates to null and the query quietly matches nothing — this is a strict target: every emitted field comes from SentinelOne's own published PowerQuery field reference, and a field that is not in it fails the conversion with the reason instead of shipping a query that looks healthy. Negations are always written not (…), because the reference documents that x not in (…) parses cleanly and returns zero rows.

SentinelOne PowerQuery reference →

How it works

  1. Step 1

    Paste the rule

    Drop a Sigma rule into the left pane, or open a .yml file. The tool says what it thinks you pasted before anything is sent.

  2. Step 2

    Pick your SIEM

    Choose the target dialect. Every shipped target is free and none of them are behind a sign-up.

  3. Step 3

    Read the report

    The query comes back with the log-source profile that was used, every field it renamed, and anything the target could not express.

  4. Step 4

    Verify, then deploy

    Run it against your own telemetry in audit mode before it alerts on anything.

Questions

Paste the Sigma rule into the tool on this page and press Convert. It returns PowerQuery for SentinelOne, the log-source profile it matched, the field map it applied, and anything SentinelOne cannot express. Free, no sign-up.

PowerQuery, which SentinelOne also calls S1QL 2.0 — the only language accepted for new custom detection rules since February 2026. Legacy S1QL 1.0 is deliberately not emitted: it is removed in February 2027, and a 1.0 operator inside a 2.0 rule is accepted by the API and then never matches anything.

Paste it into Event Search in the Singularity Operations Center or into Deep Visibility Enhanced in the Management Console; the same text is accepted by the Singularity Data Lake query APIs. It filters on dataSource.name = 'SentinelOne', so it reads the native EDR telemetry rather than third-party ingested logs.

PowerQuery has neither operator and no value wildcard — contains 'foo*' would search for a literal asterisk. The correct spelling is an anchored regular expression with the literal escaped, which is what the converter emits. Backslashes are doubled exactly as SentinelOne's own reference requires for matches values.

It will run if your field names match the profile shown in the report. Whether it matches the right events depends on your own telemetry, so verify it before deploying. The coverage figure tells you how much of the rule made it into the query.

The other pair

The same tool, with a different target preselected.

Every rule in the detection catalog is written in Sigma, so any of them converts to SentinelOne here.