4.3 Server Configuration Demo Part 3
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
3 hours 10 minutes
we'll write. Our three servers have come back up
so we can continue one with her configuration.
I running Sudo has so sad up again that beginning password.
so look at the first screen will be the same.
But we get the message. Looks like etc. Network in two races have has already been configured by the script. Would you liketo skip network configuration? Yes, we want to skip it.
this case, we want to do production mode and we want to do the manager first. So production mode means that
will be potentially using it in production. This is difference than the stand alone mode, like we did earlier because that was evaluation mode.
this case will be doing more than one server.
And since we're configuring the master note first we want to say new.
All right, first user account,
just put my name in there
All right. So here we can customize our deployment, or we can use best practices. I'm happy using best practices.
All right, So what ideas for rule said, Do we want to use?
There are a couple of options we can do emerging threats open pro, uh, or smart or two? Subscriber. Talos rule set.
Ah, since I do not have any bank codes will just use emerging threats open, which should work just fine for us.
And we do want to use the snort i D. S engine. In this instance,
you can also use terra cotta, if you would like.
I know that there are a lot of people who really enjoy using Sarah Cottle over snort. It's just
matter of preference and what you're comfortable with.
Oh, right. So do we want to enable network censor service is
on the manager. That means do we want to sniff the traffic that is hitting
our network? Are we're manager in this case, we do not,
we we won't be throwing any traffic at it. And
just for, uh, performance purposes I'd recommend, and they would recommend as well disabling that.
All right, do we want to store logs locally? We are set going to set up our S O storage node so we don't need to store anything on the manager, so, no, I will lad storage notes for load balancing.
Okay, so we're about to do these things, said the OS Time Zone to UTC. Delete any existing SM data configuration. That's fine. Create a squeal database there. Squeal Server named
Security Onion. We're adding the user account for Carl.
We're downloading the emerging threats, open rule sets, configuring elastic stack
and we will load balance two additional storage nodes.
And so, yes, we want to proceed with changes,
and this one could potentially take a couple of minutes.
Well, that's running. Let's get going on our forward node.
All right? Same start screen.
We do not need to reconfigure the network settings
we want to do production mode.
Now, this time we want to select existing because we will be connecting eso forward to S o master.
So right here it's asking for either a host name or an I p address of the master server.
Um, typically, it'll be best practice to put in your
fully qualified domain name for your master server.
Since I don't really trust my home d n a server to have s o master and they're properly I'm just going to use the I P address,
It's It's a good idea to use the
host named because the host name is less likely to change them. The i P address.
if you'll recall the first thing that we did when we were setting up or when we were prepping to do this demo was we set up a couple of user names on the master server.
So we want to put in this
user name that we set up in this case it was
here is asking, What kind of note will this be?
This one has forward in the name. So we will say forward server.
And once again, we'll be using best practices.
What would we like to set RPF? Minimum number of slots too.
The default is 4096 4 busy networks. You might want to increase it to a higher number.
How? This will not be a very busy network. So default is fine.
And we want to monitor these two sniffing interfaces nine and 10.
So this is a configuration that will go into snort. It will define what our home network is.
Ah, right now, the I P addresses in here are the RFC 1918 private.
Uh, I p address ranges.
Um, if you have if your organization or if you have ah, I p address range that you own and you use on internal i p addresses. Then by all means, put those in here.
the faults are fine for us here.
All right, so that is everything. Here, we're setting time zone to a UTC deleting old configuration monitoring these two
configuring the sensors to report to the manager.
we're running a single ideas engine process per interface.
Single bro crosses per interface.
Now, the more cores that you have dedicated to your server,
the more instances you'll be able to devote per interface.
You have 32 cores on your
server, then you'll have a lot more ideas. And bro process is running. This is a fairly simple deployment, so we only have four cores going. So
So all we need here,
then configuring our home net and disabling elastic stack because the Ford nodes, if you'll recall from our architecture discussion, discussion,
we do not have elastic stack running, So you want to proceed with the changes there?
so we have s o storage.
You want to get that going so right here we have a terminal pop up asking us to approve
authenticity of that server.
And now we want to put in the
password that we set up for. Our forward child user
may have typed it in and correctly the first time.
All right, let's get going on storage mode.
Yes. Skip Network configuration
that storage child.
In this case, we're doing this storage node
as we can see up here, there's a quick explanation of the different server types. The Ford Nodes generate and collect logs and forward them to the master server.
The full pack capture remains on the forward nodes. Do not run in the elastic stack processes.
I really miss about passwords that bad.
we will talk about that window in a second.
So forward notes required less hardware than heavy nose, but typically use more network bandwidth. So that's
you can understand that
So middle one here is our heavy note architecture. Er
thes to terminal sessions are very meaty,
heavy nose generate and collect logs and store them locally heavy nodes to rent elasticsearch and log stash. A master, Sir Herbert queries heavy nodes by a cross cut Lester search and heavy no, to require more hardware than forward notes, but typically use less network bandwidth. So
the heavy note architecture is one that is not really recommended that we use anymore just because everything is running on this one server, so it has to dedicate more resource is,
uh, cross more processes.
the third note here that we're
deploying now is the storage node. They do not generate logs themselves. So thus we do not have any sniffing interfaces here, but they simply extend the storage of the master server.
And they do require that the master server has already been configured to load balance
toe additional storage nodes. Okay, So if we have multiple storage notes than the manager rule, load balance between them
and storage notes do run elasticsearch and log stash and the master crazed Mr Orange nodes by across cluster search.
So when you were actually deploying that you can read all of that yourself and research it to your heart's content.
All right, so how much discs based we want to devote to elasticsearch? We'll just use the default of nine.
You have a 20 gig hard drive on this server. So
nine is just under half.
Okay, so we're setting the always time zone to UTC deleting any existing configurations and confessed configure as elastic storage. Knowed All right? Yes. We want to continue.
Okay, so we have a master will say OK,
it's now complete.
You can check on our running service's with eso stats.
Yes. We want to prove this server.
Yes. We want to put in the password correctly. The first time
rule was added. Apparently I could type this time.
So little bit of info. One s o stat.
We have a bit of information on our rules location of the rules, where we can add rules, modify rules, how to update rules, things like that.
Bit of information about the firewall, how we can
rules to the firewall to allow further access. Something that we will need to do if we want to connect over the browser.
Okay, but if information on where to find war information,
we want more training, security on in solutions dot Net
and we are all done.
So that is
that is how you configure distributed environment. Basically, if you want to add any more forward nodes or
storage knows you just run through this process again with new servers and
have them to your configuration.
Don't need toe show you clicking through these again so
we can call it good on this video. Thanks for watching
in this lesson. We had a brief discussion on the architecture of a distributed environment. We reviewed the installation and set up process. We looked at the tools that I used to make this demo work, and we had a demonstration on how to configure a distributed security onion architecture.
In our next lesson, we will take a look at what we installed on our standalone instance, CNN.