Enhanced Endpoint Telemetry

New Log Search is available for Open Preview

We are rolling out a new Log Search experience to customers with an open preview starting January 31st, 2023. You can still use original Log Search during this open preview. Both the original and New Log Search will exist in parallel until development is complete. For now, review the topic on new Log Search and navigate to the Log Search Open Preview page in InsightIDR to become familiar with the new layout. Check back soon for fully updated documentation.

While InsightIDR provides out-of-the-box detection rules for suspicious and malicious events, the information captured by the Insight Agent contains rich metadata that is useful for accelerating alert investigations and facilitating complete incident response.

Available with InsightIDR's Advanced and Ultimate Packages

Enhanced Endpoint Telemetry (EET) is an Ultimate package feature, now widely available to InsightIDR Advanced customers with a limited EET data retention period of seven days. When you purchase the Ultimate package, you receive full access to the archive of process start data captured by the Insight Agent. For pricing and packaging information, visit InsightIDR's Packages and Subscriptions page.


To access EET data, you need:

  • A license for the Advanced or Ultimate packages, or access to the previously available EET add-on module. For pricing and packaging information, visit InsightIDR's Packages and Subscriptions page.
  • The latest version of the Insight Agent installed on your endpoints.

Data retention

By default EET data is available for 13 months. For details about log storage and retention in InsightIDR, view this solution brief.

For InsightIDR Advanced customers, EET data is only available for the previous 7 days.

Optimization and performance tuning

InsightIDR engineering teams utilize a variety of tuning measures to optimize for system performance and data storage limits. These measures may include removal of excessively noisy, irrelevant, or duplicated data that would otherwise clutter dashboards and log sets, as well as data compression to make the best use of your available storage space. When implementing these measures, InsightIDR engineering teams work closely with Rapid7 researchers and security experts to ensure we are collecting data that is the most effective for detecting and investigating malicious activity in your environment.

Query EET data with the Endpoint Activity log set

You can view all of your Endpoint Activity data in Log Search and run queries to analyze activity relevant to your organization.

  1. Navigate to Log Search.
  2. Select the Endpoint Activity log set to include all Endpoint Activity logs.
  3. Update the time range as needed.
  4. Create a query. To get started, you can check out these sample queries.

InsightIDR Endpoint Activity

Enable case insensitive and partial mapping for inclusive results

Select the Case insensitive and partial mapping checkbox before running a search to ensure differences in capitalization don't lead to missing query results.

Logs available in the Endpoint Activity log set

The Endpoint Activity log set contains three log types: Process Start, Netbios Poisoning, and Local Service Creation.

These Process Start log contains log events where a process starts on an endpoint. The Netbios Poisoning log contains log events where protocol poisoning is seen on an asset. The Local Service Creation log contains log events where any new services are installed on an asset, for example, PowerShell.

Save a query

Access the data you need faster by saving queries for future use. To save a query:

  1. Create a query and click the Save button to the right of the query bar.
  2. Name your query.
  3. Optionally, choose to include your Current Log Selection and Current Time Range.

InsightIDR Save a query

View saved queries

To view your saved queries, select the Queries dropdown to the left of the query bar.

InsightIDR View saved queries

Sample Queries

EET example queries can be used to search your Endpoint Activity log data.

Tips for querying your endpoint activity data:

  • Select the Case insensitive and partial mapping checkbox in Log Search.
  • Use Advanced mode.
  • Replace values in bold from the example queries with values from your logs.
  • Update the time range as needed.
Query process start data
These queries are designed to help you find useful information in your Process Start data.

Group by

There may be instances where you want to find data based on specific criteria. You can group your logs by domain, operating systems, file descriptions etc.

  • groupby(dns_domain)
  • groupby(os_type)
  • groupby(process.exe_file.description)
  • groupby(process.exe_file.product_name)

Find all unique assets with chosen software running

where(process.name="process.exe" OR parent_process.name="process.exe")groupby(hostname)calculate(unique:hostname)limit(1000)

