<?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 David. I did some research in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-what-is-cacs/m-p/2569385#M72175</link>
    <description>&lt;P&gt;Hi David. I did some research but could not find much outside of this being a Cisco specific Radius attribute that is also used by ACS. With that being said, I don't think that this is something that you need to worry about. I don't think an ACS/ISE attribute can trigger a GP policy update on your endpoints. I have done many VPN deployments where the endpoints are authenticating against ISE or ACS and I have never had any problems nor I had the need to filter any attributes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Feel free to reach out to Cisco TAC for more details as that is all I have &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Also, feel free to have your network team chime and provide more details with regards to their concerns. You can also test this with some test workstations and confirm weather or not you will see any undesirable results &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Nov 2014 03:11:44 GMT</pubDate>
    <dc:creator>nspasov</dc:creator>
    <dc:date>2014-11-13T03:11:44Z</dc:date>
    <item>
      <title>[Cisco ISE] What is CACS?</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-what-is-cacs/m-p/2569383#M72170</link>
      <description>&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;Dear Sir,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Here is the operation&amp;gt;Authentication detail on my Cisco ISE:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Result&lt;/DIV&gt;&lt;DIV&gt;State&lt;SPAN style="white-space:pre"&gt;&lt;SPAN style="white-space: normal;"&gt; &lt;/SPAN&gt;&lt;/SPAN&gt;ReauthSession:0a01010100077000545c5b8a&lt;/DIV&gt;&lt;DIV&gt;Class&lt;SPAN style="white-space:pre"&gt;&lt;SPAN style="white-space: normal;"&gt; &lt;/SPAN&gt;&lt;/SPAN&gt;OU=VPN-USER2&lt;/DIV&gt;&lt;DIV&gt;Class&lt;SPAN style="white-space:pre"&gt;&lt;SPAN style="white-space: normal;"&gt; &lt;/SPAN&gt;&lt;/SPAN&gt;CACS:0a01010100077000545c5b8a:psn/203756592/237&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I searched many documents, but none of them could tell me what is &amp;nbsp;the meaning of CACS.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;In my authorization profile result, I only configured following:&lt;/DIV&gt;&lt;DIV&gt;Access Type = ACCESS_ACCEPT&lt;/DIV&gt;&lt;DIV&gt;Class = OU=VPN-USER2;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;It seemed that the CACS was some kind of session code, auto-generated for machine processing.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;(1)Hope somebody could help clarify “What is CACS”&lt;/DIV&gt;&lt;DIV&gt;(2) My colleague in network team concern CACS in auth response would lead to some unwanted result in ASA VPN authentication and assigning Gp policy to VPN user. To relive his concern, could we clear out the CACS from auth response?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Million thanks for your kind help.&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 13 Mar 2019 00:44:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-what-is-cacs/m-p/2569383#M72170</guid>
      <dc:creator>david.ausl</dc:creator>
      <dc:date>2019-03-13T00:44:23Z</dc:date>
    </item>
    <item>
      <title>Anyone could help?</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-what-is-cacs/m-p/2569384#M72171</link>
      <description>&lt;P&gt;Anyone could help?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Nov 2014 05:48:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-what-is-cacs/m-p/2569384#M72171</guid>
      <dc:creator>david.ausl</dc:creator>
      <dc:date>2014-11-12T05:48:53Z</dc:date>
    </item>
    <item>
      <title>Hi David. I did some research</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-what-is-cacs/m-p/2569385#M72175</link>
      <description>&lt;P&gt;Hi David. I did some research but could not find much outside of this being a Cisco specific Radius attribute that is also used by ACS. With that being said, I don't think that this is something that you need to worry about. I don't think an ACS/ISE attribute can trigger a GP policy update on your endpoints. I have done many VPN deployments where the endpoints are authenticating against ISE or ACS and I have never had any problems nor I had the need to filter any attributes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Feel free to reach out to Cisco TAC for more details as that is all I have &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Also, feel free to have your network team chime and provide more details with regards to their concerns. You can also test this with some test workstations and confirm weather or not you will see any undesirable results &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Nov 2014 03:11:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-what-is-cacs/m-p/2569385#M72175</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2014-11-13T03:11:44Z</dc:date>
    </item>
  </channel>
</rss>

