<?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: Limits on AD Client Authz attempts in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/limits-on-ad-client-authz-attempts/m-p/3578870#M509719</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One option is to use Client Exclusions on access device.&amp;nbsp; For example, if the endpoint fails auth X number of times in an interval, the endpoint is prevented from attempting auth again for specified period.&amp;nbsp; You can try setting the exclusion time to a value &amp;gt; than the AD lockout interval.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 May 2018 11:40:27 GMT</pubDate>
    <dc:creator>Craig Hyps</dc:creator>
    <dc:date>2018-05-23T11:40:27Z</dc:date>
    <item>
      <title>Limits on AD Client Authz attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/limits-on-ad-client-authz-attempts/m-p/3578868#M509713</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #58585b; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 15px;"&gt;Hi all, I have a customer who uses dual SSID BYOD, the open SSID using AD creds for auth. The issue they have is that 5 x wrong password = account lockout. They are concerned that a malicious actor would be able to exploit this and they would like to have an Authz rule which prevents any more requests being sent to the DC after say 2 or 3 failures. Has anyone seen anything like this before and able to help? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #58585b; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 15px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #58585b; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 15px;"&gt;Thanks, Gareth&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 May 2018 15:56:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/limits-on-ad-client-authz-attempts/m-p/3578868#M509713</guid>
      <dc:creator>gaowen</dc:creator>
      <dc:date>2018-05-22T15:56:39Z</dc:date>
    </item>
    <item>
      <title>Re: Limits on AD Client Authz attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/limits-on-ad-client-authz-attempts/m-p/3578869#M509716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are using AD creds then the password policies should be controlled in AD environment.&lt;/P&gt;&lt;P&gt;Authorization happens after authentication so even say for eg: if we have a rule in ISE to prevent this, it will not affect authentication since your concern is multiple auth failures hitting DC.&lt;/P&gt;&lt;P&gt;ISE does’t have rules to control the behavior of AD.&lt;/P&gt;&lt;P&gt;However we do have rules for Network access user such as password policy and account lockout if you have a local user that you can take advantage of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-krishnan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 May 2018 18:11:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/limits-on-ad-client-authz-attempts/m-p/3578869#M509716</guid>
      <dc:creator>kthiruve</dc:creator>
      <dc:date>2018-05-22T18:11:54Z</dc:date>
    </item>
    <item>
      <title>Re: Limits on AD Client Authz attempts</title>
      <link>https://community.cisco.com/t5/network-access-control/limits-on-ad-client-authz-attempts/m-p/3578870#M509719</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One option is to use Client Exclusions on access device.&amp;nbsp; For example, if the endpoint fails auth X number of times in an interval, the endpoint is prevented from attempting auth again for specified period.&amp;nbsp; You can try setting the exclusion time to a value &amp;gt; than the AD lockout interval.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 May 2018 11:40:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/limits-on-ad-client-authz-attempts/m-p/3578870#M509719</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2018-05-23T11:40:27Z</dc:date>
    </item>
  </channel>
</rss>