Find software version

Parent Process


Child Process


Find hosts with psexec or psexecsvc running as either the parent or child process

  • where(process.name="psexec.exe" OR parent_process.name="psexec.exe")groupby(hostname)calculate(unique:hostname)limit(1000)
  • where(process.name="psexecsvc.exe" OR parent_process.name="psexecsvc.exe")groupby(hostname)calculate(unique:hostname)

Find ping process by hostname and command line

where(process.name="ping.exe")groupby(hostname, process.cmd_line)

Find Netstat processes by hostname and command line

where(process.name="netstat.exe")groupby(hostname, process.cmd_line)

Find unsigned Windows processes

where(process.exe_file.signing_status.status="UNISGNED") broupby(process.name, hostname) calculate(count)

Find processes that contain a specific word in their command line and/or by hostname

where(process.cmd_line icontains "your word")groupby(hostname, process.name)

Find RDP by hostname and command line

where(process.name="mstsc.exe")groupby(hostname, process.cmd_line)

Find Microsoft Management Console and its command line


Find MMC launching ADUC by endpoint and username

where(process.name="mmc.exe" AND process.cmd_line icontains "dsa.msc")groupby(hostname, parent_process.username)

Find Mimikatz by hostname and parent process command line

where("mimikatz", loose)groupby(hostname, parent_process.cmd_line)

Group by processes running on unique hosts


Find MSIExec installations

where(process.name="msiexec.exe" AND process.cmd_line icontains "/i")groupby(process.cmd_line)

Find MSIExec quiet installations

where(process.name="msiexec.exe" AND process.cmd_line icontains "/quiet")groupby(process.cmd_line)

Group by Linux process permissions and process name

where(os_type="LINUX")groupby(process.exe_file.permission, process.name)

Group by process reputation


Find all processes by name and by reputation

  • where(process.hash_reputation.reputation='Known')groupby(process.name)
  • where(process.hash_reputation.reputation='Unknown')groupby(process.name)
  • where(process.hash_reputation.reputation=’Malicious’)groupby(process.name)

Find processes by reliability


Group by overall process reliability


Find processes by reputational threat level


Find processes by name, hostname, and username

where(process.hash_reputation.reputation='process_reputation')groupby(process.name, hostname, process.username)

Find PUPs by process name and threat level

where(process.hash_reputation.classification.type='PUA')groupby(process.name, process.hash_reputation.threat_level)

Find PUPs by name, hostname, and username

where(process.hash_reputation.classification.type='PUA')groupby(process.name, hostname, process.username)

Find adware by process name


Group by process classification types


Find password documents

where(process.name=/(winword|excel|notepad|notepad++|textpad).exe/i AND process.cmd_line=/(.password.).(doc|txt|xls).*/i)groupby(process.cmd_line)

Group by all process threat levels


Find low threat level processes by name


Find processes by threat level


Find processes with well-known reputation

where(process.hash_reputation.reliability IN ['Very high', 'High'])groupby(process.name)

Find command lines showing the Taskkill.exe process


Find hostname and users using the PsLoggedon.exe utility

where(process.name="PsLoggedon.exe")groupby(hostname, process.username)

Note: This query shows connected users on the local machine and remote connections using local endpoint resources.

Find hostname and users running the native screencapture.exe software

where(process.name='ScreenCapture.exe')groupby(hostname, process.username)

Find processes, hostnames, and users running programs for SSH and/or Telnet

where(process.exe_file.description icontains-any ["ssh", "telnet"])groupby(process.name, hostname, process.username)

Find hostnames and users performing the <code>whoami</code> command line

where(process.name="whoami.exe")groupby(hostname, process.username)

Query process start data (Powershell)

These queries are designed to help you find useful information related to the PowerShell process.

Find Powershell processes

Parent Process


Child Process


Find Powershell process command lines that are not empty or are running a ps1 script

Parent Process

where(parent_process.name="powershell.exe" AND parent_process.cmd_line NOT IIN ["null", ".ps1"])groupby(parent_process.cmd_line)

