Configure collection ↗
On the configuration page, select the relevant categories and artifacts for collection.
Configuration for collection
Note
When search fields are specified, the search is limited based on those filters. If more than one entry is in a search filter field, the search returns entries that match any of them. For example: A File Search with two specified paths ("C:\Test\" and "C:\Windows\") will return results from both the Test and Windows folders.
If you specify multiple search fields, the search returns entries that match all the selected criteria. For example: A File Search with one path ("C:\Test") and one size filter (">= 100MB") will return results from the Test folder that are greater than or equal to 100 megabytes.
Not all artifacts within an artifact category support the same search fields. If an artifact does not support one of the specified fields, then that filter is not applied to the search results. For example, in Windows, a Process Execution search with the search field User Name="jsmith" will filter the CidSizeMRU, LastVisitedPidlMRU, and UserAssist artifacts for that user name. That user name will not filter results from the Amcache, Prefetch, and Shimcache artifacts because those artifacts do not have a User Name field.
You can create a search query by adding any of the following artifacts available for both triage and hunt collections:
| Category from Hunt Collection | Default Timeout | Data collected during a Triage Collection is categorized into Artifacts, Volatiles, and File Collection | Supported Filters |
|---|---|---|---|
| Archive History (Windows only) | 60 minutes |
|
|
| Browser History | 60 minutes |
|
|
| Command History | 60 minutes |
|
|
| Deleted Files (Windows only) | 180 minutes |
|
|
| File Access | 60 minutes |
|
|
| File Search | 180 minutes |
|
|
| Log Search | 180 minutes |
|
|
| Network Data | 60 minutes |
|
|
| Persistence | 60 minutes |
|
|
| Process Execution | 60 minutes |
|
|
| Registry Search (Windows only) | 180 minutes |
|
|
| Remote Access (Windows only) | 60 minutes |
|
|
| System Statistics (Windows only) | 60 - 120 minutes |
|
|
| User Searches | 60 minutes |
|
|
Linux Artifacts Table
| Category | Schedule | Artifact & Description | Parameters / Options |
|---|---|---|---|
| Core Linux | 60 minutes | Authorized Keys: Contains public keys that are permitted to log in as a specific user via SSH. Attackers can add their own keys to this file to gain persistent access to a system. | <p>Comment: regular expression (case-sensitive) Example: tancref.*</p> |
Known Hosts: The known_hosts file stores the public keys of SSH servers that a user has connected to. This helps to verify the server's identity and prevent man-in-the-middle attacks by alerting the user if the server's key changes. |
<p>Host: IP or hostname (regular expression) Example: 41.21.21., .google.com</p> |
||
| System Information: Provides fundamental hardware and system information, including manufacturer, model, UUID, and memory details. This helps identify and profile the system. | <p>File Name: regular expression (case-sensitive) Example: [0-9A-F]{8}</p> |
||
| Systemd Journal: | None required | ||
| Running Processes: A detailed snapshot of running processes on the system. This includes process identifiers, user context, executable path, parent-child relationships, state, and performance metrics. It is a cornerstone artifact for live system analysis. | <p>• File Name: regular expression (case-sensitive) Example: [0-9A-F]{8}• Process Owner: Entries are either numeric UIDs or text usernames. Example: 1001• Path: file path Example: /usr/local/share//bin/</p> |
||
| Network Connections: Lists active network connections and listening ports. Essential for identifying unauthorized network communications, malware command and control (C2) channels, or unexpected listening services. | <p>• Local IP: IPv4 or IPv6 addresses Example: 10.0.0.5• Local Port • Local IP • Remote IP • Remote Port • Netstat Command Line • Netstat Process Name • Netstat Process Path</p> |
||
| <p>Firewall Rules: Firewall rules (for example, from iptables) that control network traffic. Analyzing these rules is important for understanding the network security posture and identifying potentially malicious or overly permissive configurations. NOTE: Supported only for the UFW tool (Firewall management tool for some Linux distributions such as Ubuntu)</p> |
<p>• Source: regular expression (case-insensitive) Example: [0-9A-F]{8}.exe• Destination: regular expression (case-insensitive) Example: [0-9A-F]{8}.exe</p> |
||
| Kernel Modules: Lists kernel modules on the system, their state, and the associated file path. Malicious actors may use custom kernel modules (rootkits) to hide their presence or gain privileged access. | <p>• Module Name: regular expression (case-insensitive) • Module Path: path</p> |
||
| Environment Variables: Lists environment variables for a given context (for example, a user's shell or a specific process). These variables define the execution environment and can contain important paths, configurations, or sensitive data. | <p>• Key: regular expression (case-sensitive) • Value: regular expression (case-sensitive)</p> |
||
| Mounted Filesystems: Lists all mounted file systems, their sources (devices), types, and unique identifiers. This is useful for discovering connected storage, network shares, and understanding the file system layout. | None required | ||
| User Login & Session History: Records of user login sessions from the last command, showing who logged in, from where, and for how long. This is essential for auditing user access and investigating unauthorized logins. | User Login | ||
Command History: Detailed records of commands from user shell history files (for example, .bash_history, .zsh_history). This artifact is essential for tracking user activity and command execution. |
<p>• Command: • Executed by: Entries are either numeric UIDs or text usernames. Example: 1001</p> |
||
| Auditd Rules: Refers to the log data collected by the Linux Audit Daemon, which is a core component of security auditing. It records a detailed, chronological trail of system events based on a set of pre-configured rules. | <p>• Command: • Executed by: Entries are either numeric UIDs or text usernames. Example: 1001• Auditd List:</p> |
||
System-Wide Configuration: Key-value pairs parsed from various configuration files within the /etc directory, such as /etc/resolv.conf for DNS settings. This artifact helps understand the system's network and operational configuration. |
<p>Source: regular expression (case-insensitive) Example: [0-9A-F]{8}.exe</p> |
||
| File Listing: A plain text file used in digital forensics to create a detailed timeline of a file system activity. | <p>• File Name: regular expression (case-sensitive) Example: [0-9A-F]{8}• User Id: Entries are either numeric UIDs or text usernames. Example: 100001• Group Id: Entries are either numeric GIDs or text group names. Example: 0, 1</p> |
||
| Files & Processes: The artifact lists the files opened by the processes. This listing is essential for mapping a process directly to the files, loaded libraries, and network sockets it's using, which can immediately reveal hidden activities or active connections. | <p>• File Name: regular expression (case-sensitive) Example: [0-9A-F]{8}• User Id: Entries are either numeric UIDs or text usernames. Example: 100001</p> |
||
System Configuration Files: Shell profile files (for example, .bashrc, .profile) that contain commands and configurations executed at session startup. They are analyzed for persistence mechanisms, aliases, and malicious environment modifications. |
None required | ||
| Service Status: Lists system daemons or services (for example, from systemd). Analyzing these is key to understanding which long-running processes are configured on the system and to spot malicious or unnecessary services. | <p>• File Name: regular expression (case-sensitive) Example: [0-9A-F]{8}• Path: file path Example: /usr/local/share//bin/• Command:</p> |