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
5 months agoBeth
5 months agoCrista
5 months agoJeannetta
4 months agoAntonio
5 months agoSvetlana
5 months agoBrent
5 months agoPhyliss
5 months agoCarey
5 months agoElly
5 months agoAdelaide
4 months agoRoosevelt
5 months agoDelsie
6 months ago