Environment Variables in Policy Rules
Table of Contents
4.2 (EoS)
Expand all | Collapse all
-
- Set Up the Endpoint Infrastructure
- Activate Traps Licenses
-
- Endpoint Infrastructure Installation Considerations
- TLS/SSL Encryption for Traps Components
- Configure the MS-SQL Server Database
- Install the Endpoint Security Manager Server Software
- Install the Endpoint Security Manager Console Software
- Manage Proxy Communication with the Endpoint Security Manager
- Load Balance Traffic to ESM Servers
-
- Malware Protection Policy Best Practices
- Malware Protection Flow
- Manage Trusted Signers
-
- Remove an Endpoint from the Health Page
- Install an End-of-Life Traps Agent Version
-
-
- Traps Troubleshooting Resources
- Traps and Endpoint Security Manager Processes
- ESM Tech Support File
-
- Access Cytool
- View the Status of the Agent Using Cytool
- View Processes Currently Protected by Traps Using Cytool
- Manage Logging of Traps Components Using Cytool
- Restore a Quarantined File Using Cytool
- View Statistics for a Protected Process Using Cytool
- View Details About the Traps Local Analysis Module Using Cy...
- View Hash Details About a File Using Cytool
Environment Variables in Policy Rules
In addition to wildcards, policy rules also support
native environment variables, including user- and system-wide variables.
Restriction rules also support the use of multiple environment variables
as long as the environment variable does not expand to another environment
variable. You can use many environment variables that are supported
by the Windows OS but some environment variables, including this
specific set of variables, are not supported:
- %USERNAME% environment variable
- Environment variables that are private
- Recursive environment variables which include other environment variables in their definition (for example, %MySystemDrive% with a definition of %SystemDrive%)
The following topics describe supported environment variables
in Windows and examples of the target values.