<?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: Client Provisioning Policy in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/client-provisioning-policy/m-p/3337865#M550034</link>
    <description>&lt;P&gt;Here is the basic difference between posture policies and client provisioning.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Posture: These are policies that are&amp;nbsp;related to any sort of program/files/updates/etc.&amp;nbsp;that exist on the client.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Client Provisioning: These policies are really only related to Cisco AnyConnect or posture modules from ISE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example you may have a posture policy to check AV status, and if the endpoint AV is out of date you might put it in a VLAN where it can only hit the AV update server. Once the AV is up to date the endpoint is allowed normal network access. Now you have a client provisioning policy to push out the XML file for the AnyConnect&amp;nbsp;corporate VPN connection, it sees that the endpoint doesn't have the correct XML file and now the client gets the updated XML from ISE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hopefully this gives some clarification between the 2 policies. &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 26 Feb 2018 14:44:39 GMT</pubDate>
    <dc:creator>Ben Walters</dc:creator>
    <dc:date>2018-02-26T14:44:39Z</dc:date>
    <item>
      <title>Client Provisioning Policy</title>
      <link>https://community.cisco.com/t5/network-access-control/client-provisioning-policy/m-p/3337611#M550033</link>
      <description>&lt;P&gt;Hello Community,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am&amp;nbsp;New to ISE 2.1&amp;nbsp;and getting confused while understanding&amp;nbsp;Posture policy&lt;/P&gt;
&lt;P&gt;why do we need to define CPP Policy separate.&lt;/P&gt;
&lt;P&gt;we define posture conditions under "Policy Elements &amp;gt; Conditions&amp;nbsp; &amp;gt; Posture"&lt;/P&gt;
&lt;P&gt;and then Action items under&amp;nbsp;&amp;nbsp; "Policy Elements &amp;gt;&amp;nbsp;Results&amp;nbsp; &amp;gt; Posture"&lt;/P&gt;
&lt;P&gt;I think we call the above condition and results which we created under Posture Policy - Correct me if I am wrong here&lt;/P&gt;
&lt;P&gt;then what is the use&amp;nbsp;of CPP ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Suggestions would be very helpful.&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:46:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/client-provisioning-policy/m-p/3337611#M550033</guid>
      <dc:creator>Ali</dc:creator>
      <dc:date>2020-02-21T18:46:38Z</dc:date>
    </item>
    <item>
      <title>Re: Client Provisioning Policy</title>
      <link>https://community.cisco.com/t5/network-access-control/client-provisioning-policy/m-p/3337865#M550034</link>
      <description>&lt;P&gt;Here is the basic difference between posture policies and client provisioning.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Posture: These are policies that are&amp;nbsp;related to any sort of program/files/updates/etc.&amp;nbsp;that exist on the client.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Client Provisioning: These policies are really only related to Cisco AnyConnect or posture modules from ISE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example you may have a posture policy to check AV status, and if the endpoint AV is out of date you might put it in a VLAN where it can only hit the AV update server. Once the AV is up to date the endpoint is allowed normal network access. Now you have a client provisioning policy to push out the XML file for the AnyConnect&amp;nbsp;corporate VPN connection, it sees that the endpoint doesn't have the correct XML file and now the client gets the updated XML from ISE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hopefully this gives some clarification between the 2 policies. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Feb 2018 14:44:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/client-provisioning-policy/m-p/3337865#M550034</guid>
      <dc:creator>Ben Walters</dc:creator>
      <dc:date>2018-02-26T14:44:39Z</dc:date>
    </item>
  </channel>
</rss>

