Script Analysis
- Open a Windows profile, then click the 'Script Analysis' tab.
'Script Analysis' inspects what interpreters such as PowerShell, Windows Script Host and the command prompt are asked to run. The panel carries 'Edit' and 'Delete' buttons and has three sub-tabs.

General Settings
| Setting | Value seen |
| Perform Script Analysis (Recommended) | Enabled |
| Limit the total size of saved detected scripts to (KB): | 100 |
Runtime Detection
The sub-tab opens with the line 'Manage the list of applications for which you would like to perform script analysis before execution.'
| Button | Description |
| Add | Adds an interpreter to the list. |
| Edit | Changes the selected entry. |
| Remove | Takes the selected entry off the list. |
| Reset to Default | Puts the list back to the one the product ships with. |
| Column | Description |
| APPLICATION | The interpreter the row covers, given as a path pattern such as '*powershell.exe'. |
| HEURISTIC COMMAND-LINE ANALYSIS | An ON/OFF toggle. Inspects the command line the interpreter was given. |
| EMBEDDED CODE DETECTION | An ON/OFF toggle. Looks for code hidden inside what is being run. |
| EXCLUSIONS | An 'Exclusions' link, one per row, for things that interpreter may run unchecked. |
The list includes interpreters such as '*WScript.exe', '*cscript.exe', '*mshta.exe', '*cmd.exe', '*rundll32.exe', '*regsvr32.exe', '*powershell.exe', '*pwsh.exe', '*python.exe' and '*java.exe'.
Add an interpreter
'Add' is greyed out until you click 'Edit'. It opens the 'Add New Application' dialog. The 'Autoruns Scan' sub-tab has the same button and the same dialog, and keeps its own list.
| Field | Description |
| Application: | The interpreter to analyse, given as a path pattern such as '*powershell.exe'. |
- Click 'Policies' in the left navigation bar and open the profile.
- Click the 'Script Analysis' tab, then click 'Edit'.
- Click 'Runtime Detection' or 'Autoruns Scan'.
- Click 'Add' and give the path pattern under 'Application:'.
- Click 'OK', then set the two toggles on the new row and click 'Save'.
Add an exclusion for an interpreter
The 'Exclusions' link on a row opens the 'Manage Exclusions' dialog, which holds the things that interpreter may run without being analysed.
| Control | Description |
| (exclusion type) | A drop-down offering 'Path' or 'Regular Expression'. |
| Add | Adds a row of the chosen type to the list. |
- Click 'Policies' in the left navigation bar and open the profile.
- Click the 'Script Analysis' tab, then click 'Edit'.
- Click the 'Exclusions' link on the interpreter's row.
- Choose 'Path' or 'Regular Expression', click 'Add' and give the entry.
- Click 'OK', then click 'Save'.
Autoruns Scan
The sub-tab opens with the line 'Manage the list of applications for which you would like to perform script analysis to protect Windows services, autostart items and scheduled tasks.' It has the same four buttons and the same four columns as 'Runtime Detection', and lists the same interpreters.
Set up script analysis
- Click 'Policies' in the left navigation bar and open the profile.
- Click the 'Script Analysis' tab, then 'Edit'.
- On 'General Settings', turn on 'Perform Script Analysis (Recommended)' and set the size limit.
- On 'Runtime Detection', switch command-line analysis and embedded code detection on or off for each interpreter.
- On 'Autoruns Scan', do the same for services, autostart items and scheduled tasks.
- Click 'Save'.
Note: 'Reset to Default' replaces the whole list, including any interpreters you added and any toggles you changed.
