skip to content

In a LOLBAS YAML entry, which fields tell a defender where the file lives, what privilege a command needs and how to detect it?

level: middleimportance: should knowfreq 14%

answer

  1. path rows and per-command rows
  2. free text, not a controlled list
  3. System32 and its 32-bit sibling
  4. a detection block with subfields
  5. most rows ask only for a user

basics

~10 s

Full_Path lists where the file commonly sits. Each command row carries Category, Privileges, MitreID and OperatingSystem. The Detection block holds IOC, Sigma, Elastic, Splunk, BlockRule and Analysis references.

solid answer

~30 s

An entry has `Name`, `Description`, optional `Aliases`, then a `Commands` list and `Full_Path`, `Code_Sample`, `Detection`, `Resources` and `Acknowledgement` blocks. For a defender, `Full_Path` gives the common locations to search an inventory, such as System32 and SysWOW64. Each command row has `Category`, `Privileges`, `MitreID` and `OperatingSystem`; the privileges value is free text, and a `User` value means the use does not need administrator rights. The `Detection` block holds `IOC`, `Sigma`, `Elastic`, `Splunk`, `BlockRule` and `Analysis` items. All of it is community-supplied, so read it as a lead to verify on your own hosts, not as a guarantee.

code

yaml · 15 lines
yaml
Name: Binary.exe
Description: Something general about the binary
Commands:
  - Command: <catalogued command line, not reproduced here>
    Category: Execute
    Privileges: User
    MitreID: T####
    OperatingSystem: Windows 10 1803
Full_Path:
  - Path: c:\windows\system32\bin.exe
  - Path: c:\windows\syswow64\bin.exe
Detection:
  - IOC: free-text indicator
  - Sigma: https://example.com/rule
  - BlockRule: https://example.com/block-rules

go deeper

for a junior

Name the entry blocks: Full_Path, the per-command fields Category, Privileges, MitreID and OperatingSystem, and the Detection block with its subfields.

for a middle

Explain what each field gives you and that Privileges and OperatingSystem are free text. Know that System32 and SysWOW64 both need searching, and that User means no administrator rights are needed.

for a senior

Show that you parse the data defensively: normalise free text, expect missing detection, and treat paths and versions as leads rather than guarantees.

for a principal

Describe the data pipeline you would build from the YAML source into inventory, review and detection work, including how you would handle schema drift and the date you last synced.

## The shape of an entry The repository's `YML-Template.yml` shows every field, and the project's notice explains them. One entry describes one file and has these top-level fields: - **`Name`** and **`Description`:** the file and a short sentence on its legitimate function. - **`Aliases`:** optional, for other builds of the same file. - **`Author`** and **`Created`:** who submitted the entry and when. - **`Commands`:** a list; each item has `Command`, `Description`, `Usecase`, `Category`, `Privileges`, `MitreID`, `OperatingSystem` and optional `Tags`. - **`Full_Path`:** a list of `Path` items, the places the file is commonly found. - **`Code_Sample`**, **`Detection`**, **`Resources`** and **`Acknowledgement`:** links, detection references, further reading and credits. This leaf never needs the `Command` text itself. The fields a defender reads are the ones around it. ## What each field gives a defender | Field | Where | What you take from it | |---|---|---| | `Full_Path` | entry | Where to look in an inventory. Common paths, not a complete list of locations. | | `Category` | command | The kind of function, which maps to the control that should answer it. | | `Privileges` | command | The rights the command needs, in free text. | | `MitreID` | command | The ATT&CK technique the use maps to, for reporting and detection coverage. | | `OperatingSystem` | command | The Windows versions the contributor observed. Free text such as a version number, not a fixed-in marker. | | `Detection` | entry | Indicators and rule links to start a detection from. | ## Reading the data honestly Counting the 248 entry files as read on 2026-10-04: 1. **Paths:** 774 `Path` items. 286 mention System32, 99 mention SysWOW64 (the 32-bit system folder on 64-bit Windows) and 284 sit under Program Files, which is where the separately installed Microsoft products live. An inventory therefore needs both system folders and the product folders. 2. **Privileges:** the field has no controlled vocabulary. Of 490 command rows, 426 say `User`; the rest use spellings such as `Administrator`, `Admin`, `SYSTEM` and `Local Admin`, plus a few one-off phrases. Normalise before counting, and note that most uses need no elevation. 3. **MitreID:** every one of the 490 command rows carries one. It names a technique, so one ID can cover several different commands. 4. **Detection:** 233 files carry the block and 232 have at least one item inside it, so 16 files have no detection reference at all. ## Traps - **Privileges: User is not low risk.** It only says the command needs no administrator rights. - **`OperatingSystem` is observation, not coverage.** A version missing from the list does not mean the behaviour is absent there. - **Fields are required in theory only.** CONTRIBUTING.md says every field is required, yet the template and notice differ in small ways (for instance, `BlockRule` appears in the template and in 24 entries but not in the notice's field list). Parse defensively. - **Do not paste a `Command` value into a rule or a ticket.** The defender's use of an entry is its path, category, privileges, technique and detection links. ## Using the fields in a pipeline 1. Parse the YAML with a tolerant parser and expand `Commands` into one row per command. 2. Normalise `Category` case and map `Privileges` free text into a small set such as standard user, administrator and SYSTEM. 3. Join `Full_Path` to your file inventory, adding the product folders for the OtherMSBinaries type. 4. Join `Detection` items to the rule repository you actually deploy from, and record which entries have none. 5. Store the date and the repository commit you synced. ## What the fields do not give you - **No severity.** Nothing in an entry ranks impact. - **No prevalence.** An entry does not say how common legitimate use is on your fleet. - **No fixed-in version.** `OperatingSystem` records what a contributor observed, not when the behaviour ended. - **No business need.** Whether your teams use the file is your data, not the catalogue's. - **No guarantee of freshness.** The `Created` date is when the entry was filed, and later changes to the file's behaviour may not be reflected.

  • A command row says Privileges: User. Does a program to remove local administrator rights close that use?
    No. The value says the command needs no administrator rights, so removing local admin does not remove it. As read on 2026-10-04, 426 of about 490 rows say User. Rights reduction is still worthwhile for the rows that need elevation, but the file's presence and use must be handled by block, constrain or monitor decisions.
  • Does an entry's Full_Path list every place that file exists on a host?
    No. The notice describes it as commonly located paths. Use it as the starting set for an inventory, add the product folders for the OtherMSBinaries type, and rely on file-hash or signature inventory where completeness matters.

  • Privileges is a controlled list that can be filtered exactly
  • A listed OperatingSystem version is the only one affected
  • Detection is present and trustworthy on every entry
  • A MitreID uniquely identifies one command line
  • Full_Path is a complete list of where the file exists
  • The Command field is what a defender copies into a rule