--- title: "policymgr signature name <nameID>" slug: "policymgr-signature-name-nameid" tags: ["Reference", "CMS 11.x", "EX 11.x", "HX 10.x", "FX 11.x", "AX 11.x", "NX 11.x", "IVX 11.x", "Customer", "Network Security"] updated: 2026-08-04T17:23:18Z published: 2026-08-04T17:23:18Z canonical: "docs.trellix.com/policymgr-signature-name-nameid" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # policymgr signature name <nameID> Configures an alert policy exception for the alert rules that address aspects of the specified signature name. ### Syntax `policymgr signature name <nameID> interface {<portPair> | ALL | MGMT} src {<srcIP>/<prefix> | any} dst {<dstIP>/<prefix> | any} action <actionType>` ### Parameters `<nameID>` Configure an exception for the alert rules that address aspects of the specified signature name. `interface {<portPair> | ALL | MGMT}` Apply the exception to traffic through the specified appliance interface: - `<portPair>`—Traffic through the specified monitoring port pair. See the *Hardware Administration Guide* for your appliance. - `ALL`—Traffic through all monitoring port pairs. - `MGMT`—Traffic through the appliance management interface. `src {<srcIP>/<prefix> | any}` Apply the exception to traffic with the specified source. - `<srcIP>/<prefix>`—Traffic with the specified source IPv4 host or subnet, specified in CIDR format. Example: `10.128.45.154/32` - `<any>`—Traffic with any source IPv4 address. `dst {<dstIP>/<prefix> | any}` Apply the exception to traffic with the specified destination. - `<dstIP>/<prefix>`—Traffic with the specified destination IPv4 host or subnet, specified in CIDR format. Example: `172.217.27.36/32` - `<any>`—Traffic with any destination IPv4 address. `<actionType>` Take the specified action on matched traffic: **Block**, **UnBlock**, **Suppress**, **Suppress & Unblock**, or **Default**. For details, see "Alert Policy Exception Actions" in the Network Security User Guide. ### Example This example configures an alert policy exception for the alert rules that address aspects of the signature name Downloader.Locky. The exception applies to traffic through the appliance monitoring port pair A, with the 10.128.45.154/32 subnet source and the 172.217.27.36/32 subnet destination. For matched traffic, blocking is disabled. ``` hostname (config) # policymgr signature name Downloader.Locky interface A src 10.128.45.154/32 dst 172.217.27.36/32 action unblock ``` ### User role Operator or Admin ### Supported appliances This command is supported on the following appliances running the specified releases or later: - **Network Security:** Release 9.0.2