<?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 Selective rogue auto-containment in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5142046#M273346</link>
    <description>&lt;P&gt;9800-40, 17.12.3, 1000 AP, 4 sites&lt;/P&gt;
&lt;P&gt;I would like all APs to detect rogues but only a subset of them to perform a rogue containment. For example one site is more open and public so we are not alowed to contain rogues while another one is closed and private and the containment can be performed..&lt;/P&gt;
&lt;P&gt;The only thing I can is to disable rogue detection in a AP join. I would like to keep detection but not contain.&lt;/P&gt;
&lt;P&gt;Is there any way to do it?&lt;/P&gt;
&lt;P&gt;Mirek&lt;/P&gt;</description>
    <pubDate>Tue, 09 Jul 2024 11:03:57 GMT</pubDate>
    <dc:creator>Mirek_Tichy</dc:creator>
    <dc:date>2024-07-09T11:03:57Z</dc:date>
    <item>
      <title>Selective rogue auto-containment</title>
      <link>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5142046#M273346</link>
      <description>&lt;P&gt;9800-40, 17.12.3, 1000 AP, 4 sites&lt;/P&gt;
&lt;P&gt;I would like all APs to detect rogues but only a subset of them to perform a rogue containment. For example one site is more open and public so we are not alowed to contain rogues while another one is closed and private and the containment can be performed..&lt;/P&gt;
&lt;P&gt;The only thing I can is to disable rogue detection in a AP join. I would like to keep detection but not contain.&lt;/P&gt;
&lt;P&gt;Is there any way to do it?&lt;/P&gt;
&lt;P&gt;Mirek&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jul 2024 11:03:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5142046#M273346</guid>
      <dc:creator>Mirek_Tichy</dc:creator>
      <dc:date>2024-07-09T11:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: Selective rogue auto-containment</title>
      <link>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5142153#M273356</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - FYI :&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_wl_16_10_cg/rogue-per-ap.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_wl_16_10_cg/rogue-per-ap.html&lt;/A&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&amp;gt;..&lt;EM&gt;.Rogue detection is configured &lt;U&gt;&lt;STRONG&gt;per AP&lt;/STRONG&gt;&lt;/U&gt; or for a &lt;U&gt;&lt;STRONG&gt;group of APs&lt;/STRONG&gt;&lt;/U&gt;. The rogue AP detection is configured under the AP profile. The&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;rogue AP detection configuration enabled by default and is part of the default AP profile.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;FONT color="#008000"&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Check the entire document too ,&amp;nbsp;&amp;nbsp;&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;M.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jul 2024 13:16:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5142153#M273356</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-07-09T13:16:14Z</dc:date>
    </item>
    <item>
      <title>Re: Selective rogue auto-containment</title>
      <link>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5142415#M273381</link>
      <description>&lt;P&gt;Be careful with containment! There are large fines if used incorrectly:&amp;nbsp;&lt;A href="https://edition.cnn.com/2014/10/03/travel/marriott-fcc-wi-fi-fine/index.html" target="_blank"&gt;https://edition.cnn.com/2014/10/03/travel/marriott-fcc-wi-fi-fine/index.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You want to make sure the rogue is within your network and an actual threat not someones hotspot or neighbouring companies wireless networks.&lt;/P&gt;&lt;P&gt;The other thing is it will tax your AP whilst containing it.&lt;/P&gt;&lt;P&gt;Catalyst Centre has a really nice rogue rule set that enables you to filter the rogues and also do things like create the rules in an easy GUI format&lt;/P&gt;&lt;P&gt;I would recommend only containing rogues where they are honey pots (using your SSIDs) or a rogue on the wire:&lt;BR /&gt;Rogue on wire:&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;A "Rogue AP on wire" is an unauthorised access point that is physically connected to the wired network infrastructure without authorization or approval. This type of rogue access point is particularly concerning because it can be used to bypass security controls and provide an attacker with a direct connection to the wired network.&lt;/SPAN&gt;&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;&lt;SPAN&gt;A rogue AP on wire can be intentionally or accidentally connected to the wired network by an employee, contractor, or malicious actor. Once connected, the rogue AP can provide unauthorised wireless access to the network, potentially allowing an attacker to compromise sensitive data or resources.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Honeypot:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;A rogue access point (AP) that mimics a legitimate AP in order to intercept and manipulate network traffic.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Tue, 09 Jul 2024 22:55:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5142415#M273381</guid>
      <dc:creator>Haydn Andrews</dc:creator>
      <dc:date>2024-07-09T22:55:14Z</dc:date>
    </item>
    <item>
      <title>Re: Selective rogue auto-containment</title>
      <link>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5143675#M273456</link>
      <description>&lt;P&gt;Thanks Haydn, it's clear. It is just the reason why we want to do it selectively strictly in closed company offices. But want to keep monitoring other areas.&lt;/P&gt;
&lt;P&gt;Mirek&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2024 14:39:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5143675#M273456</guid>
      <dc:creator>Mirek_Tichy</dc:creator>
      <dc:date>2024-07-11T14:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: Selective rogue auto-containment</title>
      <link>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5143963#M273458</link>
      <description>&lt;P&gt;THX, but my original question was: "How to configure a subset of APs to &lt;STRONG&gt;keep rogue detection&lt;/STRONG&gt; but not participate in the autocontainment"&lt;/P&gt;
&lt;P&gt;MiTi&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jul 2024 07:10:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/selective-rogue-auto-containment/m-p/5143963#M273458</guid>
      <dc:creator>Mirek_Tichy</dc:creator>
      <dc:date>2024-07-12T07:10:29Z</dc:date>
    </item>
  </channel>
</rss>

