AP Containment

Answered Question
Jan 22nd, 2009

Need Clarification

Can the AP containment feature on

CUWN 4.2 be automated to contain rogue APs that are advertising your SSID or is this a manual procedure.

Can the new Cisco mobilty service engine IDS/IPS system do this automatically?

Can Air defense / Air tight / Air Magnet do this?

Mark

I have this problem too.
0 votes
Correct Answer by Leo Laohoo about 7 years 10 months ago

If this resolves your post, can you tick "resolved"? Thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.3 (4 ratings)
Loading.
Leo Laohoo Mon, 01/26/2009 - 17:36

Containment of Rogue AP can only be done manually. Auto Containment of "Rogue on Wire" and/or "AdHoc Rogue AP", on the other hand, is turned off by default. To enable this feature, go to Security -> Wireless Protection Policies -> Rogue Policies -> General.

Does this help?

mark.cronin Wed, 01/28/2009 - 12:05

Yes this does help, but I am more concerned with our wireless clients trying to connect to

a rogue AP advertising our SSID, the rogue may or may not be wired in to our LAN. My thoughts are that to rely on manual AP containment is slightly risky as it requires a member of the support staff to look at the WCS logging.

My hopes are that the new Cisco mobility services IDS/IPS offering will automate this.

Thanks for you answers

Mark

Leo Laohoo Thu, 01/29/2009 - 13:14

If you are concerned about clients connecting to a Rogue AP with the same SSID (aka "Honeypot"), the WLC/WCS will flag this alarm.

One of the logic why this is not incorporated into the automation is the risk associated that "somebody" in the organization may have innocently setup their very-own AP for company use without telling everyone. There's also a risk of your organization if the WLC/WCS will attack legitimate AP it considers as "Rogue".

True, IPS/IDS will do the trick, but I've been doing this for the past 2 years and I'd rather be the one to throw the switch for the WLC/WCS to contain a possible Rogue AP than let the machine do it for you.

For instance, I saw a a firmware bug where an AP was flagged by the WLC and the WCS as a suspected Honeypot. Upon closer inspection, the so-called Honeypot is an AP register to the same WLC and therefore legitimate.

In my humble opinion ...

mark.cronin Thu, 01/29/2009 - 13:20

looks like I need to convince the support staff to look at the logs

Correct Answer
Leo Laohoo Tue, 02/03/2009 - 16:50

If this resolves your post, can you tick "resolved"? Thanks.

Actions

This Discussion

 

 

Trending Topics - Security & Network