Any server that receives requests from clients will always be a potential target for someone to try and exploit by initiating an attack. Attacks can come in many different forms, and over time, it is important to keep a history of the originating source of the attack. So, we can monitor the behavior and patterns more closely and potentially use this data to block access as needed.
In this next recipe, you will learn how to store the source IP addresses of clients, who based on their request behavior are to be flagged as suspicious IPs.
To step through this recipe, you will need a running Splunk Enterprise server, with the sample data loaded from Chapter 1, Play Time – Getting Data In. You should be familiar with navigating the Splunk user interface.