Custom Command Line Script
How To Configure
Enabling Custom Command Line Script may introduce potential security risks. It is recommended that only experienced administrators enable and manage this setting, taking full responsibility to implement appropriate security measures and monitor for any vulnerabilities.
Post-processing scripts can be configured via the Run custom command line script option.
Variables from the table below can be used in the scripts.
One command can only be configured for the script. For multiple commands, a batch or powershell script should be created and then called from the command line script.
For example, the following command line will call a batch script that will copy the file that was analyzed by Kiosk to E:\MD_POST_ACTION_BY_PAC folder and delete after the copy.
echo offset file=%1copy /y %file% E:\MD_POST_ACTION_BY_PACdel /q %file%
After entering your script, click Apply.
Be sure to test the script before configuring with Kiosk as the script is not validated.
Paths or parameters (excluding Pre-defined variables for scripts) containing blanks should be surrounded in "quotes".
Pre-defined variables for scripts
| Variable | Description | Notes |
|---|---|---|
| %%%file_path%%% | The absolute path of the file scanned | |
| %%%threat_name%%% | The name of the threat found by the engines | This variable only applies to infected scan results (scan_all_result_i = 1) |
| %%%scan_finished%%% | The time when the scan was finished | Local time of the kiosk system |
| %%%ticket_id%%% | A random number assigned to each Kiosk session | |
| %%%scan_results%%% | Integer representation of the scan result | |
| %%%process_result%%% | The process outcome
|
Running a Powershell script
To execute a Powershell script, the corresponding group policy needs to be set.
See About Execution Policies under USE GROUP POLICY TO MANAGE EXECUTION POLICY.
Enable Turn on Script Execution -> select Allow all scripts