--- title: "Configure Web Server - Denial-of-Service Protection at the admin domain node and interface level" slug: "configure-web-server-denial-of-service-protection-admin-domain-node-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:26:19Z published: 2026-11-19T12:26:19Z canonical: "docs.trellix.com/configure-web-server-denial-of-service-protection-admin-domain-node-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 Web Server - Denial-of-Service Protection at the admin domain node and interface level The Layer 7 DoS protection settings for web servers are disabled by default. You can configure the Layer 7 DoS inspection options in the parent domain at a global level and inherit these options in the child admin domains (interfaces and subinterfaces). You can modify the inherited settings at the child admin domains. You can also modify the setting at the interface level. 1. Click the **Policy** tab. 2. Select the domain from the **Domain** drop‑down list. 3. Navigate to **Intrusion Prevention** → **Policy Types** → **Inspection Options**. 4. To create a new policy, click ![GUID-E7BA235E-C8E9-494B-A481-32F301FEAAB8-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a265d0b5-4039-16f5-7bb1-cb4512697e13(8).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A44%3A54Z&se=2026-11-20T11%3A44%3A54Z&sr=c&sp=r&sig=HSN1M8gro5CWJsRE5LeekHs2i6fylJiAwTl372ycBPk%3D). To edit an already existing policy, double click on the policy. If you are creating a new policy, proceed to step 5. If you are editing an already existing policy, proceed to step 6. The following substeps have to be followed when configuring Layer 7 DoS protection at an interface level: 1. In the **Policy** tab, after selecting the **Domain**, navigate to **Intrusion Prevention** → **Policy Manager**. 2. On the **Interface** tab, double-click the interface to enable Layer 7 DoS protection. The **** panel opens. 3. In the **Inspection Options** section, select the policy from the **Policy** drop down list. To create a new policy, click the ![GUID-E7BA235E-C8E9-494B-A481-32F301FEAAB8-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a265d0b5-4039-16f5-7bb1-cb4512697e13(8).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A44%3A54Z&se=2026-11-20T11%3A44%3A54Z&sr=c&sp=r&sig=HSN1M8gro5CWJsRE5LeekHs2i6fylJiAwTl372ycBPk%3D) icon or click the ![GUID-6E2D5582-3868-4FBA-BA20-20A3995E8669-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-4f159cfa-68ca-d13f-1bc3-b7999c42d5c5(12).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A44%3A54Z&se=2026-11-20T11%3A44%3A54Z&sr=c&sp=r&sig=HSN1M8gro5CWJsRE5LeekHs2i6fylJiAwTl372ycBPk%3D) icon to edit an already assigned policy. You can also assign a policy to an interface by selecting the **Prompt for assignment after save** option in the **Inspection Options** page. If you are creating a new policy proceed to step 5. If you are editing an existing policy proceed to step 6. 5. The **Properties** page opens. Enter the **Name** and **Description**. Select the **Visibility** and click **Next**. The **Inspection Options** page opens. **Configuration of Web Server-Denial of Service**![Configuration of Web Server-Denial of Service](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-3a98328b-32a0-34bf-bdea-97e5fddf23ad(3).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A44%3A54Z&se=2026-11-20T11%3A44%3A54Z&sr=c&sp=r&sig=HSN1M8gro5CWJsRE5LeekHs2i6fylJiAwTl372ycBPk%3D) 6. Configure the following DoS protection settings. **Web Server - option definitions** | Option | Definition | | --- | --- | | **Denial-of-Service Prevention** | Select the direction of traffic for which you would like to configure the DoS prevention. | | **Maximum Simultaneous Connections Allowed to All Web Servers** | Specifies the threshold for maximum connections allowed to all web servers from a host. When connection limiting rules are created, whichever has smaller threshold raises an alert first. > [!NOTE] > Note > > The allowed configuration range for the maximum connection threshold to all web servers is 10 to 2,147,483,647. | | **Slow-Connection Attack Prevention** | Enable this option to close 10% of the oldest slow open connections. This option is disabled by default. | | **Maximum HTTP Requests/Second Allowed to Any Website Path** | Specifies the threshold for maximum HTTP requests allowed to all website per second | | **Client Browser Detection** | Enable this option to send a challenge back to the user to determine if the HTTP requests are originating from valid browsers or Bots. | | **Browser Detection Method** | The detection methods use the challenge/response mechanism to detect a valid client browser. The options are **HTML Challenge** and **JavaScript Challenge**. This option is not supported in span and tap modes. | | **Website Paths to Protect** | Specify website paths to which the HTTP requests are sent, to be protected. You can protect **All** or **Specific** paths. A maximum of 64 website paths per Sensor and 8 website paths per interface can be protected. | | **Website Paths to Protect** | | **New Website Path** | Enter the website paths that you want to protect in **New Website Path** and click **Add**. For example, if you specify /trellix.com as a path, then the Sensor inspects only those requests that contain /trellix.com. - **Path** — Specify the website path you would like to protect. - **Requests/Second** — Specify the maximum HTTP requests allowed to the protected website path. - To delete a website path, hover over the path and click the **X** icon. | 7. Click **Save**.