--- title: "HTTP2 traffic inspection" slug: "http2-traffic-inspection-1" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:26:19Z published: 2026-11-19T12:26:19Z canonical: "docs.trellix.com/http2-traffic-inspection-1" --- > ## 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. # HTTP2 traffic inspection ### Introduction IPS supports HTTP2 inspection for the following scenarios: - HTTP2 Prior Knowledge - HTTP2 over TLS > [!NOTE] > Note > > HTTP2 upgrade (h2c) scenario is not supported. When you install/upgrade the Manager, by default, HTTP2 traffic inspection is not enabled. ### Enable HTTP2 traffic inspection from the Manager You can enable HTTP2 traffic inspection at both Global and Devices level in the Manager. To enable HTTP2 traffic inspection at Global level, go to **Devices** → **** → **Global** → **IPS Device Settings** → **Advanced Device Settings** and select **Enable HTTP2 Traffic**. **Advanced Device Settings at Global level**![Advanced Device Settings at Global level](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-e4080a94-86f0-0952-bbf4-e9ce4621318f(7).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A14Z&se=2026-11-20T11%3A08%3A14Z&sr=c&sp=r&sig=rTwIs6JGdnvmfct2DNhILlUgdY87hcvD0lWptTcqNfs%3D) To enable HTTP2 traffic inspection at Devices level, go to **Devices** → **** → **Devices** → **** → **Setup** → **Advanced** → **Advanced Device Settings** and select **Enable HTTP2 Traffic**. **Advanced Device Settings at Device level**![Advanced Device Settings at Device level](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-85b0e232-115e-f20f-fecd-64af9887c768(7).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A14Z&se=2026-11-20T11%3A08%3A14Z&sr=c&sp=r&sig=rTwIs6JGdnvmfct2DNhILlUgdY87hcvD0lWptTcqNfs%3D) > [!NOTE] > Note > > By default, **Enable HTTP2 Traffic** is disabled. After enabling the HTTP2 traffic inspection from **Devices** tab, follow the below steps: 1. Go to **Policy** → **** → **Intrusion Prevention** → **Policy Types** → **Inspection Options**. 2. Navigate to **Inspection Options** tab and click **Traffic Inspection** tab. 3. Configure **HTTP Response Traffic Scanning** based on your requirement. 4. Go to **HTTP2** section, configure **HTTP2 Traffic Scanning** and **HTTP2 Server Push Traffic Scanning** based on your requirement. 5. Click **Save**. **Notes:** - The Sensor requires a reboot when you enable or disable **HTTP2 Traffic Scanning**. You can check the Sensor reboot status from **Device Manager** or `status` CLI. - **HTTP2 Traffic Scanning** can be enabled only when **HTTP Response Traffic Scanning** is enabled. - **HTTP2 Server Push Traffic Scanning** can be enabled only when **HTTP2 Traffic Scanning** is enabled. - HTTP2 traffic inspection requires a sigset with HTTP2 features. - Only NS9600, NS9500, NS7600, NS7500, and NS3600 Sensors support HTTP2 traffic inspection. - From 11.1.5.122, HTTP2 traffic inspection with TLS and proxy-based SSL decryption is supported. - HTTP2 performance numbers align with HTTP 1.1 for supported Sensor models. **Inspection Options: Traffic Inspection**![Inspection Options: Traffic Inspection](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-336058c8-09f2-3a91-9397-47963bc5b0a1(7).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A14Z&se=2026-11-20T11%3A08%3A14Z&sr=c&sp=r&sig=rTwIs6JGdnvmfct2DNhILlUgdY87hcvD0lWptTcqNfs%3D) **HTTP2 Protocol settings** You can configure the HTTP2 protocol settings for any required Sensor from **Devices** → **** → **Devices** → **** → **Setup** → **Advanced** → **Protocol Settings**. Go to **HTTP2** section, and configure the following: | Parameters | Description | | --- | --- | | **Flow Allocation %** | Set the maximum HTTP2 flows as a percentage of total supported flows. Flow allocation differs for each Sensor model. For NS3600, NS7500, NS7600, NS9500 and NS9600 Sensors the min and max flow allocation are as follows: - NS3600 and NS7500 - It can range from 1% to 5%. - NS7600, NS9500 and NS9600 - It can range from 1% to 10%. After configuring, click **Update** to apply the changes. > [!NOTE] > Note > > The Sensor requires a reboot after updating the flow allocation. | | **Include decoded packets in attack packet log** | While inspecting HTTP2 traffic, the Sensor decodes the HTTP2 packets/frames into HTTP requests/responses. By enabling this, the Manager will include decoded HTTP requests/responses along with HTTP2 packets/frames in the attack packet log. After configuring, click **Update** to apply the changes. | | **Slowloris Attack Configuration** | Allows you to configure the values for the following parameters: - **Slow Post Timeout** - Set the value between 5 and 30. - **Slow Post Threshold Frame Size** - Set the value between 1 and 100. - **Slow Post Minimum Number of Streams** - Set the value between 50 and 100. - **Slow Post Min Number of Tiny Frames** - Set the value between 1 and 10. - **Slow Read Timeout** - Set the value between 30 and 300. - **Slow Read Window Size** - Set the value between 1 and 100. - **Slow Read Minimum Number of Streams** - Set the value between 50 and 100. > [!NOTE] > Note > > Users are recommended to modify these configurations only in consultation with Trellix support team. | **HTTP2 Protocol Settings**![HTTP2 Protocol Settings](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-8246d0a8-d119-0248-d9fe-7f58dfd7b24a(7).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A14Z&se=2026-11-20T11%3A08%3A14Z&sr=c&sp=r&sig=rTwIs6JGdnvmfct2DNhILlUgdY87hcvD0lWptTcqNfs%3D) **Alert enhancements for HTTP2** The following new alert fields are included in Layer 7 data: - HTTP2_STREAM_ID - HTTP2_SETTINGS_ENABLE_PUSH - HTTP2/3_HTTP_VERSION You can customize the alert fields from **Devices** → **** → **Devices** → **** → **Setup** → **Advanced** → **L7 Data Collection**. > [!NOTE] > Note > > **HTTP2/3 HTTP VERSION** is always enabled. **Layer 7 Data Collection**![Layer 7 Data Collection](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-7ad217b3-d536-0921-6e51-2460a049b77e(7).jpg?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A14Z&se=2026-11-20T11%3A08%3A14Z&sr=c&sp=r&sig=rTwIs6JGdnvmfct2DNhILlUgdY87hcvD0lWptTcqNfs%3D) **Filter HTTP2 alerts** You can filter HTTP2 alerts through the **Attack Log** or **Reports** page in the Manager. **Attack Log** To focus on attacks detected on HTTP2 traffic, you can apply the filter in the **Attack Log**. To apply the filter, select **Filters** from **Layer 7 Data** column drop-down and in the search field, enter **HTTP2/3 HTTP VERSION: HTTP2**. **Layer 7 Data: Filter value**![Layer 7 Data: Filter value](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-098f79c1-a244-2aff-619e-7d361604a74c(7).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A14Z&se=2026-11-20T11%3A08%3A14Z&sr=c&sp=r&sig=rTwIs6JGdnvmfct2DNhILlUgdY87hcvD0lWptTcqNfs%3D) **Alerts for attacks detected on HTTP2 traffic**![Alerts for attacks detected on HTTP2 traffic](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a2edba71-5a54-1fb1-ed60-9bd4c55446c0(7).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A14Z&se=2026-11-20T11%3A08%3A14Z&sr=c&sp=r&sig=rTwIs6JGdnvmfct2DNhILlUgdY87hcvD0lWptTcqNfs%3D) For a particular alert, you can differentiate the HTTP2 alerts by verifying the **Protocol** data in **Summary** tab of **Details** panel in **Attack Log** page. **Summary tab**![Summary tab](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-b6899f0a-5380-86f4-2911-b462a7a57290(7).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A14Z&se=2026-11-20T11%3A08%3A14Z&sr=c&sp=r&sig=rTwIs6JGdnvmfct2DNhILlUgdY87hcvD0lWptTcqNfs%3D) You can also verify the HTTP2 alerts through the **Layer 7** section in **Details** tab of **Details** panel in **Attack Log** page. **Details tab**![Details tab](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-d7824474-ab4f-1047-7b48-cfee0b3b6eb8(7).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A08%3A14Z&se=2026-11-20T11%3A08%3A14Z&sr=c&sp=r&sig=rTwIs6JGdnvmfct2DNhILlUgdY87hcvD0lWptTcqNfs%3D) **Reports** You can follow the below steps to create HTTP2 reports: 1. Go to **Analysis** → **** → **Event Reporting** → **Custom Reports**. 2. In the **Custom Reports** page, select **New**. 3. Select the type of data as **Alert Data** and click **Next**. 4. Specify the required display and click **Next**. 5. Specify the required fields and click **Next**. 6. Select **Protocol** and set the property value to be equal to **HTTP2** and click **Next**. 7. Configure the **Date Options** and **Report Format**. 8. Click **Run**. **Supported features with HTTP2** In this release, IPS supports following HTTP2 attack categories: - Attack content in a single HTTP2 stream - Attack content across multiple HTTP2 stream - HTTP2 protocol compliance attacks - HTTP2 DoS attacks **Unsupported features with HTTP2** In this release, the following features are not supported over HTTP2 connections: - Malware scanning - URL Reputation - Application Identification - SSL (Known Key, Agent) - Mandate Authentication/HTTP Redirection - Layer 7 Distributed DoS - Trellix Snort Rules - Botnet detection over HTTP - Connection limiting - X-Forwarded-For Header Parsing (XFF) - Decompression (Gzip, Deflate) and Decoding (Chunk, HTML) - Shell Code Detection - Firewall - File Reputation - Web Security - IPS Quarantine