This repository serves as a comprehensive collection of resources for monitoring, detecting, and analyzing Remote Monitoring and Management (RMM) tools across enterprise environments. While RMM tools are essential for legitimate IT administration, they are increasingly being leveraged by threat actors as part of "Living Off the Land" (LOL) techniques, making their detection and monitoring crucial for security teams.
Currently, the repository focuses on Splunk-based detection and monitoring capabilities, but it is actively expanding to include:
- Multi-SIEM detection rules and dashboards
- API integration scripts for RMM platforms
- Detection engineering guidance
- Threat hunting playbooks
- Incident response procedures
Note
All data is compiled and curated from: https://lolrmm.io
Important
This project aims to become a central hub for security practitioners dealing with RMM tool detection and analysis across different platforms and tools.
- Dashboard: Interactive visualization of RMM tool usage across your network
- Scheduled Search: Creates and maintains a lookup table of RMM detections
- Multiple Data Source Options: Flexibility to use Splunk Enterprise Security, PaloAlto firewalls, or custom data sources
├── splunk/
│ ├── dashboards/
│ │ └── lolrmm_network_dashoard.xml # Main Splunk RMM monitoring dashboard
│ ├── searches/
│ │ ├── es-lolrmm_dns_cim_search.spl # Splunk ES-compatible DNS monitoring
│ │ ├── es-lolrmm_network_report.spl # Splunk ES network traffic analysis (powers KV Store)
│ │ ├── es-lolrrm_dns_search.spl # Splunk ES DNS detection search
│ │ └── non-es-lolrrm_dns_search.spl # Standard Splunk DNS detection
│ └── demo.csv # Sample Splunk data for testing
├── crowdstrike/
│ ├── RMM-Artifacts.csv # CrowdStrike Lookup: RMM process/file artifacts
│ ├── RMM_Domain_Artifacts.csv # CrowdStrike Lookup: RMM domain/network artifacts
│ └── RemoteManagementActivity.yaml # CrowdStrike Dashboard template
This repository provides search and dashboard options for both Splunk Enterprise Security (ES) customers and non-ES Splunk customers.
Important
Search files are prefixed with either es- or non-es- to clearly indicate which environment they are designed for.
This section details instructions for Splunk Enterprise or Splunk Cloud, with options for both Enterprise Security (ES) customers and non-ES customers.
Important
Splunk search files are prefixed with either es- or non-es- to clearly indicate which environment they are designed for.
ES customers can leverage the data model accelerations and additional context provided by Splunk Enterprise Security:
- Use the searches prefixed with
es-which utilize the Network_Traffic data model - The dashboard automatically detects if you're using ES and enables appropriate features
- ES-specific correlation searches can be scheduled to trigger notable events
If you don't have Splunk Enterprise Security, you can still use these resources:
- Use the searches prefixed with
non-es-which are designed to work with standard Splunk indexes - Configure the dashboard to use PaloAlto or raw network data sources
- Create scheduled searches to populate the lookup tables needed by the dashboard
Choose one of the following setup options for the Splunk dashboard:
Tip
This approach is ideal for large enterprises as it reduces query load during dashboard viewing, provides consistent historical data, and enables faster dashboard loading times.
- Install the search
lolrm_network_report.splas a scheduled search - Configure the search to run at your preferred interval (e.g., daily)
- The search will output results to a KV store lookup table named
lolrmm.csv - Import the dashboard XML and select "LOLRMM Network Report" as the data source
- Import the dashboard XML
- Select "PaloAlto Index" as the data source
- Ensure your PaloAlto logs are being ingested with the sourcetype
pan:traffic
- Import the dashboard XML
- Select "Splunk ES" as the data source
- Ensure your Network_Traffic data model is properly populated
Important
Custom macros detect_remote_access_software_usage_traffic_filter and remote_access_software_usage_exceptions must be configured for proper dashboard functionality.
Important
For the Splunk dashboard, custom macros detect_remote_access_software_usage_traffic_filter and remote_access_software_usage_exceptions must be configured for proper functionality, especially for filtering legitimate RMM tools specific to your environment.
- Timeline View: Visualize RMM tool usage over time
- Application Distribution: See which RMM tools are most prevalent
- Geographic Map: View global distribution of RMM connections
- Source Analysis: Identify hosts using RMM tools
- Filtering Options: Drill down by tool type, category, time range, and more
- Identify unauthorized RMM tool usage
- Monitor legitimate RMM tool activity
- Detect potential lateral movement or command and control activity
- Validate security policies around remote access tools
- Splunk Enterprise or Splunk Cloud
- For ES option: Network_Traffic data model
- For PaloAlto option: PaloAlto firewall logs with sourcetype
pan:traffic
This section details instructions for utilizing the CrowdStrike Falcon platform resources.
-
Upload Lookup Files:
- Navigate to
Next-Gen SIEM -> Log management -> Lookup filesin your Falcon console. - Upload
crowdstrike/RMM-Artifacts.csv. - Upload
crowdstrike/RMM_Domain_Artifacts.csv.
- Navigate to
-
Import Dashboard:
- Navigate to
Next-Gen SIEM -> Log management -> Dashboards. - Click
Create dashboardand selectImport. - Upload the dashboard template file
crowdstrike/RemoteManagementActivity.yaml
- Navigate to
-
Configure Dashboard Application Filter:
- Once imported, open the newly created dashboard.
- Click
Edit(usually in the top right). - Locate the "Application Filter" parameter/input (top left).
- Replace the default value with a pipe-separated (
|) list of your approved RMM tools (e.g.,ApprovedTool1|ApprovedTool2|ApprovedTool3). This helps filter out known legitimate activity from the main views. Note: Remote Desktop related terms will be filtered by default, review the dashboard query if needed. - Save the dashboard changes.
- CrowdStrike Falcon Platform.
- Access to Next-Gen SIEM / LogScale module.
- Permissions to upload Lookup files and create/edit Dashboards.
Warning
RMM tools are frequently used in legitimate IT operations. Always investigate and verify findings before taking blocking or remediation actions to avoid disrupting critical business operations. Context is key.
Caution
These dashboards and searches identify network traffic, process executions, or other artifacts associated with RMM tools based on known indicators. They do not automatically distinguish between legitimate and malicious usage without proper tuning (like filtering approved tools) and investigation.
