In this post, I'm going to veer away from the network security side of Splunk and more on the network operations side of things by introducing the Cisco Networks Splunk app. This app will gather syslog and Call Home data from various network devices in the network and visualize it in some rather interesting ways. 

In this blog post, I'll be going over aggregating all of the various security addons for Splunk into the Cisco Security Suite. This will a very short port since most of the work has already been done in our previous Spunk posts. 

In this blog post, I will be detailing how I added WSA logs to my Splunk instance. There's a few ways you can do this but I'm doing to be uploading the logs to Splunk via FTP. You can also utilize SCP but I chose not to go that route. 

In this blog post, I'll be writing about adding Firepower logs to Splunk. With Firepower, we will utilize the built in eStreamer to send this data securely to our Splunk server.

This post is going to be a bit different. I'm configuring Splunk in my lab currently for reporting and as I go through it, I'm going to detail my configurations here. I am going to use Splunk to aggregate my ISE logs to it. In order to do so, we're going to have to install the Spunk for Identity Services (ISE) app onto Splunk. Before starting, please download the app

I'm currently adding Splunk to my lab so as I'm going through the configuraitons, I'm going to list out what I do here as a series of blog posts. Splunk is a pretty power SIEM that works to aggregate and correlate data across your network and security tools. If you ever wanted to try it out for free, go to splunk.com and you should be able to download it for free for use up to a certain point. The nice thing about Splunk is that there are tons of free pre-built apps and dashboards for multiple vendors which you can download