Customize AgileSec Tanium actions to meet custom functionality requirements.
Overview
This guide covers creating a custom configuration file for AgileSec Tanium Discover and Run actions. After creating the configuration file, users should load the configuration files to the appropriate action package in their Tanium UI, then proceed through AgileSec Tanium: Execute Scans steps.
1. Configure Run Action
Perform the following actions to configure the AgileSec Tanium Run action:
-
Create configuration files
tanium_run_linux.ymlandtanium_run_windows.ymlwith the following templates:
-
Update lines 70+ (
values:) with custom configuration parameters. See the following tables for configuration guidance. -
Load the configuration file(s) to the Run package in Tanium UI.
-
When performing AgileSec Tanium: Execute Scans, ensure you update the Run action’s Config File parameter with the updated configuration file.
Note: The custom configuration .yml may be named differently as long as the correct name is passed into the Config File parameter when Executing.
Run Action Fields: UI or Configuration .yaml
Custom configuration will fully replace all parameters set in UI.
|
Run Action Field |
Description |
Recommended Default |
Custom Configuration Example |
|---|---|---|---|
|
Scan Path
|
Set the Directories or Drives to include in the analysis |
Windows: Linux: Note: using / for Linux or C:/ for Windows may be heavy and time-consuming as it scans the entire target machine. Adjust the path based on performance and scope requirements. |
Important: Windows paths may use either Example:
|
|
Host Scan Type
|
Select the type of scan to run:
Run-Incremental: Perform Incremental Scan since last scan and export results to AgileSec Server. After every 5 incremental scans, a complete scan executes.
Run-Full: Perform complete scan and export results to AgileSec Server.
Network: Only scan network interfaces and export results to AgileSec Server
Note:
|
Run-Full |
Run-Full
Run-Incremental:
Network:
|
|
Include Tanium
|
By default, Tanium directory is excluded from the scan process. To include Tanium in the scan process, comment out this line or remove |
Not Enabled (Exclude Tanium directory) |
Enable, excluding Tanium from scan:
Disable, including Tanium in scan (remove
|
|
Skip Mounts
|
Set to skip network mounts |
Enabled |
Uncomment Example:
|
|
Scan Priority
|
Set priority of the discovery process vs other processes:
|
Low |
Low:
Normal:
High:
|
|
CPU Priority
|
Set number of workers to parallelize the discovery process run:
|
Normal |
Low:
Normal:
High:
|
|
Log Level
|
Sets the log level for the log file to Warn, Info, or Debug. When scan runs, a log file is created in the installation directory on the execution machine. Log files can be examined if there is remote access to machine.
|
Warn |
|
Run Action Fields: Configuration .yaml Only
The following fields are only configurable via custom configuration file:
|
Run Action Field |
Description |
Recommended Default |
Custom Configuration Example |
|---|---|---|---|
|
Exclude Directory
|
Add directories to exclude from search. |
None |
Important: Windows paths may use either Example:
|
|
No Case
|
Determines if |
|
|
|
Enable Context
|
Enables incremental scanning. When set to |
False |
|
|
Scan Count
|
When Host Scan Type is Update Scan Count to change this default. For example, a value of 10 means we do 1 full scan, 9 incremental scans, then 1 full scan, 9 incremental scans, then 1 full scan, and repeat. |
N/A |
Setting scan cycle to 1 full scan, 9 incremental scans:
|
Run Action Fields: UI Only
The following fields can only be set via UI:
|
Run Action Field |
Description |
Recommended Configuration in UI |
|---|---|---|
|
Background Mode (Async Mode) |
When enabled, scan runs as an asynchronous background process. |
Enabled |
|
EDR Id |
An organization ID used by sensor to retrieve a token |
EDR Id obtained from AgileSec UI (Settings → EDR Management) |
|
Ingest URL |
Ingest URL of your AgileSec Server
|
|
|
Config File |
Add a custom configuration file |
Set to config file |
|
Ignore Missing Path |
Avoid fail if a given scan path is missing. For example, when targeting Windows systems, if When enabled, scan will still fail if all given scan paths do not exist. |
Enabled |
2. Configure Discover Action
Perform the following actions to configure the AgileSec Tanium Discover action:
-
Create configuration files
tanium_discover_linux.ymlandtanium_discover_windows.ymlwith the following templates:
-
Update lines 70+ (
values:) with custom configuration parameters. See the following tables for configuration guidance. -
Load the configuration file(s) to the Discover package in Tanium UI.
-
When performing AgileSec Tanium: Execute Scans, ensure you update the Discover action’s Config File parameter with the updated configuration file.
Note: The custom configuration .yml may be named differently as long as the correct name is passed into the Config File parameter when Executing.
Discover Action Fields: UI or Configuration .yaml
Custom configuration will fully replace all parameters set in UI.
|
Discover Action Field |
Description |
Recommended Default |
Custom Configuration Example |
|---|---|---|---|
|
Scan Path
|
Set the Directories or Drives to include in the analysis |
Windows: Linux: Note: using |
Important: Windows paths may use either Example:
|
|
Host Scan Type
|
Select the type of scan to run:
|
None |
Regular:
Full:
|
|
Network Scan Type
|
Select the network scan type: Host: Scan local processes on host to check if they allow SSH or TLS connections.
|
Host |
Perform network scan only:
Perform host scan and network scan:
|
|
Include Tanium
|
By default, Tanium directory is excluded from the scan process. To include Tanium in the scan process, comment out this line or remove |
Not Enabled (Exclude Tanium directory) |
Enable, excluding Tanium from scan:
Disable, including Tanium in scan (remove
|
|
Skip Mounts
|
Set to skip network mounts with a script on startup. |
Enabled |
Uncomment Example:
|
|
Scan Priority
|
Set priority of the discovery process vs other processes:
|
Low |
Low:
Normal:
High:
|
|
CPU Priority
|
Set number of workers to parallelize the discovery process run:
|
Normal |
Low:
Normal:
High:
|
|
Scan files modified since days
|
Limit scan to only new or modified files since x days ago. For example, if the last scan was 3 days ago, set the value to 3 to scan for new results. |
0 |
|
|
Log Level
|
Sets the log level for the log file to When scan runs, a log file is created in the installation directory on the execution machine. Log files can be examined if there is remote access to machine.
|
Warn |
|
Discover Action Fields: Configuration .yaml Only
The following fields are only configurable via custom configuration files:
|
Discover Action Field |
Description |
Recommended Default |
Custom Config Example |
|---|---|---|---|
|
Database
|
Must use the same directory as specified in the
|
If |
Default installation directory example:
|
|
Exclude Directory
|
Add directories to exclude from search. |
None |
Important: Windows paths may use either Example:
|
|
No Case
|
Determines if |
|
|
Discover Action Fields: UI Only
The following fields can only be set via UI:
|
Discover Action Field |
Description |
Recommended Configuration in UI |
|---|---|---|
|
Background Mode (Async Mode) |
When enabled, scan runs as an asynchronous background process. |
Enabled |
|
Config File |
Add a custom configuration file |
Set to config file |
|
Ignore Missing Path |
Avoid fail if a given scan path is missing. For example, when targeting Windows systems, if When enabled, scan will still fail if all given scan paths do not exist. |
Enabled |