<?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 How to best switch 4.2 design to 5.3 scaleable model in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/how-to-best-switch-4-2-design-to-5-3-scaleable-model/m-p/2001710#M206171</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Drew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACS 5.3 will help you with you current situation. With ACS 4 there was the group mapping landscape in the way users were mapped and dropped in a bucket with those operations. ACS 5.x is a policy driven solution and can really does process policies based on the endpoint and can combine multiple policies in order to match a result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the basics of ACS 5 and the comparison of ACS 4 - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.3/user/guide/policy_mod.html"&gt;http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.3/user/guide/policy_mod.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Aug 2012 03:19:56 GMT</pubDate>
    <dc:creator>Tarik Admani</dc:creator>
    <dc:date>2012-08-16T03:19:56Z</dc:date>
    <item>
      <title>How to best switch 4.2 design to 5.3 scaleable model</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-best-switch-4-2-design-to-5-3-scaleable-model/m-p/2001709#M206163</link>
      <description>&lt;P&gt;Hi All;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am somewhat a Newbie with ACS, and am trying to document, resolve and understand a 4.2 implementation in preparation for an upgrade to current version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In our system we might have 20 engineers, some of whom need access to some of 10 service groups, where a service group could be 3 servers in a cluster providing a network service like logging, SIEM, Configuration control, Key Management etc.&lt;/P&gt;&lt;P&gt;Engineer A might need access to Logging Servers and SIEMs&lt;/P&gt;&lt;P&gt;Engineer B might need access to SIEMS and Key Management servers&lt;/P&gt;&lt;P&gt;Engineer C might need access to Key Management Servers and Logging servers.&lt;/P&gt;&lt;P&gt;Because each engineer uses a single admin user object held in the local ACS internal database, I believe the engineer can be a member of only 1 ACS group.&lt;/P&gt;&lt;P&gt;And there is no easy way to create groups that match to all the different role combinations.&lt;/P&gt;&lt;P&gt;What was put in place with ACS 4.2 was:&lt;/P&gt;&lt;P&gt;Create a separate group for each engineer.&lt;/P&gt;&lt;P&gt;For each network service like Logging or SIEM, place all the logging servers in a separate dedicated NDG&lt;/P&gt;&lt;P&gt;Create a separate policy for access to logging servers&lt;/P&gt;&lt;P&gt;Then for each of the 4 out of our 20 engineers that need access to the logging servers, create 4 permit rules in the Logging NAP policy, a separate permit rule for each of the 4 engineers.&lt;/P&gt;&lt;P&gt;This is not a design to be overly proud of, and is not very scalable, but it works fine at our level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand ACS 5.3 provides a more elegant and scalable solution. Can you please advise/provide links to clarify a preferred solution?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Drew&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:25:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-best-switch-4-2-design-to-5-3-scaleable-model/m-p/2001709#M206163</guid>
      <dc:creator>drewgans</dc:creator>
      <dc:date>2019-03-11T02:25:55Z</dc:date>
    </item>
    <item>
      <title>How to best switch 4.2 design to 5.3 scaleable model</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-best-switch-4-2-design-to-5-3-scaleable-model/m-p/2001710#M206171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Drew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACS 5.3 will help you with you current situation. With ACS 4 there was the group mapping landscape in the way users were mapped and dropped in a bucket with those operations. ACS 5.x is a policy driven solution and can really does process policies based on the endpoint and can combine multiple policies in order to match a result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the basics of ACS 5 and the comparison of ACS 4 - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.3/user/guide/policy_mod.html"&gt;http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.3/user/guide/policy_mod.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Aug 2012 03:19:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-best-switch-4-2-design-to-5-3-scaleable-model/m-p/2001710#M206171</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2012-08-16T03:19:56Z</dc:date>
    </item>
  </channel>
</rss>

