<?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 Syslog or Trap for Malicious APs in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4170268#M13554</link>
    <description>&lt;P&gt;Hello, we have a Cisco 5520 WLC. I'm looking into auto-containment of rogue devices found on the network or with our SSID. However I want to get an alert of when it happens. I know the WLC itself doesn't alert, but you can send syslogs and traps to a server. We have SolarWinds as a log viewer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Two questions:&lt;/P&gt;&lt;P&gt;1 - If I setup our WLC to auto contain, if it starts to auto contain an AP on the network, or with our same SSID, will it automatically clasify that AP as "malicious" and I'll be able to see it under the Monitor &amp;gt; Rogues &amp;gt; Malicious Aps section?&lt;/P&gt;&lt;P&gt;2 - What might the syslog look like if a device is being "contained" and not alert for the status? I'm able to see in our log server when a device is marked as malicious, but I would like to see when the status changes to contained. Then I can setup SolarWinds to alert me on that. I had on purpose started to contain an out of inventory AP we have for testing, and the syslog didn't show anything but malicious, but I couldn't see a status of "Contained". I could however see that in the GUI and CLI with some show commands.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would think the WLC out of the box should be able to generate an email stating when an AP is actively being contained...&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 19:40:27 GMT</pubDate>
    <dc:creator>Travis-Fleming</dc:creator>
    <dc:date>2021-07-05T19:40:27Z</dc:date>
    <item>
      <title>Syslog or Trap for Malicious APs</title>
      <link>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4170268#M13554</link>
      <description>&lt;P&gt;Hello, we have a Cisco 5520 WLC. I'm looking into auto-containment of rogue devices found on the network or with our SSID. However I want to get an alert of when it happens. I know the WLC itself doesn't alert, but you can send syslogs and traps to a server. We have SolarWinds as a log viewer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Two questions:&lt;/P&gt;&lt;P&gt;1 - If I setup our WLC to auto contain, if it starts to auto contain an AP on the network, or with our same SSID, will it automatically clasify that AP as "malicious" and I'll be able to see it under the Monitor &amp;gt; Rogues &amp;gt; Malicious Aps section?&lt;/P&gt;&lt;P&gt;2 - What might the syslog look like if a device is being "contained" and not alert for the status? I'm able to see in our log server when a device is marked as malicious, but I would like to see when the status changes to contained. Then I can setup SolarWinds to alert me on that. I had on purpose started to contain an out of inventory AP we have for testing, and the syslog didn't show anything but malicious, but I couldn't see a status of "Contained". I could however see that in the GUI and CLI with some show commands.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would think the WLC out of the box should be able to generate an email stating when an AP is actively being contained...&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 19:40:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4170268#M13554</guid>
      <dc:creator>Travis-Fleming</dc:creator>
      <dc:date>2021-07-05T19:40:27Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog or Trap for Malicious APs</title>
      <link>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171392#M13555</link>
      <description>&lt;P&gt;Auto Containment shouldn’t be used, at least in the US since 2015, check this Public Notice from the FCC &lt;A href="https://docs.fcc.gov/public/attachments/DA-15-113A1.pdf" target="_blank"&gt;https://docs.fcc.gov/public/attachments/DA-15-113A1.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2020 01:36:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171392#M13555</guid>
      <dc:creator>Grendizer</dc:creator>
      <dc:date>2020-10-22T01:36:35Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog or Trap for Malicious APs</title>
      <link>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171706#M13556</link>
      <description>Well that is silly if it’s found to be on your network? If it’s plugged into my LAN on a remote branch network I can’t even block it from what I read. Thanks for the notification.&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Oct 2020 11:51:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171706#M13556</guid>
      <dc:creator>Travis-Fleming</dc:creator>
      <dc:date>2020-10-22T11:51:54Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog or Trap for Malicious APs</title>
      <link>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171717#M13557</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- On your network&amp;nbsp; , is a bit of a dubious subject in wireless terms, this could be just out of your networking&amp;nbsp; perimeter too, such as the ice cream van arrived at your front door and broadcasting the ssid : &lt;EM&gt;&lt;FONT color="#0000FF"&gt;icecreamishere&lt;/FONT&gt;&lt;/EM&gt;.&amp;nbsp; Hence the wise&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;EM&gt;rules from the government&lt;/EM&gt; &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2020 12:07:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171717#M13557</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2020-10-22T12:07:41Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog or Trap for Malicious APs</title>
      <link>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171794#M13558</link>
      <description>&lt;P&gt;So what are some best practice Rogue Rules you guys use to let you know when there is a BYOD type scenario where someone plugs in their own AP on your corporates network? We have 20 remote sites most of which have a flexconnect setup with thin Cisco AP's.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2020 13:14:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171794#M13558</guid>
      <dc:creator>Travis-Fleming</dc:creator>
      <dc:date>2020-10-22T13:14:57Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog or Trap for Malicious APs</title>
      <link>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171931#M13559</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&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; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Check if these info-resources can be helpful :&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/112045-handling-rogue-cuwn-00.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/112045-handling-rogue-cuwn-00.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;A href="https://community.cisco.com/t5/wireless-mobility-documents/rogue-management-attack-detection-and-threat-mitigation/ta-p/3112862" target="_blank"&gt;https://community.cisco.com/t5/wireless-mobility-documents/rogue-management-attack-detection-and-threat-mitigation/ta-p/3112862&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_wl_16_10_cg/managing-rogue-devices.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_wl_16_10_cg/managing-rogue-devices.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2020 16:05:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171931#M13559</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2020-10-22T16:05:50Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog or Trap for Malicious APs</title>
      <link>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171978#M13560</link>
      <description>&lt;P&gt;Thank you that helps. One thing I'm having troubles finding anywhere is hot to auto-clasify an AP that is on my network? I can edit rogue rules on my WLC 5520 to mark AP's with a minimum RSSI, has at least 1 client, and no encryption. But really, I would like to classify it as rogue if it's on my network. I can auto-contain based on that, but how would I make a rule to auto identify them and classify them as malicious?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2020 17:22:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171978#M13560</guid>
      <dc:creator>Travis-Fleming</dc:creator>
      <dc:date>2020-10-22T17:22:23Z</dc:date>
    </item>
    <item>
      <title>Re: Syslog or Trap for Malicious APs</title>
      <link>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171981#M13561</link>
      <description>&lt;P&gt;You can configure rogue rule as below, this will "alert" you if rogues are using one of your configured enabled SSIDs&lt;BR /&gt;&amp;gt;config rogue rule add ap priority 1 classify malicious notify all state alert ManagedSSID&lt;BR /&gt;&amp;gt;config rogue rule condition ap set managed-ssid ManagedSSID&lt;BR /&gt;&amp;gt;config rogue rule enable ManagedSSID&lt;BR /&gt;You will see the new rule from SECURITY &amp;gt; Wireless Protection Policies &amp;gt; Rogue Rules&lt;BR /&gt;Other than that, with default settings of the WLC, you will get all related alerts like Rogue APs and Rogue clients and the WLC will show them in trap logs (MANAGEMENT &amp;gt; SNMP &amp;gt; Trap Logs) and if you configured "SNMP Trap Receiver" then that server will receive all traps including those as well.&lt;BR /&gt;With the above rule, you will be notified thru the Trap Logs as:&lt;BR /&gt;Classification: malicious, State: Alert, RuleClassified : Y&lt;BR /&gt;Instead of&lt;BR /&gt;Classification: unclassified, State: Alert, RuleClassified : N&lt;BR /&gt;and based on that, you can configure the trap receiver (Prime Infrastructure or in your case SolarWinds) to send you emails as alert&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2020 17:23:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/syslog-or-trap-for-malicious-aps/m-p/4171981#M13561</guid>
      <dc:creator>Grendizer</dc:creator>
      <dc:date>2020-10-22T17:23:34Z</dc:date>
    </item>
  </channel>
</rss>

