BIG-IP AFM Blacklisting Magic
Have you ever wondered which IP addresses floating around out there on the Internet are the good ones? The benign ones? The malicious ones? You get the idea. Peter Silva recently published an article that discusses the IP Intelligence feature of the BIG-IP where each IP address is examined and an intelligent decision is made about how good or bad the address is. As the BIG-IP compiles all the data from the IP Intelligence feeds, it can automatically add IP addresses to one or more Blacklist categories for a specified period of time. Blacklist(noun) : a list of items (usernames, IP addresses, etc) that are denied access to a system It’s nice to know that you don’t have to manually add all the Blacklist IP addresses any more. However, you certainly still have the flexibility to add items to a Blacklist category if you’d like. To view the Blacklist category names on the BIG-IP AFM, navigate to Security >> Network Firewall >> IP Intelligence >> Black List Categories and you will see the default categories listed there. The BIG-IP AFM comes preloaded with several Black List categories (i.e. botnets, phishing, spam_sources, etc). Check out the screenshot below for a view of the Black List category page. In addition to the categories already loaded on the BIG-IP, you can create your own categories as well. To do this, simply click the “Create” button on the upper/right portion of the Black List Category page, and you can create a name, description, and Match Type (Source, Destination, or Both) for your category. These categories are important when creating IP Intelligence policies because, when you create an IP Intelligence policy, you can specify what action to take on an IP address from a particular feed list when it matches an IP address in one of your Black List categories. See the screenshot below for details on creating a new Black List Category. Now that you have a new Black List category, it will show up in the full listing of Black List categories. Notice in the screenshot below that my newly created Black List Category is listed. While the BIG-IP AFM will take care of automatically adding bad IP addresses to the various Black List Categories, you can still manually add IP addresses and assign them to a Black List Category as well. To do this, you navigate to the Black List Category page and type in the IP address in top portion of the page and select a Black List Category from the dropdown menu. Finally, you specify (in seconds) the amount of time the IP address should stay in that particular Black List category. See the screenshot below for details: Auto-Shun in Version 12.0 In BIG-IP version 12.0, the "auto-shun" feature was introduced. It allows you to configure a DoS protection profile to watch for a Source IP address and, if it exceeds the detection threshold for a given period of time, it is automatically added to a Blacklist category for a configurable period of time. See the chart below for more details: Many organizations struggle with maintaining a good and timely list of bad IP addresses, but now you have the power of the BIG-IP AFM that can do it all for you automatically!1.6KViews1like5CommentsIP-Intelligence Manual Additions and Bad Actor Additions Not Working
Greetings dev central community, I have come to impasses in two goals on a 15.1.0.5 VE running in esxi related to IP-Intelligence configuration and I would very much appreciate direction for resolution. Impasse 1: Having my manually added IP address be respected by the IP-Intelligence policy.Though pre-existing blacklisted sources are dropped with my configuration, my manually added IP addresses added via are not respected. I'm adding the IP addresses to my categories configured for drop in my IP-Intelligence policy via Security ›› Network Firewall : IP Intelligence : Blacklist Categories >> Add to Category. I've tried with public and private IP's. I've tried with pre-existing and custom blacklist categories. My license is valid. iprep_lookup from the CLI shows no verdict/category for the manually added IP's. Where as the GUI "Check Entry" button shows the IP address as present in the blacklisted category. Impasse 2: DoS blacklisting via Bad Actor Detection is not updating the blacklist category with the offending IP address. My tests have been done via Device DoS Protection via ICMPv4 flooding. I can see the attack vector being rate limited in DoS logs. My settings to add to the bad actor to the blacklist category are set low (Sustained Attack Detection Time of 10 seconds). Even if my test source attacks for a prolonged period of time and is mitigated for this prologed period of time, the address never shows up in the blacklist category specified. I have tried custom categories as well as the pre-made denial-of-service category. I have selected to advertise externally and I have BGP setup to redistribute kernel. Regardless, the IP address that should be shunned does not show up in the routing table as a local blackholed kernel route nor does it show up in the upstream BGP peer as a blackholed route. Manually configured blackholed routes are propogated properly via redistribute kernel. GUI "Check Entry" button does not show the IP address as present in the specified bad actor specified category. I have tried triggering the attack vector/bad actor protection private IP's as well as spoofed public IP's. list security dos device-config dos-device-vector icmpv4-flood allow-advertisement enabled allow-upstream-scrubbing disabled attacked-dst disabled auto-blacklisting enabled auto-scrubbing disabled auto-threshold disabled bad-actor enabled blacklist-category denial_of_service blacklist-detection-seconds 10 blacklist-duration 14400 ceiling 200000 default-internal-rate-limit 100000 detection-threshold-percent 500 detection-threshold-pps 10000 enforce enabled floor 100 multiplier-mitigation-percentage 300 packet-types none per-dst-ip-detection-pps infinite per-dst-ip-limit-pps infinite per-source-ip-detection-pps 1000 per-source-ip-limit-pps 10000 scrubbing-category attacked_ips scrubbing-detection-seconds 10 scrubbing-duration 900 simulate-auto-threshold disabled state mitigate suspicious false threshold-mode manual-multiplier-mitigation valid-domains none604Views1like0Comments