Option A is interesting, but I'm not sure how the HTTP User-Agent strings would be relevant for profiling devices on the Aruba Mobility Controller. Seems like a bit of a stretch.
D) You want the MC to analyze wireless clients' traffic at a lower level, so that the ArubaOS firewall can control Web traffic based on the destination URL.
C and D both seem like valid options for controlling traffic at a lower level. I'm not sure which one would be more appropriate for the Aruba Mobility Controller specifically.
Option B seems like the most logical choice. If the security team suspects an attack, a packet capture would be the best way to investigate the traffic and identify the issue.
Glendora
8 months agoBeth
8 months agoCrista
8 months agoJeannetta
7 months agoAntonio
7 months agoSvetlana
7 months agoBrent
7 months agoPhyliss
8 months agoCarey
8 months agoElly
8 months agoAdelaide
7 months agoRoosevelt
7 months agoDelsie
8 months ago