Configure interpreters

Map an interpreter with a file or script extension:

sadmin scripts add extension interpreter1 [interpreter2]...

sadmin scripts add .vbs wscript.exe cscript.exe

This command enables Application Control to enforce that wscript.exe and cscript.exe can execute a .vbs script (when the script file and interpreters are allow listed). After the association is defined, wscript.exe and cscript.exe can also execute other script files (provided the interpreter can read and understand the instructions in the script file). The association is effective immediately and applies to all new interpreter instances initiated after running this command.

If needed, you can associate additional interpreters with a script or file type. For example:

sadmin scripts add .vbs zscript.exe

If you try to add an interpreter that is already associated with a file or extension type, no action is taken.

Note

Application Control supports a special tag 16 Bits as a synthetic extension for the 16-bit binaries. To control execution for the 16-bit binaries, execute these commands.

• sadmin scripts add 16Bit wowexec.exe

• sadmin scripts add 16Bit ntvdm.exe

View interpreter and file extension associations

sadmin scripts list

Sample output appears like this:

.ps1     "powershell.exe"
.bat     "cmd.exe"
.cmd     "cmd.exe"
.pif     "ntvdm.exe"
.sys     "ntvdm.exe"
.vbe     "cscript.exe" "wscript.exe"
16Bit    "ntvdm.exe" "wowexec.exe"
.vbs     "cscript.exe" "wscript.exe"
.exe     "ntvdm.exe"

Remove interpreter and file extension associations.