Fleet uses osquery tables to query operating system, hardware, and software data. Each table provides specific data for analysis and filtering.
wmi_cli_event_consumers
WMI CommandLineEventConsumer, which can be used for persistence on Windows. See https://www.blackhat.com/docs/us-15/materials/us-15-Graeber-Abusing-Windows-Management-Instrumentation-WMI-To-Build-A-Persistent%20Asynchronous-And-Fileless-Backdoor-wp.pdf for more details.
Column | Type | Description |
---|---|---|
class | text | The name of the class. |
command_line_template | text | Standard string template that specifies the process to be started. This property can be NULL, and the ExecutablePath property is used as the command line. |
executable_path | text | Module to execute. The string can specify the full path and file name of the module to execute, or it can specify a partial name. If a partial name is specified, the current drive and current directory are assumed. |
name | text | Unique name of a consumer. |
relative_path | text | Relative path to the class or instance. |
select filter,consumer,query,command_line_template,wcec.name from wmi_cli_event_consumers wcec left outer join wmi_filter_consumer_binding wcb on consumer = wcec.relative_path left outer join wmi_event_filters wef on wef.relative_path = wcb.filter;