ePub(274.9 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(227.5 KB) View on Kindle device or Kindle app on multiple devices
Updated:September 27, 2023
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to configure Windows Browser proxies for Cisco Secure Client connected to FTD Managed by FDM.
Cisco recommends that you have knowledge on these topics:
Cisco Secure Firewall Device Manager (FDM)
Cisco Firepower Threat Defense (FTD)
Cisco Secure Client (CSC)
The information in this document is based on these software and hardware versions:
Cisco Secure Firewall Device Manager Version 7.3
Cisco Firepower Threat Defense Virtual Appliance Version 7.3
Cisco Secure Client Version 5.0.02075
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
The term "proxy" refers to a service that is located between the user and the resource you want to reach. Web browser proxies, specifically, are servers that transmit web traffic so, when navigating to a website, the Secure Client prompts the proxy server to request the site instead of doing it directly.
Proxies can be used to achieve different objectives such as content filtering, traffic handling, and traffic tunneling.
In this document, it is assumed that you already have a working Remote Access VPN configuration.
In the FDM, navigate to Remote Access VPN > Group Policies, click the Edit button on the Group Policy where you want to configure the browser proxy, and navigate to the Windows Browser Proxy section.
From the Browser Proxy During VPN Session dropdown, select Use custom settings.
On the Proxy Server IP or Hostname box, enter the proxy server information and on the Port box, enter the port to reach the server.
If there is an address or hostname that you do not want to reach through the proxy, click the Add Proxy Exemption button and add it here.
Note: Specifying a port on the Browser Proxy Exemption List is optional.
Click Ok and deploy the configuration.
To verify if the configuration was applied successfuly, you can use the CLI of the FTD.