Saturday, May 22, 2021

Cisco ASA Change HTTPS port

We can configure firewall devices in two ways. The first one is the command-line mode and the other one is the graphical mode. To take the command-line access through the network, we can use some kind of terminal emulator software like "Putty" and if we want to take the graphical mode access then we can use the ASDM tool. The ASDM is the Cisco proprietary tool and can be downloaded directly from the Cisco website. 

Using ASDM (Adaptive Security Device Manager), we can take secure access to the Cisco ASA firewall device. The HTTPS server is usually enabled in the firewall's network interfaces. Later, the ASDM tool is used to connect that network interface's HTTPS server so that secure communication can take place between the client system and the firewall. We knew that the HTTPS server is used TCP port 443 and that's why in the ASDM  tool we use that TCP port to connect to that HTTPS server or firewall. But sometimes we may want to change this default HTTPS port for security purposes.

In this tutorial, we will learn how to change this default HTTPS server port to another TCP port number.
To change the HTTPS server port or ASDM port, we will use the Cisco ASDM tool, and we will go through the step-by-step process.

After login into the firewall using ASDM, we will go to the "Configuration" tab and then we will select "Device Management" from the left panel.


Now expand the "Management Access" tree from the "Device Management" list.


Now you will get a list of the HTTPS server enabled interface and their associated port number.


From here, you can change the HTTPS port number, also you can enable or disable the HTTPS server for a specific interface.

After changing the default HTTPS port number, you must have specified the updated number during the ASDM login process. Such as we changed our HTTPS port to 5555. Then we have to specify it into the ASDM "Device IP Address" field. Just like as follows:


That's the process to change the default HTTPS port number.

No comments:

Post a Comment