<?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 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4645730#M576010</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The above is dynamic acl&amp;nbsp; ,this will not help&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jul 2022 10:58:01 GMT</pubDate>
    <dc:creator>bluesea2010</dc:creator>
    <dc:date>2022-07-07T10:58:01Z</dc:date>
    <item>
      <title>cisco ise</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4645651#M576006</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have cisco ise base license , and one&amp;nbsp; ssid with dot1x authentication.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If anyone use corporate device ,I want put them&amp;nbsp; in&amp;nbsp; vlan 10 if not I want put them guest vlan or&amp;nbsp; just give them internet access&amp;nbsp;&lt;/P&gt;&lt;P&gt;or just give them the privilege's of guest users&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 08:30:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4645651#M576006</guid>
      <dc:creator>bluesea2010</dc:creator>
      <dc:date>2022-07-07T08:30:02Z</dc:date>
    </item>
    <item>
      <title>Re: cisco ise</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4645720#M576008</link>
      <description>&lt;P&gt;look at the guide below you may help you :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/212419-configure-per-user-dynamic-access-contro.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/212419-configure-per-user-dynamic-access-contro.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 10:43:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4645720#M576008</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-07-07T10:43:50Z</dc:date>
    </item>
    <item>
      <title>Re: cisco ise</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4645730#M576010</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The above is dynamic acl&amp;nbsp; ,this will not help&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 10:58:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4645730#M576010</guid>
      <dc:creator>bluesea2010</dc:creator>
      <dc:date>2022-07-07T10:58:01Z</dc:date>
    </item>
    <item>
      <title>Re: cisco ise</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4645736#M576011</link>
      <description>&lt;P&gt;You can achieve that by configuring a specific authorization rule that will match the corp devices traffic, where you will also have an authorization profile associated to that rule which in turn will have the VLAN10 configured. For the devices that won't match the corp rule you can rely on the default authorization rule and associate an authorization profile where you have the guest VLAN defined. Alternatively, you can create a custom rule that would match those personal devices and place them into the guest VLAN, however, this won't be an easy one as you wouldn't know all the device types and attributes of those personal devices to make a 100% match. If you want to be more specific in what to allow and deny for the personal device then you can define an dACL and configure it in the authorization profile that would be then associated to the personal devices authorization rule. Regarding the way to deal with the dACLs in this case it depends on what WLC you have, if you have an old one then the dACL should be created on the WLC and referenced in ISE authorization profile in the airespace ACL name section. However, if you have the 9800 WLC then you can define the ACL on ISE itself in the same way you do this for the switches.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 11:16:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4645736#M576011</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2022-07-07T11:16:32Z</dc:date>
    </item>
    <item>
      <title>Re: cisco ise</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4647420#M576056</link>
      <description>&lt;P&gt;"Corporate Device" implies the use of a digital certificate for authentication to identify it as a managed endpoint.&lt;/P&gt;
&lt;P&gt;Are your corporate endpoints provisioned with wired or wireless network profiles to use a digital certificate for authentication with 802.1X or a specific SSID?&lt;/P&gt;
&lt;P&gt;If not, you will need an MDM or other computer management tool to configure it (SCCM, etc).&lt;/P&gt;
&lt;P&gt;You may configure the Guest VLAN as the default VLAN on a switch. See &lt;LI-MESSAGE title="ISE Secure Wired Access Prescriptive Deployment Guide" uid="3641515" url="https://community.cisco.com/t5/security-documents/ise-secure-wired-access-prescriptive-deployment-guide/m-p/3641515#U3641515"&gt;&lt;/LI-MESSAGE&gt; .&lt;/P&gt;
&lt;P&gt;For wireless, you should be using a totally separate Guest SSID to clearly indicate guest services. See &lt;LI-MESSAGE title="ISE Guest Access Prescriptive Deployment Guide" uid="3640475" url="https://community.cisco.com/t5/security-documents/ise-guest-access-prescriptive-deployment-guide/m-p/3640475#U3640475"&gt;&lt;/LI-MESSAGE&gt; .&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jul 2022 22:15:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4647420#M576056</guid>
      <dc:creator>thomas</dc:creator>
      <dc:date>2022-07-08T22:15:35Z</dc:date>
    </item>
    <item>
      <title>Re: cisco ise</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4651095#M576180</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;You mean to use EAP-TLS (certificate based authentication )&amp;nbsp; for corporate devices ,In that case how to do byod devices ?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2022 10:13:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4651095#M576180</guid>
      <dc:creator>bluesea2010</dc:creator>
      <dc:date>2022-07-15T10:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: cisco ise</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4651216#M576188</link>
      <description>&lt;P&gt;MDM &amp;gt;&amp;gt;&amp;gt;&amp;gt; BYOD&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2022 14:12:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/4651216#M576188</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2022-07-15T14:12:43Z</dc:date>
    </item>
  </channel>
</rss>

