Network Input Lab
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
Hello and welcome back to the Splunk Enterprise Certified Administrator course on Sai Buri. In this video, we're gonna be doing a lab where we set up a
UDP or network input for Splunk and just test to see how we can get some logs coming in over that medium. So it's gonna consist of basically setting up this input through an apple send out through the deployment server. And then we will set up a cyst log server too
forward some data to that network port that were listening on and then just validate that we're getting that data by looking in slug,
so we'll get started by first creating our input, so we'll head over to the command line. But I clear this down here,
get over to our search head because this is where we make our deployment. APS has acknowledged deployment server as well, so we'll just see what's in here currently.
And we're gonna make a new directory and it's gonna have a subdirectory swimming that slash p
and we're going to make this indexer sis, log in foot
to a fault
that well made
our input stock competition February soon.
So we're gonna do UDP
on. We're gonna dio generally 5 14 is this long But I think that this server already has RCIs log running so Splunk won't be able to use that port. So we'll just do 95 14
and will set save all these false. I don't We don't really need that. But I'm gonna put anyways send it to Windows because we're gonna send some windows data off of my host machine right here.
We'll set source equal Teoh Beauty P 95 14 and source type people The window of a dog.
Uh, well put colon
cisl or something like that.
So that should be everything that we need
for that. Well, actually, we could do
connection Host would be the one other thing. So this will be
basically how it uses, um, whether uses i p address or host name where? I mean, DNS, I guess in this case is the actual attribute value You would give it to determine where the status coming from. Uh,
I think because I have a DNS record, I don't know for certain that it will be able to convert my i p address, so I'm just going to be
and Now we'll make a server class to push this to our indexer.
the index slaw
add the at first cause we're gonna set it up so it restarts Splunk so that the setting actually takes effect.
And now we will add our client.
So just okay, I d x star check preview check marks. All good save.
So now that app should get sent out and spoon should start restarting.
And basically, what will be looking for on this indexer is to make sure that Splunk listening. So I have a command that I've
so also obviously, I've already done this, but you need to add
fire reports that your box is actually listening on. Then this Net stat command will show you which ports were listening on and you can see Splunk D is listening on 95 14. So if we send data, we should be able to see it.
Something that's kind of nice to Dio as well is if you run
that's CCP dump. You might have to install that if you haven't already on and you can specify port 5 15 and this is just some information to increase the verbosity and actually see the contents of the load coming through. But this will watch. I'm going to switch to report that we're using nine.
So now I'm listening on this box. So if anything comes in, I'll see the log pop up here. So basically, why I like to do this is because it eliminates one of the areas where you could have a problem. So basically, if I Ford a log to this box and it doesn't show up in Splunk
But it shows up here, I know that it's not a networking problem. It's more than likely a Splunk listening problem.
But because we already have this here, it's most likely this should work. But we'll see. So we're gonna go back to my actual box and right here on this device, I just happen to have solar winds installed so I can use this. This is CIS load client, so I can use this to monitor certain data forwarded to Splunk.
Right now, I have the application log in the system long being monitored because our UFO sorry, monitoring the security log.
So we just have to add a destination here. So
I'm gonna cancel out of that 1st 2nd get my i p address
and then I'll rerun that,
and we'll set that to the proper i p address and the port and we're listening on u dp. So we want to keep it is UDP
and will create. Um, we could sit here and wait for an actual log to occur, but I'm just going to generate a text message,
um, or a test
message so that we have
data for sure. I'll do a couple
and you could see that there popping up here warning error
so you could see that our box is receiving these logs, Which makes sense. So now it's just a matter of checking Splunk to see
the data is working from an input perspective.
And you can see
this is coming from the i P address, and we set that connection host information to i. P. And here are the logs. We can see that it's from application, which is what we sent the test log from. So that makes sense has so you can tell that our network input is working.
Um, if that didn't work again, like I said already this these are a couple steps to just check if your network
input was set up properly. You see Splunk lis actively listening on that port If you use nets step.
If you don't have that set installed, you can install it pretty easily. If you're on Santos with yum install,
I believe Net tools Net hyphen tools, I think is the package that this comes in so pretty easy for you. Get that TCP dump is another command line tool that might not be there by default. But you can very easily download that as well. And so
uh, yeah, those are the two areas where this might get messed up. Either Splunk won't be listening or there will be a networking problem and the data isn't getting through,
yes, So those are two places you want to focus on your troubleshooting If your input doesn't work now, just for your awareness as well. If you're setting up assist log sis, log input in your Splunk deployment.
Don't do it this way. I only did this this way for the demonstration off, setting up a network input.
But in real in the real world, you what you would want to do is probably send your sis log to sis log servers, ideally at least two and have them load balanced just to give you some high availability. Some Well, a little more data. Resiliency. And then on those specs,
sis log servers. You could put on a Splunk U F or a split heavy foreigner and basically have the systolic servers right. These events to disk and then have Splunk read them from disk.
This is a lot better because you can load balance that files are written to disk versus just being sent over the wire and then possibly lost. And also, when you use a system like server to write to disk, you can use some rejects based rules toe break the data out into individual directories,
and then that makes setting up your file monitor inputs much easier and also much
more granular so that you don't have to do a bunch of complicated ri routes and stuff to get your data.
You know, metadata on your data assigned properly, So that's just something to keep in mind. But that is it for this lab. This is a pretty simple one. You could make any number of changes to this if you want into. So for example, you could have specified this,
in this format.
I'd be address slash post name 95 14 to specify only a single host. You can also write it like this, and that would work.
But I think this is the most straightforward. So that's how I write it. Obviously, there's a lot more attributes you could configure, but this is at least at a high level how you set it up.
If you want to get more into the weeds on this, you can check the documentation for
on. Just go through the section on monitors, which
TCP or UDP, so you can see whatever list of attributes and
options for configuring this. You won and get as granular as you want, but this wraps it up for this lab. So we'll see you in the next one
Scripted Input Lab
HTTP Event Collector Lab
Windows Input Lab
Props and Transforms