Hello and welcome to the Splunk Enterprise Certified Administrator course on Sai Buri. So this is module to admin basics, as we mentioned before, this is gonna be a pretty high level course talking about things like, what are what is Splunk? The different components that make up ***.
I'm also going to *** architectures. So I'll be three lessons in this module.
We're gonna move ahead into lesson 2.1, which is the overview of Splunk.
And in this lesson, the plan is to make sure that you know what Splunk iss and then also the three core functions off spoke.
So why are we learning this? I think before we get into configuring and working with the tool first it's important to understand what it is and what problems it solves. Then also, when we talk about Splunk in terms of its three core capabilities, we're also gonna break that down into the three phases of
you know, and how how data moves through Splunk. And I think that's going to be very important in later lessons based on some common mistakes that I've seen in in environments as a consultant just understanding, you know, which configurations and which components are associate ID
with which function of Splunk
will help to make sure that you're placing your configurations in the right place or when you're troubleshooting that you're going to the right device. So I think that it's important to start talking about that concept early and really getting in front of mind.
So what is Splunk Just bucks a company that provides a number of software solutions, including Splunk enterprise, which is what we're talking about in this course. They also offers phantom and user behavior, analytics, enterprise Security Service intelligence and a number of other
premium maps that build onto Splunk.
But Splunk, as a software, is a machine data analysis platform. So basically what that means is, it's, uh it's a software that allows you to bring in
Boggs or data from tons of different
computer based devices and then analyze them, build your own correlations and visualizations and alerting rounded on. That's why it's called a platform because of that ability to build and grow it that you have
now as far as the words Blunk. If you are interested where I came from, it actually is from the word spelunking so imagine if you don't know its plunking is it's when you're underwater in your deep sea cave exploring. So just imagine, that's what you're doing with your dad. And that's the point of Splunk is to basically get under the surface and
really find the hidden gems in your in your data.
So before we talk about Splunk and its court capabilities, let's talk about the main pain points behind machine data because that's gonna really explain the problems that Splunk is here to solve and just makes blanc as a whole make a lot more sense. So with machine data, you're gonna run into a problem where
you have tons of devices located all over the place. They're all producing events.
And when when you have all those data sources all over the place, it's hard to do any kind of analysis. Or or Tito make anything to gain any actionable insights out of your data because it's all over the place. It's not in one location,
so that goes into the second point, which is there's no single pane of glass to see all this machine data
And what what that means. It's I know it's a bit industry jargon. So explain basically just means that there isn't one system. There is a one screen, which is what they us single pane of glass, one
one view into all of that information
and that, like I said, those two components lead to a very tedious analysis. Because if you need to investigate something, you have to go to all these different devices separately. Maybe you're using some sort of remote access like rdp, remote desktop protocol or ssh, secure shell toe
to access all these different devices, collect logs from each of them,
come back toe your own computer and do your analysis. And that's just not an effective way
to investigate this kind of stuff. And if it's a security of that, for example, and time is of the essence, then you're really gonna lose a lot of you're gonna have an ineffective response because it's gonna take so long
that leaves really well into the functions of Splunk. Because sports basically designed to address all of those problems just bunk provides you with the ability to ingest data from tons of different sources, doesn't really care about the format of the data, doesn't care How you want to bring the data in its very versatile
and then second function of sport is to store the data.
So now it's in one central repository, so that gets rid of the highly disparate data, and then it also provides you the ability to investigate or search on that data, which addresses the tedious analysis, allows you to do things much, much faster than if you had access all these devices individually.
So we're gonna break this down a little bit more in detail, and we're also going to conceptualize it a little differently so
we can think about all of those core functions as phases and basically the life cycle of slowing. So you know, you start with data ingests where you go to all these different devices and you choose the mechanism for bringing that data in. That's one gives you a lot of options. You can forward it
over a network court. You could
have a Splunk forward or installed up forwards The data for you. You could have pools against a P I.
There's that. There's a ton of different ways Splunk will allow you to bring that in and send it to itself.
So once all that data is sent from different places,
you enter the second phase, which is where slowing parses it and indexes the data,
it assigns a bunch of information about the data itself to the data. So that's what metadata is data about data so assigns things like that. Like where the where the data came from, the name of the file it came from, if its applicability all the time. You know, the things of that nature is that you could identify
the data more easily,
an index, which, in *** is really just a directory where you set some retention and per and visibility permissions which leads into parsing indexing, being part of the security aspect of Splunk. Because this is where you decide who is allowed to see which data on an index by index basis.
And also, when you're bringing the data and you conform transformations on it to massacre obvious Kate
once the data is processed and stored on disk, now, you into the third phase where you actually prefer perform searches on that data.
So here you could be an analyst, maybe with security event that just went off, and you're doing log analysis to determine more information about the event.
You could have searches that are running to detect activity from multiple different data sources that might indicate some behavior. For example, it could be a veiled log in, followed by or preceded by a intrusion detection system event,
and that might indicate that there was a compromised account.
But basically the key here is that now that you have all that data in one place, you can build higher fidelity more effective searches
by using multiple data sources. Teoh correlate versus just relying on a single of then
on that. Also, you can build your dashboards and visualizations because even though it's cliche, a picture really is worth 1000 words. And so being able to take all your data and visualize it in tow charts and graphs and tables really adds a lot mawr at action ability to the data. So
wraps up this lesson. So now we've learned what Splunk is. We know that it's a machine. Data announced this platform, and we also know that there's three core functions of Splunk, its ability to ingest data from a large number of disparate sources. Its ability, its ability to store that data in a central repository
and then the ability to allow users to interface with the data.
So that covers this lesson and we'll see you in the next one.