<?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: ISE 3.1 posture redirect in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4834341#M581713</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;it works?&lt;/P&gt;</description>
    <pubDate>Fri, 12 May 2023 13:10:26 GMT</pubDate>
    <dc:creator>adrian.ciubotariu.lacatusu</dc:creator>
    <dc:date>2023-05-12T13:10:26Z</dc:date>
    <item>
      <title>ISE 3.1 posture redirect</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4821379#M581367</link>
      <description>&lt;P&gt;I'm helping a coworker set up posture assessment on ISE 3.1. Everything is configured but we are having trouble with the client provisioning/posture redirect.&amp;nbsp; Does anyone have an example of a posture redirect ACL on an IOS switch, or can you point me to documentation with this information? I looked at the ISE 3.1 admin guide but didn't see anything specific on this, and I'm not sure if anything has changed since ISE 2.x.&amp;nbsp; Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 14:38:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4821379#M581367</guid>
      <dc:creator>ben.levin1</dc:creator>
      <dc:date>2023-04-25T14:38:53Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 posture redirect</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4821408#M581369</link>
      <description>&lt;P&gt;For posture redirection on switch, you need to configure below rules:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Deny DNS traffic&lt;/LI&gt;
&lt;LI&gt;Deny DHCP traffic&lt;/LI&gt;
&lt;LI&gt;Deny traffic to ISE PSN on TCP 8443, 8905, 8909 (assuming you are using default ports on ISE for posture)&lt;/LI&gt;
&lt;LI&gt;Permit ip any any&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Logic : On the switch, anything that is denied would be allowed and rest would be redirected. We have to allow DHCP, DNS and traffic to ISE, rest everything should be redirected.&lt;/P&gt;
&lt;P&gt;Also, ensure that https services are running on the switch. ("ip http server" and "ip http secure-server")&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 15:20:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4821408#M581369</guid>
      <dc:creator>Nancy Saini</dc:creator>
      <dc:date>2023-04-25T15:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 posture redirect</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4821508#M581373</link>
      <description>&lt;P&gt;Thanks! We'll give that a shot.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 17:34:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4821508#M581373</guid>
      <dc:creator>ben.levin1</dc:creator>
      <dc:date>2023-04-25T17:34:44Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 posture redirect</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4834341#M581713</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;it works?&lt;/P&gt;</description>
      <pubDate>Fri, 12 May 2023 13:10:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4834341#M581713</guid>
      <dc:creator>adrian.ciubotariu.lacatusu</dc:creator>
      <dc:date>2023-05-12T13:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 3.1 posture redirect</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4839891#M581886</link>
      <description>&lt;P&gt;Also, make sure the IP device tracking is working.&lt;/P&gt;
&lt;P&gt;Another way to define the ACLs is to use both url-redirect-acl and DACL. The url-redirect-acl is usually an ACL configured on the Cisco IOS switch. When we use it in combination with a DACL, the url-redirect-acl can be much simplified, e.g.,&lt;/P&gt;
&lt;LI-CODE lang="c"&gt;ip access-list extended ISE-URL-REDIRECT
 10 deny   tcp any host 10.1.129.8 eq www
 20 permit tcp any any eq www&lt;/LI-CODE&gt;
&lt;P&gt;Then, the DACL may have the following content, where 198.18.133.1 is the DNS server, 198.18.133.27 is the ISE server, and 198.18.0.0/16 represents the internal networks.&lt;/P&gt;
&lt;LI-CODE lang="c"&gt;permit udp any host 198.18.133.1 eq domain
permit tcp any host 198.18.133.27 eq 8443
permit tcp any host 198.18.133.27 eq 8905
permit tcp any host 198.18.133.27 eq 8084
deny   ip any 198.18.0.0 0.0.255.255
permit ip any any&lt;/LI-CODE&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>Sun, 21 May 2023 23:36:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-3-1-posture-redirect/m-p/4839891#M581886</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2023-05-21T23:36:43Z</dc:date>
    </item>
  </channel>
</rss>

