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
2 months agoBeth
2 months agoCrista
2 months agoJeannetta
22 days agoAntonio
30 days agoSvetlana
1 months agoBrent
1 months agoPhyliss
2 months agoCarey
2 months agoElly
2 months agoAdelaide
23 days agoRoosevelt
1 months agoDelsie
2 months ago