Can we re-run a URL blocklist against logged traffic?
That is, now that I have updated my URL blocklist, I want to go back through the log and ban any IP that would have been banned by the current list.
Why? Because someone at that IP has proven that they are malicious and intent on intruding on one of my sites. If they come back, I don’t want them probing again with some new trick. I don’t want them on Any of my sites. So I want to Pro-actively ban them, rather than waiting for them to hit the site again so that I can Maybe Re-actively ban them if they try some activity that I’ve already identified.
Imagine a world where the Hub allows us to update a URL blocklist for all sites, like we can with IP addresses. And with a single button click we can trigger all sites to process the current common list in addition to their own individual lists, banning IPs from all sites that tried to abuse any of our sites.
As always, if Defender and the Hub don’t already do this, please just point me to the function that needs to be called to ban an IP. I’ll run a cron process, look at the logs myself, run prior visitors through my new lists, and – with the provided function – ban the IP.
Or I’ll just do this outside of Defender and let fail2ban handle it.
What are the options for this?
Thanks!