Script

Scripts are widely used to automate various tasks in a network, such as backing up data, updating system configurations, and managing network resources. However, if these scripts are not properly managed, they can become a potential source of vulnerability, allowing attackers to execute malicious code on your devices. To reduce the risk of such attacks, ensuring that both the interpreter and the script file are trustworthy is important.

To execute a script, you must trust the interpreter and the script file. The script interpreter is responsible for executing the script and will not open any file it does not trust.

Default Script

The Default Script tab consist the following fields:

PROPERTY	DESCRIPTION
	By toggling this switch, you can turn using the default trusted script. Enabled indicates that SecureAge Central will use the predefined trusted scripts.

Back to top

User-Defined Script

The User-Defined Script tab consist the following fields:

PROPERTY	DESCRIPTION
	Add a new script interpreter and its associated file extensions to the list. This can be used to introduce new scripts or validate in-house ones. Interpreter The executable that runs the script Extensions Their associated file extensions
	Delete User-Defined Script

Back to top

More information

• Adding a CatchPulse policy

• Adding global policy interval

• Editing a CatchPulse policy

• Assigning new CatchPulse groups to a policy

• Duplicating CatchPulse policy

• Deleting a CatchPulse policy

---

Support and feedback

Should you encounter any issues using the SecureAge Central with any of the mentioned or missed requirements above, you can always write to us a docs@secureage.com.

---

This page was last updated: September 03, 2024