Use Smart Client scripts safely
Smart Client scripts (.scs files) automate actions and run with the permission of the logged-in VMS user. To maintain system security, follow these hardening baselines.
Manage credentials securely
For maximum security, never store plain-text passwords in script files.
Recommended: Use Windows Default authentication (<Login AuthenticationType="WindowsDefault" ... />). For unattended computers, such as video walls or kiosks, pair this with a dedicated, restricted Windows user account.
Alternative login: If using basic or other Windows authentication, you increase security by omitting the Password attribute from the
<Login>block, prompting the operator to enter their credentials at startup. If the operator selects Remember Password, the next run of the script will use the remembered password and log in automatically.
Keep the legacy script engine disabled
For maximum security, it is recommended that you leave the legacy script engine disabled so scripts cannot bypass validation:
In
Client.exe.config, ensure thatStartupScript_AllowRuntimeCompilationis not set to true. If it's left out or empty, it defaults to false.Restrict write access to
Client.exe.configto local administrators and verify this setting again after upgrading XProtect Smart Client.
Restrict folder and file permissions
Script files are plain text files, and it is recommended you protect them from unauthorized changes:
Store approved scripts in a protected directory.
Configure Windows folder permissions so that only Administrators and SYSTEM have full control, and Operators have read and execute permissions only.