<?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 Hi Marco, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-esmtp-inspection-with-tls-for-some-hosts-and-without-tls-for/m-p/2738887#M192959</link>
    <description>&lt;P&gt;Hi Marco,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can just add to your new service policy the ESMTP inspection modifications. Traffic will still match the global policy for any other parameters and protocols.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The "deny" ESMTP ACL entry is not necessary as, just like the ACLs used for interfaces, there will be an implicit "deny ip any any" at the bottom. But in this case, it won't drop traffic. It just means that any other traffic won't be matched.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, if you want to have TLS traffic enabled for that host inbound and outbound, I would suggest the next changes:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Being 192.168.10.1, the device we want to allow TLS.&amp;nbsp;&lt;/P&gt;

&lt;PRE&gt;
! ACL to match interesting traffic
access-list ALLOW-TLS extended permit ip host 192.168.10.1 any
access-list ALLOW-TLS&amp;nbsp;extended permit ip any host 192.168.10.1

!ACL to match everything else but not match interesting traffic.
access-list DENY-TLS extended deny ip host 192.168.10.1 any
access-list DENY-TLS extended deny ip any host 192.168.10.1
access-list DENY-TLS extended permit ip any any

!Allow TLS policy map.
policy-map type inspect esmtp ALLOW-TLS
&amp;nbsp;parameters
&amp;nbsp; allow-tls

!Class matching traffic to support TLS.
class-map ALLOW-TLS
&amp;nbsp;match access-list ALLOW-TLS

!Class matching all other traffic.
class-map DENY-TLS
&amp;nbsp;match access-list DENY-TLS

!Removing default ESMTP inspection and creating new classes
policy-map global_policy
&amp;nbsp;class inspection_default
  no inspect esmtp
&amp;nbsp;exit
&amp;nbsp;class ALLOW-TLS
&amp;nbsp; inspect esmtp ALLOW-TLS
&amp;nbsp;class DENY-TLS
&amp;nbsp; inspect esmtp

&lt;/PRE&gt;

&lt;P&gt;This will create two different classes inside the global policy, so, no matter where the traffic starts, it will be matched and there won't be any policy overlaps.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can tests using the command:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;PRE&gt;
&amp;nbsp; &amp;nbsp; &amp;nbsp;show service-policy flow tcp host x.x.x.x host 192.168.10.1 eq smtp
&lt;/PRE&gt;

&lt;P&gt;By changing&amp;nbsp;x.x.x.x to any desired source IP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this info helps!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Cesar.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Aug 2015 13:28:28 GMT</pubDate>
    <dc:creator>Cesar Gustavo Lopez Zamarripa</dc:creator>
    <dc:date>2015-08-10T13:28:28Z</dc:date>
    <item>
      <title>ASA: ESMTP inspection with TLS for some hosts and without TLS for other hosts</title>
      <link>https://community.cisco.com/t5/network-security/asa-esmtp-inspection-with-tls-for-some-hosts-and-without-tls-for/m-p/2738886#M192958</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to enable ESMTP inspection on one ASA, but since a have devices which don´t support TLS I was wondering how to enable ESMTP with TLS inspection for some hosts and ESMTP without TLS inspection for the others. I added the line "esmtp tls-allow" to the default global_policy so I was thinking in creating another policy-map for the hosts which don´t support TLS as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list ESMTP permit ip host X.X.X.X any&lt;BR /&gt;access-list ESMTP deny ip X.X.X.0 255.255.255.0 any !Would be this line required??&lt;/P&gt;&lt;P&gt;class-map CMAP&lt;BR /&gt;match access-list ESMTP&lt;/P&gt;&lt;P&gt;policy-map PMAP&lt;BR /&gt;class CMAP&lt;BR /&gt;inspect dns preset_dns_map&amp;nbsp;&lt;BR /&gt;................... ! include the&amp;nbsp;default application inspections&lt;BR /&gt;inspect esmtp&amp;nbsp;&lt;/P&gt;&lt;P&gt;service-policy PMAP interface inside&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could anyone tell me whether this configuration would work or not, please?? Many thanks in advance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:24:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-esmtp-inspection-with-tls-for-some-hosts-and-without-tls-for/m-p/2738886#M192958</guid>
      <dc:creator>marcosespinatrigo</dc:creator>
      <dc:date>2019-03-12T06:24:23Z</dc:date>
    </item>
    <item>
      <title>Hi Marco,</title>
      <link>https://community.cisco.com/t5/network-security/asa-esmtp-inspection-with-tls-for-some-hosts-and-without-tls-for/m-p/2738887#M192959</link>
      <description>&lt;P&gt;Hi Marco,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can just add to your new service policy the ESMTP inspection modifications. Traffic will still match the global policy for any other parameters and protocols.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The "deny" ESMTP ACL entry is not necessary as, just like the ACLs used for interfaces, there will be an implicit "deny ip any any" at the bottom. But in this case, it won't drop traffic. It just means that any other traffic won't be matched.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, if you want to have TLS traffic enabled for that host inbound and outbound, I would suggest the next changes:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Being 192.168.10.1, the device we want to allow TLS.&amp;nbsp;&lt;/P&gt;

&lt;PRE&gt;
! ACL to match interesting traffic
access-list ALLOW-TLS extended permit ip host 192.168.10.1 any
access-list ALLOW-TLS&amp;nbsp;extended permit ip any host 192.168.10.1

!ACL to match everything else but not match interesting traffic.
access-list DENY-TLS extended deny ip host 192.168.10.1 any
access-list DENY-TLS extended deny ip any host 192.168.10.1
access-list DENY-TLS extended permit ip any any

!Allow TLS policy map.
policy-map type inspect esmtp ALLOW-TLS
&amp;nbsp;parameters
&amp;nbsp; allow-tls

!Class matching traffic to support TLS.
class-map ALLOW-TLS
&amp;nbsp;match access-list ALLOW-TLS

!Class matching all other traffic.
class-map DENY-TLS
&amp;nbsp;match access-list DENY-TLS

!Removing default ESMTP inspection and creating new classes
policy-map global_policy
&amp;nbsp;class inspection_default
  no inspect esmtp
&amp;nbsp;exit
&amp;nbsp;class ALLOW-TLS
&amp;nbsp; inspect esmtp ALLOW-TLS
&amp;nbsp;class DENY-TLS
&amp;nbsp; inspect esmtp

&lt;/PRE&gt;

&lt;P&gt;This will create two different classes inside the global policy, so, no matter where the traffic starts, it will be matched and there won't be any policy overlaps.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can tests using the command:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;PRE&gt;
&amp;nbsp; &amp;nbsp; &amp;nbsp;show service-policy flow tcp host x.x.x.x host 192.168.10.1 eq smtp
&lt;/PRE&gt;

&lt;P&gt;By changing&amp;nbsp;x.x.x.x to any desired source IP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this info helps!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Cesar.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2015 13:28:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-esmtp-inspection-with-tls-for-some-hosts-and-without-tls-for/m-p/2738887#M192959</guid>
      <dc:creator>Cesar Gustavo Lopez Zamarripa</dc:creator>
      <dc:date>2015-08-10T13:28:28Z</dc:date>
    </item>
  </channel>
</rss>

