04-10-2014 07:19 AM - edited 03-10-2019 06:10 AM
I have an ASA5540X firewall with the internal (software based) IPS module. The module has the up-to-date signatures and seems to be running correctly. However, after enabling anomaly detection (ad0), and specifying the internal zones, I don't see any "Learned OS" in IME
My settings are pretty basic for the sensor
access-list ips_traffic extended permit ip any any
access-list ips_traffic extended permit udp any any
class-map ips_class
match access-list ips_traffic
policy-map global_policy
class ips_class
ips inline fail-open
not sure why it isn't learning the OSs
Solved! Go to Solution.
04-10-2014 10:56 PM
Learned OS maps—OS maps observed by the sensor through the fingerprinting of TCP packets with the SYN control bit set. Learned OS maps are local to the virtual sensor that sees the traffic.
can you verify the OS finger printing from
sensor# show os-identification learned
Enable passive-traffic-analysis {enabled | disabled}
04-10-2014 10:56 PM
Learned OS maps—OS maps observed by the sensor through the fingerprinting of TCP packets with the SYN control bit set. Learned OS maps are local to the virtual sensor that sees the traffic.
can you verify the OS finger printing from
sensor# show os-identification learned
Enable passive-traffic-analysis {enabled | disabled}
04-11-2014 07:19 AM
I realized that the problem was a failover issue--the ASAs are in a pair, and after a failover, the IPS policies had been applied to the wrong (failover) IPS module. Once I applied them on the correct module, I could see all the learned OSs.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide