<?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 Wi-Fi Access Security in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wi-fi-access-security/m-p/2071532#M12349</link>
    <description>&lt;P&gt;We have installed a working Wi-Fi solution running on a 5508 controller, software ver 7.2.110.0 with 15 AIR LAP 1142 AP’s.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The RADIUS authentication is backed off to a Win 2008 R2 server running NPS. The “Connection Request Policy” is configured to look at NAS port Type “Wireless or Wireless IEEE 802.11” and the Authentication Provider is “Local Computer”. The Network Policy again looks for “Wireless or Wireless IEEE 802.11” and the AD group “Domain Users”&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above solution is working just fine and the users are happly connecting, the problem that I am experiencing is that people have started to connect their own personal devices to our wireless network using their Domain account details, what I need to do is prevent this from happening can anyone suggest a way to deal with this issue? I was thinking about using certificates?&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 05:59:17 GMT</pubDate>
    <dc:creator>Murray Bown</dc:creator>
    <dc:date>2021-07-04T05:59:17Z</dc:date>
    <item>
      <title>Wi-Fi Access Security</title>
      <link>https://community.cisco.com/t5/wireless/wi-fi-access-security/m-p/2071532#M12349</link>
      <description>&lt;P&gt;We have installed a working Wi-Fi solution running on a 5508 controller, software ver 7.2.110.0 with 15 AIR LAP 1142 AP’s.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The RADIUS authentication is backed off to a Win 2008 R2 server running NPS. The “Connection Request Policy” is configured to look at NAS port Type “Wireless or Wireless IEEE 802.11” and the Authentication Provider is “Local Computer”. The Network Policy again looks for “Wireless or Wireless IEEE 802.11” and the AD group “Domain Users”&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above solution is working just fine and the users are happly connecting, the problem that I am experiencing is that people have started to connect their own personal devices to our wireless network using their Domain account details, what I need to do is prevent this from happening can anyone suggest a way to deal with this issue? I was thinking about using certificates?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 05:59:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wi-fi-access-security/m-p/2071532#M12349</guid>
      <dc:creator>Murray Bown</dc:creator>
      <dc:date>2021-07-04T05:59:17Z</dc:date>
    </item>
    <item>
      <title>Re: Wi-Fi Access Security</title>
      <link>https://community.cisco.com/t5/wireless/wi-fi-access-security/m-p/2071533#M12350</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yea you have a few options ..&lt;BR /&gt;&lt;BR /&gt;Mac filtering .. But I wouldn't recommend it because its labor intensive to manage and easily to work around&lt;BR /&gt;&lt;BR /&gt;ISE .. Expensive, but can ID a corp asset vs a personal asset and apply rules based on such&lt;BR /&gt;&lt;BR /&gt;EAP-TLS .. Would require additional knowledge as this is the more complex of the Eaps. Also a Pki would be helpful to manage the Certs.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Nov 2012 12:30:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wi-fi-access-security/m-p/2071533#M12350</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2012-11-06T12:30:52Z</dc:date>
    </item>
  </channel>
</rss>

