Occasionally, I notice that the firewall has been blocking tens or even hundreds of attempts from a single source address for multiple threats. In a case like this, it seems obvious, for someone looking at the logs, that that source IP should have been temporarily blocked and possibly banned, but that does not happen automatically.
We do have some exception in our vulnerability profile that change the action from reset to block-IP, for instance, but this only applies to a specific TID. When you have a host combining say 5 or 10 different exploits in one minute, is there a way to configure the firewall to automatically block the offending IP?
Solved! Go to Solution.
I've cloned syslogMiner node in MineMeld, and added (rigth after our Splunk server) the MMeld server to the syslog profile, port UDP 13514. It seems that the new node is not receiving any data. Also attempted creating a separate syslog server profile.
I've been following instructions contained in this doc:
This now more and more belongs into the minemeld forum;)
You also configured the local firewall (iptables) to allow this traffic and if needed edited the rsyslog.conf file?
Sounds like something similar as in this topic: https://live.paloaltonetworks.com/t5/MineMeld-Discussions/MineMeld-need-help-importing-and-processin...
I agree. I'll post this in the MineMeld forum, if needed. I'd like to thank you and BPry for your help thus far.
edit: the port was already opened on the ubuntu server, but it's using port TCP 13514, not UDP 13514. :-)
TCP clearly shows in the doc I linked, I simply missed that.
@vsys_remo could you please explain how the following can be implemented:
"In PAN-OS 8 you could tag attacking IPs based on specific filters (for example when a critical vulnerability was blocked or even one specific vulnerability). With this tag you are then able to create a dynamic addressgroup and use this group in your policy to drop connections from there completely. "
Anyone know how to tag attacking IPs based on specific filters (for example when a critical vulnerability was blocked or even one specific vulnerability). With this tag you are then able to create a dynamic addressgroup and use this group in your policy to drop connections from there completely.
You need to start with a log forwarding profile, there you define a specific filter for the threatlogs (you either filter on the severity or on specific threat ID or something completely different). As action you then choose to tag the source or destination IP (depending on your filter) and assign a Tag to these IPs. After that you create a dynamic address group with the criteria the tag you created for that. From this point you can use the address group in your policy to block connections from or to these IPs.
Hope this helps.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!