--- title: "Configure Sensor alert logging for threat feeds as per IoC types" slug: "configure-sensor-alert-logging-for-threat-feeds-as-per-ioc-types-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:29:31Z published: 2026-11-19T12:29:31Z canonical: "docs.trellix.com/configure-sensor-alert-logging-for-threat-feeds-as-per-ioc-types-2" --- > ## 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. # Configure Sensor alert logging for threat feeds as per IoC types Alert detection and logging by Sensors for configured threat feeds differs by the imported IoC types that you want to use for threat detection and response. | IoC types | Actions to be taken for alert logging | | --- | --- | | **IPv4 Endpoint**, **IPv6 Endpoint**, **IPv4 CIDR**, **IPv6 CIDR** | 1. Navigate to the **Devices** → **** → **Devices** → **** → **Setup** → **Logging** → **Firewall Access Logging** page. 2. If you have already configured the syslog server for firewall rules logging at the Sensor level, you can use the same server for detection and logging of these IoC types. For more information, see [Enable syslog forwarding for Firewall at Sensor level](/network-and-platform/docs/enable-syslog-forwarding-for-firewall-at-sensor-level-2). 3. If you do not have a target syslog server configured for firewall rules logging - > [!NOTE] > Note > > In scenarios where the same IPv4/IPv6 endpoint or CIDR is configured in both a firewall policy (ACL) and as an active IoC in a threat intelligence feed, the IoC block action takes precedence over the Firewall Policy (ACL) block action. The prioritization of IoC block action is applicable even if the firewall policy was configured first. 1. Navigate to **Manager** → **** → **Setup** → **Notification** → **Firewall Access Events** page. 2. Configure a syslog server which the Sensors will be using to send IoC logging details. For more information, see [Enable rule match notification](/network-and-platform/docs/enable-rule-match-notification-2). 3. Go to the **Devices** → **** → **Devices** → **** → **Setup** → **Logging** → **Firewall Access Logging** page and select the configured server enable syslog forwarding for the required Sensors. For more information, see[Enable syslog forwarding for Firewall at Sensor level](/network-and-platform/docs/enable-syslog-forwarding-for-firewall-at-sensor-level-2). | | **Domains**, **URLs** | 1. Go to the **Policy** → **** → **Intrusion Prevention** → **Policy Types** → **Inspection Options** page and add an inspection options policy, or update an existing policy. 2. On the **Traffic Inspection** tab, under **Miscellaneous**, enable **Layer 7 Data Collection** in the required direction. 3. Configure the fields **URL Reputation Analysis** and **Minimal URL Risk** on the **GTI Reputation Services** tab. 4. Select the required Sensor(s) which you need to assign the policy to for the detection of these IoC types. For more information, see [Add an inspection options policy](/network-and-platform/docs/add-an-inspection-options-policy-2) and [Enable Layer 7 Data Collection for an interface or subinterface](/network-and-platform/docs/enable-layer-7-data-collection-for-an-interface-or-subinterface-2). | | **File Hash** | 1. Go to **Policy** → **** → **Intrusion Prevention** → **Policy Types** → **Advanced Malware** page and create an Advanced Malware policy, or edit an existing one. 2. Under the **File Scanning Options**, update the **File Type**, **File Size** for the **Threat Feed/ Local Block List** Malware Engine, and configure **Action Thresholds** to determine Sensor response to this IoC type. 3. Assign the policy to the required Sensor(s). For more information, see [Add an Advanced Malware Policy](/network-and-platform/docs/add-an-advanced-malware-policy-6). |