<?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: Cisco ISE Version 3.0 posture provisioning in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4553227#M572809</link>
    <description>&lt;P&gt;Look great let me narrow it down and try with this rule, then I will let you know the result. Thank&lt;/P&gt;</description>
    <pubDate>Wed, 16 Feb 2022 02:11:21 GMT</pubDate>
    <dc:creator>bunleang</dc:creator>
    <dc:date>2022-02-16T02:11:21Z</dc:date>
    <item>
      <title>Cisco ISE Version 3.0 posture provisioning</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4545366#M572587</link>
      <description>&lt;P&gt;Hi all ISE experts,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone could tell me how to apply dacl profile to clients while posture scan found device non-compliance&amp;nbsp;&lt;/P&gt;&lt;P&gt;- non-compliance devices blocked access to the internal system&lt;/P&gt;&lt;P&gt;- non-compliance internet must be accessible&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Feb 2022 08:31:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4545366#M572587</guid>
      <dc:creator>bunleang</dc:creator>
      <dc:date>2022-02-04T08:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Version 3.0 posture provisioning</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4545438#M572589</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1267184"&gt;@bunleang&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This sounds like a standard scenario for posture assessment.&lt;/P&gt;
&lt;P&gt;Please check &lt;A href="https://community.cisco.com/t5/security-documents/ise-posture-prescriptive-deployment-guide/ta-p/3680273" target="_self"&gt;ISE Posture Prescriptive Guide&lt;/A&gt; to understand concepts and to see how to implement it.&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Milos&lt;/P&gt;</description>
      <pubDate>Fri, 04 Feb 2022 10:51:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4545438#M572589</guid>
      <dc:creator>Milos_Jovanovic</dc:creator>
      <dc:date>2022-02-04T10:51:11Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Version 3.0 posture provisioning</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4545485#M572590</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Anyone could tell me how to apply dacl profile to clients while posture scan found device non-compliance&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-You will need a separate authz profile, which contains your desired dacl, that you will use in your radius authorization policy for noncompliant clients.&amp;nbsp; Your conditions in the authz policy will contain Session:Posture Status EQUALS NonCompliant.&amp;nbsp; Then for the result profile assign the authz profile for noncompliant use cases that contains your respective dacl.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Authz/dacl can be created here: Policy-&amp;gt;Policy Elements-&amp;gt;Results-&amp;gt;Authorization&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Feb 2022 12:20:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4545485#M572590</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2022-02-04T12:20:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Version 3.0 posture provisioning</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4552844#M572788</link>
      <description>&lt;P&gt;Could you share me sample guide with auth dacl access-list rule?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 15:46:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4552844#M572788</guid>
      <dc:creator>bunleang</dc:creator>
      <dc:date>2022-02-15T15:46:14Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Version 3.0 posture provisioning</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4552858#M572789</link>
      <description>&lt;P&gt;I would recommend looking at the guide&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/330320"&gt;@Milos_Jovanovic&lt;/a&gt;&amp;nbsp;shared and this one:&amp;nbsp;&lt;A href="https://community.cisco.com/t5/security-documents/ise-secure-wired-access-prescriptive-deployment-guide/ta-p/3641515" target="_blank"&gt;https://community.cisco.com/t5/security-documents/ise-secure-wired-access-prescriptive-deployment-guide/ta-p/3641515&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 16:01:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4552858#M572789</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2022-02-15T16:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Version 3.0 posture provisioning</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4552934#M572796</link>
      <description>&lt;P&gt;Personally I would apply the following rules on the non-compliant DACL, you can narrow them down if you want:&lt;/P&gt;
&lt;P&gt;permit udp any eq bootpc any eq bootps&lt;/P&gt;
&lt;P&gt;permit udp any any eq 53&lt;/P&gt;
&lt;P&gt;deny ip any 10.0.0.0 0.255.255.255&lt;/P&gt;
&lt;P&gt;deny ip any 172.16.0.0 0.15.255.255&lt;/P&gt;
&lt;P&gt;deny ip any 192.168.0.0 0.0.255.255&lt;/P&gt;
&lt;P&gt;permit tcp any any eq 80&lt;/P&gt;
&lt;P&gt;permit tcp any any eq 443&lt;/P&gt;
&lt;P&gt;deny ip any any&lt;/P&gt;
&lt;P&gt;Keep in mind please that if you want to apply the above DACL to an old WLC, then you need to create the ACL on the WLC, and from ISE authorization profile instead of enabling the check on the "DACL Name" and select the DACL, you would need to enable the "Airespace ACL Name" and provide the name of the ACL you created on the WLC.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 17:32:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4552934#M572796</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2022-02-15T17:32:43Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Version 3.0 posture provisioning</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4553227#M572809</link>
      <description>&lt;P&gt;Look great let me narrow it down and try with this rule, then I will let you know the result. Thank&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 02:11:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-version-3-0-posture-provisioning/m-p/4553227#M572809</guid>
      <dc:creator>bunleang</dc:creator>
      <dc:date>2022-02-16T02:11:21Z</dc:date>
    </item>
  </channel>
</rss>

