<div>
<div class="content wysiwyg-content">
I have the below scenario...<br />
I have a Cisco ASA firewall connected to Internet via public IP. <br />
I have a URL published in the internet pointing to hte public IP <br />
ex abc.test.com -&gt; 1.1.1.1<br />
<br />
In the ASA i have configured SSL VPN to send the request to my web server.<br />
The ASA is configured to send the request to Web Server on port 5555<br />
10.10.10.10:5555<br />
<br />
<br />
So whenever user browse the URL it hits the ASA &amp;&nbsp;ASA sends the request to the Web server <br />
<br />
The web server intern connects to the App Server . The communication between App &amp;&nbsp;Web Server occurs on many ports.<br />
When the Web server talks back to the Firewall what port should the Web server should use. Does it uses the port 5555 or any other port which is used between the Web &amp;&nbsp;App server.
</div>
</div>


I have the below scenario...
I have a Cisco ASA firewall connected to Internet via public IP. 
I have a URL published in the internet pointing to hte public IP 
ex abc.test.com -> 1.1.1.1

In the ASA i have configured SSL VPN to send the request to my web server.
The ASA is configured to send the request to Web Server on port 5555
10.10.10.10:5555


So whenever user browse the URL it hits the ASA & ASA sends the request to the Web server 

The web server intern connects to the App Server . The communication between App & Web Server occurs on many ports.
When the Web server talks back to the Firewall what port should the Web server should use. Does it uses the port 5555 or any other port which is used between the Web & App server.

Cisco ASA Clientless Web VPN

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Network security consists of the policies adopted to prevent and monitor authorized access, misuse, modification, or denial of a computer network and network-accessible resources. Network security involves the authorization of access to data in a network, and covers a variety of computer networks; conducting transactions and communications among businesses, government agencies and individuals. Networks can be private, such as within a company, and others which might be open to public access.