everyone. My name is Peter Sip alone. And this is the network Security course. This is going to be module three. Lesson one, the application section.
So the prerequisites for this video are really just modules one and two. Model one was simply an intro demonstrating how the courses leading out and module to was really a basic foundation off core cybersecurity, knowledge and principles.
And we're to had to keep up to date with the different laws and regulations and what's going on in the cybersecurity world.
So, like I said, we are now in the application information section off this course in this section, we're really gonna learn about specific applications and how they're broken down and why they're important to network security in this video. Specifically,
we're gonna learn how to manage data. We're gonna prevent it,
control it, had a handle it properly, and we're gonna look at some encryption practices that relate to the data. And obviously, when we're done using all the data, we're gonna look at the proper way to dispose of it.
data leak it prevention, also known as DLP DLP, is a cycle or process off controlling data and handling it in a responsible manner, So we're going to start up the top and work our way around clockwise.
So the first part of data leakage prevention is the discovery section. This is finding the data. You can't prevent data leakage, and you can't prevent the misuse of data if you don't know where it is. So actions in this section really include kind of scrolling through your network. Checking out your servers
PC's what information is on there trying to locate the data
that you want to protect?
The second step is labeling. This is where you tagged the data with sensitivity levels or basically other kinds of labels that can help track it for when the data moves throughout the system. Remember mandatory access control back in the second module.
While the labels sign demand for access control usually get assigned here.
The third step is policy creation. In this step, we defined the data rules and what the users can and can't do
with the with the data. You know, this is where rules get to find for where certain people might not open things. They might not be able to look at some things they might not be print certain aspects of data or send data from one spot to another. And then after we define the policy, we obviously have to watch the data
in order to make sure that the policy is being applied.
So this is where the content monitoring section comes in.
In this section, we watched the flow of data go back and forth across the network when it gets loaded on USB drives, how it gets emailed out
and basically just keeping the high on the day and make sure the policy creation the policies created in the policy creation section of being enforced.
When we do see something that's not being on fourth, probably we have the option to stop the data from leaving. This happens in the prevention and blocking section of data leakage prevention in the section This. This is where data can get filtered out either through Web, Web filter
or maybe an email attachment gets stripped out, or the far wall blocks the data from getting in from one spot
to another. And now, obviously, in the last section reporting, we got a snitch on the offenders we gotta figure out who tried to send the data to the spot that shouldn't have been doing why they were doing it and any other information to make sure that doesn't happen again.
Data encryption. There are three general areas off data. That conduct could possibly happen.
There is data at rest. That means in the date is not being used. That means being stored on a hard drive or on a server. Somewhere
there's data in motion. That means when data is going from point A to point B flowing across the network in route to do something, and then there is data and use. This is when the data is actively being queried, used, visualized in order to accomplish whatever the gold might be.
Thankfully, data can her data encryption rather can be applied in all three of these sections. Now there's storage level encryption. This is where the hard drive gets encrypted or the data gets encrypted before going into the database,
so no one can access or read the data while it's encrypted. So even if you broke into the database
wouldn't have access to the data
data in motion. This is taken care of through encryption through the use of special protocols are programs which will take a look at little bit later on in this course, specifically I, p, SEC, VP Ends and TLS and SSL.
More on that coming up later
and finally dating use is for information rights management. This is where the information basically is determined to what it can do.
So some people might have the rights to view information. Some people might have the right to print it out, right? It Some people might not have the rights to do any of that. All that's all that information is being used comes back to information rights management,
data retention and disposal. Obviously, the data can only be held onto or should only be held on to for so long and then, after which it could be disposed of in a proper and secure manner.
Data retention and disposal is a valuable part of the policy creation. It's not enough to simply say, what can a person can or can't do with the data. It's very important that the data gets recycled at the end of its life.
Now there are a couple different common ways off handling and disposing of data properly. The 1st 1 is known as disk wiping, where all the streams of zeros and ones are written over completely with all zeros or all ones. And the 2nd 1 is de glossing,
where the gloss er is a machine
that scrambles up the data so it looks like scrambled eggs and therefore the data is no longer readable. The pictures to the right show into Gosar. And what happens after the Gosar has run its course through the data
important note here, erasing or reformatting data is not enough. You actually have to make sure it leaves the computer or it is destructed in such a way that it cannot be put back together. Most people think at moving day to the recycle bin on the computer and then emptying the recycle bin deletes the data it does not.
the data merely state the data remains on the hard drive and merely the path that the computer knows to access the data is the latest. The date is not actually gone. It's still sitting on the hard drive, waiting to be over written, so you want to make sure that it's something very sensitive.
You can't actually delete it in that manner.
So in today's lesson, we discussed the data leakage prevention of life cycle. We took a look at data encryption in a network,
and then we took a look at proper data retention and how to dispose of properly when we're done with it.
All of these are components of the data leakage prevention lifecycle except
be dated disposal. See content monitoring or D reporting.
If you said B day disposal, you are correct. Remember, data disposal is not necessarily its own step in the data leakage prevention lifecycle, but rather it's like a subset off the policy creation area.
Hope you guys learned a lot in this video, and I'll see you next time.