PPL

Sigma to OpenSearch PPL

Paste a Sigma rule, get PPL for OpenSearch PPL.

  1. Paste the ruleYAML in
  2. Pick your SIEMOpenSearch PPL · PPL
  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
4 caveats
source = logs-endpoint.events.process-*
| where (`process.executable` like "%\\certutil.exe" or `process.pe.original_file_name` = "CertUtil.exe") and (`process.command_line` like "%-encode%" or `process.command_line` like "%/encode%")
2 lines · 234 B2/2 conditions

Notes — not part of the query

Target: OpenSearch PPL (PPL) — engine 1.0.1 — 2026-09-09

Profile: windows / process_creation → OpenSearch PPL

Coverage: 2/2 conditions

dropped: CASE_SEMANTICS — Narrowed to a case-SENSITIVE match: this target compares byte-exactly and the rule asked for insensitive, so a value whose case differs from the logged one will not match.

dropped: CASE_SEMANTICS — Narrowed to a case-SENSITIVE match: this target compares byte-exactly and the rule asked for insensitive, so a value whose case differs from the logged one will not match.

dropped: CASE_SEMANTICS — Narrowed to a case-SENSITIVE match: this target compares byte-exactly and the rule asked for insensitive, so a value whose case differs from the logged one will not match.

dropped: CASE_SEMANTICS — Narrowed to a case-SENSITIVE match: this target compares byte-exactly and the rule asked for insensitive, so a value whose case differs from the logged one will not match.

Setup (logs-endpoint.events.process-*): This query opens with 'source = logs-endpoint.events.process-*', the conventional index pattern for this log source. Point it at the pattern your deployment actually ships this data to — others in use are logs-windows.sysmon_operational-*, logs-system.security*, winlogbeat-*.

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

Verify against your own telemetry before deploying.

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 → OpenSearch PPL3 fields mapped · 4 constructs unsupportedClean

Every condition converted cleanly to OpenSearch PPL PPL.

Profile

Matched on product + category

Field map

Sigma fieldTarget fieldSource
CommandLineprocess.command_linegithub.com
Imageprocess.executablegithub.com
OriginalFileNameprocess.pe.original_file_namegithub.com

Unsupported constructs

  • DroppedCase sensitivity narrowed

    CASE_SEMANTICS

    opensearch_ppl has no insensitive spelling for this comparison in filter position; the query matches sensitively instead.

    Narrowed to a case-SENSITIVE match: this target compares byte-exactly and the rule asked for insensitive, so a value whose case differs from the logged one will not match.

  • DroppedCase sensitivity narrowed

    CASE_SEMANTICS

    opensearch_ppl has no insensitive spelling for this comparison in filter position; the query matches sensitively instead.

    Narrowed to a case-SENSITIVE match: this target compares byte-exactly and the rule asked for insensitive, so a value whose case differs from the logged one will not match.

  • DroppedCase sensitivity narrowed

    CASE_SEMANTICS

    opensearch_ppl has no insensitive spelling for this comparison in filter position; the query matches sensitively instead.

    Narrowed to a case-SENSITIVE match: this target compares byte-exactly and the rule asked for insensitive, so a value whose case differs from the logged one will not match.

  • DroppedCase sensitivity narrowed

    CASE_SEMANTICS

    opensearch_ppl has no insensitive spelling for this comparison in filter position; the query matches sensitively instead.

    Narrowed to a case-SENSITIVE match: this target compares byte-exactly and the rule asked for insensitive, so a value whose case differs from the logged one will not match.

Coverage

  1. selection_imgexpressed
  2. selection_cliexpressed

2 / 2 conditions expressed

Engine 1.0.12026-09-09Rule licensed NOASSERTION

Worked examples on OpenSearch PPL

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
    

    OpenSearch PPL · PPL

    source = logs-endpoint.events.process-*
    | where (`process.executable` like "%\\certutil.exe" or `process.pe.original_file_name` = "CertUtil.exe") and (`process.command_line` like "%-encode%" or `process.command_line` like "%/encode%")

    Every condition converted cleanly to OpenSearch PPL PPL. 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
    

    OpenSearch PPL · PPL

    source = logs-endpoint.events.process-*
    | where (`process.command_line` like "%.DownloadString(%" or `process.command_line` like "%.DownloadFile(%" or `process.command_line` like "%Invoke-WebRequest %" or `process.command_line` like "%Invoke-RestMethod %") and (`process.command_line` like "%| IEX%" or `process.command_line` like "%IEX (%" or `process.command_line` like "%Invoke-Expression%")

    Every condition converted cleanly to OpenSearch PPL PPL. 2/2 conditions

  3. Registry Import With A Suspicious Pathwindows / process_creationFailed

    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
    

    OpenSearch PPL · PPL

    Could not convert to OpenSearch PPL: opensearch_ppl cannot write 'regex' in expression position: no 'regex' spelling.

    Could not convert to OpenSearch PPL: opensearch_ppl cannot write 'regex' in expression position: no 'regex' spelling. 2/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
    

    OpenSearch PPL · PPL

    source = logs-endpoint.events.process-*
    | where `process.executable` like "%\\print.exe" and `process.command_line` like "print%" and `process.command_line` like "%/D%" and `process.command_line` like "%.exe%" and (not `process.command_line` like "%print.exe%")

    Every condition converted cleanly to OpenSearch PPL PPL. 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
    

    OpenSearch PPL · PPL

    source = logs-endpoint.events.process-*
    | where `process.executable` like "%\\schtasks.exe" and `process.command_line` like "%/create%" and (`process.command_line` like "%\\AppData\\Local\\Temp\\%" or `process.command_line` like "%\\Windows\\Temp\\%")

    Every condition converted cleanly to OpenSearch PPL PPL. 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
    

    OpenSearch PPL · PPL

    source = logs-endpoint.events.process-*
    | where `process.executable` like "%\\rundll32.exe" and `process.command_line` like "%comsvcs%" and `process.command_line` like "%MiniDump%"

    Every condition converted cleanly to OpenSearch PPL PPL. 2/2 conditions

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 PPL for OpenSearch PPL, the log-source profile it matched, the field map it applied, and anything OpenSearch PPL cannot express. Free, no sign-up.

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 OpenSearch PPL here.