Child Process

where(process.name="powershell.exe" AND process.cmd_line NOT IIN ["null", ".ps1"])groupby(process.cmd_line)

Find assets running powershell_ISE as either the parent or child process

where(process.name="powershell_ise.exe" OR parent_process.name="powershell_ise.exe")groupby(hostname)calculate(unique:hostname)

Query process start data (PSEXEC)

These queries are designed to help you find useful information related to the PSEXEC process.

Find all psexec command lines


Find psexec running the remote process in the system account

where(process.name="psexec.exe" AND process.cmd_line icontains ".s.")groupby(process.cmd_line)

Find remote assets that Psexec is running processes under the system account

where(process.name="psexec.exe" AND process.cmd_line icontains ".s." AND /psexec.exe (?P<remote_asset>[^ ]*)/)groupby(remote_asset)

Query historical user and asset data
When a suspicious event is detected on an endpoint, you can create a query to view all activity that occurred on the host prior to the event. You can use the queries in this section to display users and assets associated with a process start event.

Find unique assets associated with a process

where(hostname='hostname') groupby(process.cmd_line, process.exe_path) calculate(count)

Find unique assets and users associated with a process

where(hostname='hostname' and process.username=’username') groupby(process.cmd_line, process.exe_path) calculate(count)

Queries for Threat Hunting

These queries are designed to help you hunt for threats by analyzing endpoint user, process, and command line data.

Find commands being carried out by strings and stopping, all within the command line

where(process.name="cmd.exe" AND process.cmd_line ISTARTS-WITH "cmd.exe /C")groupby(process.cmd_line)

Find command line attempts to remove certain folder attributes

where(process.cmd_line icontains "attrib -h -s -r")

Find hosts and users that have launched a local endpoint's User Account Management

where(process.name IIN ["Netplwiz.exe", "lusmgr.msc"])groupby(hostname, process.username)

Find suspicious login activity

where(hostname="hostname" and process.username="username")

Find additional information about a process that triggered an alert

where(process.pid='process_id' and hostname='hostname', loose)

Find infrequently run commands

where(process.name='process_name' AND hostname='hostname') groupby(data.cmdLine) calculate(count) limit(limit)

Note: Before running the sample query, replace process_name and hostname with the name of the process and host you want to group by.

Find malicious hashes

where(process.exe_file.hashes.sha1="hash") groupby(hostname) calculate(count)

Find command lines where a setup.exe file is being launched from within the downloads folder

where(process.cmd_line icontains-all ["\downloads","setup.exe"])groupby(process.cmd_line)

Find commonly abused commands

Initial Investigation

where(process.cmd_line ISTARTS-WITH-ANY ["tasklist", "ver", "ipconfig", "systeminfo", "net time", "netstat", "whoami", "net start", "qprocess", "query"])groupby(hostname, process.cmd_line)


where(process.cmd_line ISTARTS-WITH-ANY ["dir", "net view", "ping", "net use", "type", "net user", "net localgroup", "net group", "net config", "net share"])groupby(hostname, process.cmd_line)

Spread of infection

where(process.cmd_line ISTARTS-WITH-ANY ["at", "reg", "wmic", "netsh advfirewall", "sc", "rundll32"])groupby(hostname, process.cmd_line)

Add process start event data to an investigation

All of your process start data is available for use in Investigations.

To add process start events to an investigation:

  1. Open the investigation you want to update.
  2. Select Explore Contextual Data > Search Logs. This will take you to Log Search.
  3. Select the Endpoint Activity log set.

InsightIDR Endpoint Activity

  1. Define your query. Refer to the examples above, or check out the Log Search documentation for guidance on writing queries.
  2. Select the checkboxes beside the log lines you want to add to the investigation, and click Send to Investigation.

InsightIDR Send to Investigation

  1. Add the applicable context to the log lines.
  2. Click Save. The log line will then appear in the Investigation timeline.

Enhanced Endpoint Telemetry Metadata

This section provides a detailed look at the endpoint activity data the Insight Agent sends to Log Search. You can create any number of queries to group and alert on this data. Note that the fields that appear in Log Search vary on your operating system.

Process Start Event

The following table provides information about the process start event metadata collected by the Insight Agent. Some fields vary based on Operating System. If "All" is listed in the Operating System column, the field will be sent to Log Search regardless of operating system.

FieldDescriptionOperating System
hostnameHostname of the endpoint running the processAll
dns_domainDomain of the endpoint running the processAll
os_typeEndpoint operating systemAll
r7_hostidRapid7 Host IDAll
processAll data related to the captured processAll
parent_processAll data related to the process that spawned the started processAll
env_varsThis object shows the environment variables when the process and its parent were launched. The parent value is listed only if it differs from the process value. The process value can be used to find processes that made changes to environment variables prior to launching a child process. If the env_vars of a process is null and the parent process includes environment variables, we will populate this with the parent’s environment variables.Windows
duplicated_eventsThis represents the count of identical events that occurred in a process. This is populated only if we see similar process events.Linux

Process Details

The Insight Agent collects and sends the following information about both the process triggering the event and the parent process. Some fields vary based on the Operating System the process or executible file is running on. If "All" is listed in the Operating System column, the field is sent to Log Search regardless of operating system.

FieldDescriptionOperating System
start_timeTime that this process startedAll
nameName of processAll
pidSystem Process IDAll
ppidParent system process IDMac/Linux, parent only
r7_idAgent-generated ID unique to a process startAll
exe_pathPath to the executableAll
img_pathPath to the executable. This may differ from exe_path if the executable is on a mounted remote file share. Only sent if it differs from exe_path.Windows
cmd_lineCommand line invocation used to start process, including argumentsAll
usernameLocal user who started the processAll
account_domainAD domain of the user who started the processWindows
uidUser IDMac/Linux
groupGroup nameMac/Linux
gidGroup IDMac/Linux
euid_nameEffective user nameMac/Linux
euidEffective user IDMac/Linux
egid_nameEffective group nameMac/Linux
egidEffective group IDMac/Linux
ruid_nameReal user nameMac
ruidReal user IDMac
rgid_nameReal group nameMac
rgidReal group IDMac
fsuidFile system user IDLinux
fsgidFile system group IDLinux
suidSaved user IDLinux
sgidSaved group IDLinux
sessionLogin session ID that launched the processAll
addrRemote address that the user is connecting fromMac
portPort the process usedMac
exe_fileInformation about the executable fileAll

Executable File

The following table outlines the metadata that the Insight Agent collects from the executable file.

FieldDescriptionOperating System
exe_file.ownerOwner of the executable fileAll
exe_file.uidID of the executable file ownerMac/Linux
exe_file.groupGroup of the executable fileMac/Linux
exe_file.gidGroup ID of the executable fileMac/Linux
exe_file.permissionsPermissions string of the executable fileMac/Linux
exe_file.orig_filenameThe original filename from the file metadataWindows
exe_file.descriptionThe description from the file metadataWindows
exe_file.product_nameProduct name of the executable as reported by the file metadataWindows
exe_file.authorCompany who produced the executable as reported by the file metadataWindows
exe_file.versionBuild version of the file from file metadataWindows
exe_file.createdExecutable file creation dateAll
exe_file.last_modifiedExecutable file last modification dateAll
exe_file.last_accessedExecutable file last accessed dateMac/Linux
exe_file.sizeExecutable file sizeAll
exe_file.internal_nameInternal name of the executable file from the metadataWindows
hashesCollection of different hashes of the processAll
signing_statusSignature statusWindows
signing_chainSignature chainWindows
countersigning_chainCountersignature chainWindows


The Insight Agent collects and sends the following process hash information:

FieldDescriptionOperating System
hashes.md5MD5 hashAll
hashes.sha256SHA256 hashAll
hashes.sha1SHA1 hashAll