Time
31 hours 29 minutes
Difficulty
Beginner
CEU/CPE
30

Video Description

Social Engineering and other attacks This lesson covers social engineering. This exploits weakness in people which allows attackers to find vulnerabilities. There has to be mandatory user training so employees know policies on things such as leaving a computer unlocked, giving out passwords or opening doors for unknown people. Other forms of attacks are viruses, worms, and buffer overflow. Companies and install anti-malware on computers to mitigate viruses as well as implementing user policies such as do not use unknown devices such as a USB just found on the floor. Worms are dangerous to networks because they can replicate quickly and take down a network by performing a constant denial of service. A buffer overflow is a vulnerability in a program that can write more program than can fit into a program so instead of fault finding, there is an overwriting after a buffer than can cause a crash.

Video Transcription

00:04
So next we have social engineering. Now. Social engineering is not an attack necessarily against our I T devices.
00:12
We don't social engineer. We don't social engineer a switch. We don't social engineer a router Because social engineering is exploiting people.
00:20
Social engineering is doing things such as walking is such a cz walking up to a door that requires a key card to enter and holding a box of doughnuts and or standing outside and taking a smoke break or walking up to a door on crutches right behind someone. You're exploiting people's,
00:40
uh,
00:41
procedures. You're exploiting people's weaknesses in just their day to day, day to day respectful nous and niceness. If you're walking up to the door with the computer bag over one arm, a bunch of books in the other, and you're barely making it on crutches that you that you went to the store and bought
00:59
then if you're hobbling up to a door and so and you're like, Oh, hey, hold the door,
01:03
then
01:03
a lot of times you're not gonna have someone who just says no and slams the door closed and then says, Use your own I d.
01:11
That's best security policy for them to do that. But the way that we in society have,
01:18
we have our, you know, procedures we have our own. We have our own unwritten rules of things that we have ways that we need to act. We have our own anthropological this way we have our own anthropological actions that we need to do that
01:34
social engineering can exploit those social engineering, can
01:38
exploit those weaknesses and make use of them to gain entry into our network. Again, Things like walking really fast down the hallway carrying a clipboard,
01:48
you may hear some people say, if you know, a lot of times people will say Okay, if if you walk down anywhere and you look busy, no one's gonna bother you. If you look like you're in a rush to get somewhere and you look like you know where you're going, then a lot of times you won't have somebody stop you and say, Hey, can I see your badge? If you're if you're carrying a clipboard up near where your badge usually would be,
02:07
sort of obscuring the view.
02:09
And maybe you went on your computer and printed out a little fake badge and laminated it and stuck it on, you know, and you stuck it on your best pocket. Because, of course, no one could do that at Staples or Office Depot. Then
02:21
you're gonna have a lot less People bother you. Then if you are walking around looking very suspicious, so social, so again, social engineering is just exploiting those people weaknesses by knowing how people act, knowing the standard way that people are receptive to actions knowing that if
02:38
you're requesting a password you're talking to I t on the phone
02:43
and you're requesting a password. Reset. You're requesting a password. Reset. And then you say, Well, I want to speak to your manager. You sound very urgent. Then they may just say, Okay, okay. I'll just reset the password for you. Or if you impersonate I c I t department calling someone and then you say, OK, I need your security questions or I need you to send me your password.
03:00
All of this is social engineering, anything where you were. You're not trying to find a vulnerability. You're not trying to find a technical vulnerability. You're not trying to find a vulnerability in computer software computer hardware. You're trying to find a vulnerability in people that social engineering. Now we can't patch people
03:20
we don't have.
03:22
We don't have
03:23
employee employee user Update 2.5 that exploits the door that patches the door, the door holding, opening exploit.
03:34
That's not the way that this works. We can't. We can't perform the latest Windows updates on people being respectful and people on people not asking for your badge. What The way we go, the way that we patch that the way that we fix that security hole is through user training, we have to have user training and user policies that are mandatory
03:53
so that
03:54
employees know. Okay, I know that I want to hold the door open for this person. I know that I need to be nice, but because of this policy and because of what we learned in our training, I probably should close the door. Maybe I can. I can help them with their books and let them card in and then hand them their books and then all card in two and come in the door.
04:15
We need to have training not to open that email from the Nigerian prince who wants to share his wealth for me with you. We need to have policies that let us know not to leave our computer unlocked, not to leave our badge lying around, not to write our passwords down All these things that are potential exploits in our people. So these user training and policies are extremely critical.
04:34
And if they don't work, if we still have people holding doors open, if we still have people writing down their passwords,
04:40
we need to have repercussions. For that. We need to have repercussions for if your manager finds that your computer isn't locked or if your manager finds password written down and stuck on a sticky note on your screen. Or maybe we need to hire security personnel to stay in that doors. Where does whatever the case may be? We can't just focus all of our time and all of our energy on
05:00
our actual network. Resource is on our switches and our routers and our computers.
05:03
We can make those 100% fail proof secure, but we still have people who have passwords and have access to the divide. Those devices which could be socially exploited, which could be socially engineered
05:16
and next we have viruses. Viruses are is malicious software malicious coating that attempts to
05:24
perform actions on our computer that essentially we don't want them to.
05:29
Now viruses can be in the form of
05:32
they could be formed, informed in the form of fake anti viruses. They can be in the form of malicious downloads that could be in the form of email attachments. Attack surfaces for viruses could be practically anywhere, so we need to have for in order to help
05:48
mitigate virus viruses on our network. In order to help mitigate malware on our network, we need to do a couple of things. First of all, we need to have keep having this user training. Use your training to let people know not to open email attachments that look suspicious. Let people know not to pick up
06:05
USB devices off the floor and just plug them into their computer. That could have malware on them. So Benito have user training to let people know where these viruses could come from and what not to d'oh
06:17
and what to do. In order to help prevent this and how to report how to report suspicious items.
06:24
We also need to have anti Mau updated anti malware and updated anti malware signatures on our computers. It because if we do have that malware or those viruses get on our computers, we wanna have something that is able to help prevent it from spreading. We wanna have something that gets rid of it as soon as possible.
06:41
We may want to implement intrusion prevention systems. I PS is or I. D. S is on our network
06:46
that can prevent or can detect at least suspicious traffic and suspicious items on data on our network.
06:54
We may have again user policies which goes with our user training.
06:58
In addition to our anti malware, we may have our we may have restrictions on our network that remember when we talked about our policies For if someone is allowed to connect to our network, we may have policies that say, OK, do you have the most latest you? Do you have the most recent edition of our malware?
07:16
Do you have the most updated signatures?
07:18
Have you done a scan in the last 48 hours? If not, you are. You can only connect to my remediation network until you fix these issues because I don't want you connecting to my main network because you could potentially be infected and that infection could spread. So we need to have those mitigation strategies in place
07:35
in order to protect. Protect against that. The malicious software malicious code protects against that malware.
07:42
Now, next, we have worms.
07:45
Now what's the difference between worms and viruses? Well, whereas viruses air malicious, execute a bles, worms do not need to be attached to an execute a ble in order to spread. Worms are self replicating, So all we would need to do is have that computer or have that device somehow touch a different device.
08:05
It could be connected over a network. It could be connected via a USB. But whatever the case may be, that worm has self replicating code
08:13
that it can spread by itself. It can wiggle its way through a network without having to have anyone ever click and execute herbal without anyone ever running a malicious program. It just makes its way through the network. It's self replicates
08:26
now. These convey extremely extremely dangerous to our network because if they spread wide enough and this has happened before, where worms replicate so much across our network, that 80% of our network traffic is just this worm trying to replicate itself.
08:43
So we essentially this worm is essentially performing a denial of service on our network
08:46
because it's trying to replicate. And it's doing so, so loudly. And it's taking up so much a network traffic because it's just moving all over the place, trying to infect new hosts so
08:58
worms could be self replicating. They can be polymorphic, which means that can have sections of code that adjust and change every time that they replicate so that it's harder to pin them down. It's harder to create a signature for them.
09:11
So if a warm is polymorphic it, we may have a file. When we say, Ah, this is the worm file. I found it. I'm gonna create a signature for this all my anti virus is there gonna be updated
09:18
and then you update your anti virus, and it only finds tomb or instances of that that worm on your entire network. But you know it's but it's much more widespread than that because the warmest polymorphic it keeps self, it's keeps changing its code. It's a lot harder to pin down, so worms again
09:37
are going to be one of those things that you need to do. Things such as having user policy is not to plug in unidentified US bees to your computer.
09:45
You can't plug in any personal U. S visa to your computer. They have to be secure. US peas you may want you may want to
09:52
put those ideas is an I. P. S is on your network. You may wanna have content filters to prevent people from getting too certain websites where they could unintentionally download a virus or worm. So all of these policies, all of these best practices, need to come in place to prevent these worms from infecting our network and potentially spreading on our network. It's much harder.
10:11
You know, There's a saying that
10:13
an ounce of prevention is worth more than a pound of the cure. So an ounce of set up beforehand announce of security policy and preventing the worm from getting on our network at all is worth more than the hours and hours that it may take spending to clean it up.
10:30
So we need to be aware of that.
10:31
And lastly, we have buffer overflow now buffer overflow attacks are a little bit of a a little bit of a high end topic, but let's see if we could explain them a bit.
10:43
We're talking about buffer overflows.
10:46
We're talking about data over running into other sections of memory and potentially executing arbitrary code, potentially potentially
10:56
potentially executing code that is causing our computers to do something that we don't want them to.
11:03
So
11:03
when a program on working up we're going to create, we're gonna do a very, very simplistic representation of what? A buffer overflow. Is this something that you find more interesting, which I know. I sure do feel free to go into look into programming and looking to our other programming sections
11:22
now. Ah, buffer overflow is when data executes
11:26
our program. We have something called the Stack.
11:30
This is gonna be a very, very simplistic overview.
11:33
And when on the stack is essentially a section of our men are computer memory where we can store variables, we can store data for our program to run because our pro different for different programs need some section of memory so that they can run so that they can execute code.
11:52
So when our program starts,
11:54
it's going to create something called a buffer
11:58
that is a section of memory that it reserves for its program. It's a section of memory that it reserves for its program reserves. For a variable, it was variable being a
12:11
piece of essentially
12:15
and something that equals something. So if we have a program that asks us for user input, it may create a buffer that says, Okay, I want you to save this much space in memory for that user input. So when the user enters in the input,
12:31
I could just save it right here, and I'm gonna make this buffer this big.
12:35
So it's sort of our buffer is our box that we can put things into in our memory that we say that our program saves for us
12:43
and essentially a very, very simplistic view of a buffer. Overflow
12:48
is an ex point or is a vulnerability in a program that
12:54
our buffer is just a set is just a section of memory
12:58
before
13:01
and after. Our buffer
13:03
is other information in our memory. It could be the same. This information in memory could be our same program, or it could be a completely different program.
13:13
Now when our buffer overflow runs. Essentially, what's happening is we're writing
13:18
in a very, very, very simplistic view. We're writing more data than can fit into that buffer.
13:26
So we're writing more than and then conf it, then conf it into this. So our program,
13:31
instead of fault checking this is just going to overwrite
13:37
the memory after the buffer.
13:39
And this could be something completely different. This could be a completely different program, but we're gonna overwrite that
13:45
now.
13:46
Typically speaking, if this was an accident, then this may just cause some corruption of data in our memory. This may cause a program to crash may cause some other errors on our computer, but it may not be anything or anything really too bad. But if this is a malicious attacker, if this is someone legitimately trying to exploit a program,
14:07
they may
14:09
overwrite this following data
14:11
and may overwrite this following data with information that allows them to execute commands on our computer.
14:18
So
14:20
approach any program that is writing this information to memory. They perform their ableto, successfully perform a buffer, overflow and then they're able to perform things such a system calls they're able to perform things that essentially tell our computer to just start running commands and they're able to exploit our computer.
14:39
They can get back door access into our computer. They can exploit that program.
14:43
There's a lot more to this than we're making it seem right here. But
14:48
in a nutshell. If you didn't get any of that, just take away that. A buffer overflow is a vulnerability in a program. So it's it's a vulnerability of something that we install. It's a coding vulnerability in something that we install on our computer.
15:05
So in order to mitigate Buffalo overflows, we need to do things. Unless Royal Programmer before a programmer, There's a lot of things that we need to do to help mitigate buffer overflows. But if we're just a systems administrator or a network in administrator, what we need to do to mitigate buffer overflows is to install patches and have a regular patch cycle
15:24
for the programs on our computers.
15:26
Because
15:28
unless world programmer,
15:30
we're not going to be going in and changing the programming and we're not going to be going in and doing a dissection of the programming on all of the programs that we allow on our network. What we are going to do is we're going to make sure that we leave that to the programmers of the actual software. What we do is we Whenever they release patches,
15:48
we need to make sure that we're pushing those patches out to our computer.
15:50
So for us, it's systems administrators for us, his network administrators in order to mitigate buffer overflows. We make sure that before we allow software to be installed on our computers, we have test cycles of the software. We make sure that we check. It's that software security rating. Make sure that there's no known vulnerabilities for that software that have been unpatched. And when patches do come out,
16:11
we test cycle those, and we roll those out as soon as possible
16:14
in order to prevent those from being vulnerable.
16:18
So enough about forever flows. We talked about quite a few different attacks here. We've talked about our denial of service attack, distributed denial of service, attack me in the middle middle of tax, talked about our social engineering viruses and malware, and then a little bit about buffer overflows. So let's go ahead and let's move on. And now let's talk about some packet sniffing

Up Next

CompTIA Network+

This CompTIA Network+ certification training provides you with the knowledge to begin a career in network administration. This online course teaches the skills needed to create, configure, manage, and troubleshoot wireless and wired networks.

Instructed By

Instructor Profile Image
Anthony Harris
Systems Analyst and Administrator at SAIC
Instructor