--- title: "Browser redirect" slug: "browser-redirect" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-10-05T15:40:08Z published: 2026-10-05T15:40:08Z canonical: "docs.trellix.com/browser-redirect" --- > ## 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. # Browser redirect Browser redirect ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-EB7C3915-9138-4935-A683-9A4FEC53132B-low(1).png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A12%3A42Z&se=2026-11-22T15%3A12%3A42Z&sr=c&sp=r&sig=VagnIsxdLl9iU28DlmJHErcJ3DWtjEu1wvFpl2Je6jc%3D) When a user attempts to browse to a location outside the **Quarantine Zone**, the Sensor can be configured to intercept the HTTP request and respond with a browser message explaining the reason for quarantine and its duration. Consider the illustration presented. Browser redirect message sent by the Sensor to the quarantined endpoint ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-A7024FC8-21BC-44E4-8653-0234772DB018-low.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A12%3A42Z&se=2026-11-22T15%3A12%3A42Z&sr=c&sp=r&sig=VagnIsxdLl9iU28DlmJHErcJ3DWtjEu1wvFpl2Je6jc%3D) Marco's endpoint was quarantined by the Sensor when the Sensor detected the endpoint launching an attack. Now, when he attempts to browse to a business critical finance portal which lies outside the designated **Quarantine Zone**, he receives a notification from the browser stating that his endpoint has been quarantined. What actually happened here was the administrator of Marco's network had configured the Sensor to: - Quarantine an endpoint if it attempted to launch an attack. - Respond with a browser message which stated the reason for quarantine if the quarantined endpoint user attempted to access a URL outside the **Quarantine Zone**. Configuration of Quarantine based on attack ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-91806933-9CAC-4CB2-8465-A8F8703D1D00-low.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A12%3A42Z&se=2026-11-22T15%3A12%3A42Z&sr=c&sp=r&sig=VagnIsxdLl9iU28DlmJHErcJ3DWtjEu1wvFpl2Je6jc%3D) Marco's administrator had firstly enabled quarantine for all the hosts which are generating a specific attack by quarantining the attacker IP. The next thing the administrator did to ensure every quarantined endpoint that generated this attack receives an HTTP response was to select the **Quarantine and Remediate Attacker** option in **Quarantine** drop-down in the **Attack Definitions** page for the policy. Settings in the Quarantine page for the admin domain ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-409230D2-AB44-4813-8A03-9330B693F9DB-low.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A12%3A42Z&se=2026-11-22T15%3A12%3A42Z&sr=c&sp=r&sig=VagnIsxdLl9iU28DlmJHErcJ3DWtjEu1wvFpl2Je6jc%3D) The administrator had then configured the Sensor in the **Default Port Settings** page in the Manager. In order to quarantine any violating endpoints, the administrator enables **Would you like to quarantine endpoints that attempt intrusions?**. And once an endpoint has been quarantined, in order to respond with a browser message, the administrator enables **Would you like to intercept HTTP requests from quarantined endpoints and respond with a browser message explaining why they have been quarantined?**. Similar configurations of this feature can be done from the following locations in the Manager: - [Quarantine for an admin domain](/network-and-platform/docs/quarantine-settings-for-an-admin-domain) - [Quarantine for a Sensor](/network-and-platform/docs/quarantine-settings-at-sensor-level) - [Quarantine configuration in the policies](/network-and-platform/docs/quarantine-configuration-in-the-policies)