--- title: "Testing IPS event notifications" slug: "testing-ips-event-notifications" tags: ["Network Security (NX)", "Product Usage"] updated: 2026-10-02T10:24:25Z published: 2026-10-02T10:24:25Z canonical: "docs.trellix.com/testing-ips-event-notifications" --- > ## 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. # Testing IPS event notifications After you activate IPS processing on the platform and verify detection of IPS events, you should test the FireEye notifications for IPS alerts. You can test-fire IPS events from the Web UI or the CLI: - Testing IPS event notifications (Web UI) - Testing IPS event notifications (CLI) ##### Testing IPS event notifications (web UI) This topic describes how to use the Web UI to test IPS event notifications. ###### Prerequisites - Log in to the appliance Web UI as Operator or Admin. - Configure IPS event notifications, as described in [Initial configuration of IPS](/network-and-platform/docs/initial-configuration-of-ips). - Apply IPS policies to the appliance monitoring interfaces, as described in [Activating IPS processing](/network-and-platform/docs/activating-ips-processing). ###### Procedure To test IPS event notifications: 1. Choose **Settings > Notifications**. In the following example, all FireEye event notification methods are enabled, and IPS events are enabled for notification by email and rsyslog: ![scap_ips_settings_notifications-test.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a60321bb-cf89-38de-464a-ad4fc06d4f9e.png?sv=2026-02-06&spr=https&st=2026-11-20T04%3A53%3A22Z&se=2026-11-20T05%3A53%3A22Z&sr=c&sp=r&sig=GD7CEOBAewftrvll4zE3%2FIy%2BHIodJhivM2e4Cu%2FUoa0%3D) 2. In the drop-down list below the table, select **IPS Critical**. 3. Click **Test‑Fire**. The system generates an IPS event of severity level 8, which should trigger event notifications for all notification methods configured on the platform. 4. Choose **IPS > IPS Events**. Look for the test-fire IPS event near the top of the list. By default, the list displays the most recent events at the top. IPS test-fire events are listed with the rule name `IPS‑TEST‑FIRE: Malicious PDF Downloaded`. ### Note After you initiate an IPS test-fire event, the event appears in the IPS Events page for approximately 5 minutes before it disappears from the page display and from the events database. 5. Look for the test-fire IPS event in the other event notification targets you configured for IPS events. If a configured notification method fails, correct the notification settings, and then repeat the test. ##### Testing IPS event notifications (CLI) This topic describes how to use the CLI to test IPS event notifications. ###### Prerequisites - Log in to the appliance Web UI as Operator or Admin. - Configure IPS event notifications, as described in [Initial configuration of IPS](/network-and-platform/docs/initial-configuration-of-ips). - Apply IPS policies to the appliance monitoring interfaces, as described in [Activating IPS processing](/network-and-platform/docs/activating-ips-processing). ###### Procedure To test IPS event notifications: 1. Enable the CLI configuration mode. ```plaintext hostname > enable hostname # configure terminal ``` 2. Test your IPS event notification settings. ```plaintext hostname (config) # fenotify test‑fire ips-event ``` The platform generates an IPS event of severity level 8, which should trigger event notifications for all notification methods configured on the platform. 3. If a configured notification method fails, correct the configuration settings, and then repeat the test. 4. Save your changes. ```plaintext hostname (config) # write memory ``` :