Time
3 hours 10 minutes
Difficulty
Beginner
CEU/CPE
3

Video Transcription

00:01
all right now to talk about deployment types.
00:04
Stand alone instances are single server architectures where all service is our run that on that one server.
00:11
Now these aren't really recommended for enterprise use outside of a proof of concept or POC, as it's storing and processing, that much data will likely break any server used.
00:22
Instead, single server architectures are used as forensics boxes or are used on lower bandwidth networks. Mike at home
00:31
for enterprise use and monitoring, you'll want to use a distributed environment. There are three server types, the manager forward notes and storage nodes.
00:41
Now the manager oversees the rest of the deployment and is usedto view logs by the end by the end analyst. It runs elasticsearch and log stash, as well as gathers logs from the I. D. S.
00:53
Afford notes do not run elastic stack components but are instead used for gathering and storing network traffic, as well as running them through the I. D. S.
01:03
They forward logs to log stash on the manager for storage and display.
01:08
By doing this, you are freeing up the Ford Note process and store the network traffic.
01:14
It also makes elastic set elasticsearch quicker on the manager and on the storage nodes, as it isn't competing with I. D. S or other service is for resource is
01:23
now storage notes are running elastic stack components and are used by the manager to store lock stash logs.
01:30
These logs are query through the use of cross cluster search.
01:34
Now this architecture allows you to devote servers two tasks instead of having them compete on one server like you'd see on a heavy architecture, which is what we will look at now.
01:46
So heavy architectures aren't really recommended for enterprise use for performance reasons as we touched on a bit before.
01:55
But as a heavy architecture can be cheaper as attends to need fewer servers, servers will still talk about it.
02:02
Now there are two server types with a heavy deployment. The manager and the heavy node.
02:07
Both are running elastic components. Resource is on the heavy note are split between gathering and parsing network logs and storing elastic logs, which are then queried by the manager by across cluster search.
02:22
Now the heavy architecture is still a viable option for enterprise use. Depending on your network, it's important to assess your network and then make a decision based on your findings.
02:32
All right, that wraps up Lesson two for the intro to Security Onion. In this lesson, we covered what security? Onion is including the history and the functionality. What tools are included in security Union? Plus the architecture and the deployment types.
02:49
Thank you very much for listening in. The next lesson will cover installing and configuring a standalone instance. See you then. Cheers.

Up Next

Security Onion

Security Onion is an open source Network Security Monitoring and log management Linux Distribution. In this course we will learn about the history, components, and architecture of the distro, and we will go over how to install and deploy single and multiple server architectures, as well as how to replay or sniff traffic.

Instructed By

Instructor Profile Image
Karl Hansen
Senior SOC Analyst
Instructor