<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Application port in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/application-port/m-p/1640174#M604583</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ST,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By default in an ASA, if no access-list is applied on the inside interface then all traffic going from inside (higher sec level) to outside(lower sec level) would be allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What kind of application are you running ? If its a TCP based application then you do not need to apply any access-list on the outside interface too. this is because, ASA will maintain a state of TCP based applications.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyways, If you would like to find out the port numbers that the application is using, you can apply captures on the inside interface. This would capture details about the packet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following is the method of applying captures :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list capi permit ip host &lt;SOURCE ip=""&gt; host &lt;DESTINATION ip=""&gt;&lt;/DESTINATION&gt;&lt;/SOURCE&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list capi permit ip host &lt;DESTINATION ip=""&gt; host &lt;SOURCE ip=""&gt;&lt;/SOURCE&gt;&lt;/DESTINATION&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;capture capin access-l capi interface inside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, when you do a &lt;STRONG&gt;sh capture capin detail&lt;/STRONG&gt;, you would be able to see the the source and destination ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope I could answer your question!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Manasi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Dec 2010 14:38:37 GMT</pubDate>
    <dc:creator>manasjai</dc:creator>
    <dc:date>2010-12-24T14:38:37Z</dc:date>
    <item>
      <title>Application port</title>
      <link>https://community.cisco.com/t5/network-security/application-port/m-p/1640173#M604582</link>
      <description>&lt;P&gt;Hi Experts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We got one application who's ports are unknown to be opened from inside&amp;nbsp; and outside of ASA,&amp;nbsp; For test purpose we allow permit ip&amp;nbsp; any any and it works. How do I identify the ports. &lt;BR /&gt; &lt;BR /&gt;Access-list is applied on inside and outside interface of ASA &lt;BR /&gt;ASA 5520 &lt;BR /&gt;Version 8.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope to get help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;ST&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:27:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/application-port/m-p/1640173#M604582</guid>
      <dc:creator>saquib.tandel</dc:creator>
      <dc:date>2019-03-11T19:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Application port</title>
      <link>https://community.cisco.com/t5/network-security/application-port/m-p/1640174#M604583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ST,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By default in an ASA, if no access-list is applied on the inside interface then all traffic going from inside (higher sec level) to outside(lower sec level) would be allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What kind of application are you running ? If its a TCP based application then you do not need to apply any access-list on the outside interface too. this is because, ASA will maintain a state of TCP based applications.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyways, If you would like to find out the port numbers that the application is using, you can apply captures on the inside interface. This would capture details about the packet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following is the method of applying captures :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list capi permit ip host &lt;SOURCE ip=""&gt; host &lt;DESTINATION ip=""&gt;&lt;/DESTINATION&gt;&lt;/SOURCE&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;access-list capi permit ip host &lt;DESTINATION ip=""&gt; host &lt;SOURCE ip=""&gt;&lt;/SOURCE&gt;&lt;/DESTINATION&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;capture capin access-l capi interface inside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, when you do a &lt;STRONG&gt;sh capture capin detail&lt;/STRONG&gt;, you would be able to see the the source and destination ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope I could answer your question!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Manasi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Dec 2010 14:38:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/application-port/m-p/1640174#M604583</guid>
      <dc:creator>manasjai</dc:creator>
      <dc:date>2010-12-24T14:38:37Z</dc:date>
    </item>
    <item>
      <title>Re: Application port</title>
      <link>https://community.cisco.com/t5/network-security/application-port/m-p/1640175#M604584</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ST,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One more thing to point here is if the traffic is getting initiated from the outside, We should necessarily apply an access-l on the outside interface to permit the required traffic!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Manasi!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Dec 2010 14:42:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/application-port/m-p/1640175#M604584</guid>
      <dc:creator>manasjai</dc:creator>
      <dc:date>2010-12-24T14:42:56Z</dc:date>
    </item>
  </channel>
</rss>

