1
- 1 year ago
Category
🦄
CreativityTranscript
00:00:00Hello, welcome back everyone. This is Timberwolf. I'm going to be discussing
00:00:16Introduction to Ethical Hacking with you. So let's get started. So we're going to
00:00:22have some objectives. The module objectives will be the overview of the
00:00:26current security trends. We're going to understand the elements of information
00:00:29security. We're going to understand information security threats and attack
00:00:33vectors. We're going to discuss an overview of hacking concepts, types, and
00:00:37phases. As well as understanding ethical hacking concepts and scope. And we're
00:00:44going to be discussing the overview of information security management and
00:00:48defense in-depth strategies. So that's not defense. We're going to be discussing
00:00:53defense in-depth strategies, right? So they talked about how this was a 100%
00:00:59offensive course. Nothing to do with defense. But obviously we are going to
00:01:05be discussing some defense as well. Quite a bit actually along the way. We're going to
00:01:10be discussing an overview of policies, procedures, and awareness. Which are your
00:01:15procedural controls? Policies and procedures and awareness to keep your
00:01:21people sharp versus just trusting and being dependent on tools. Part of the
00:01:26defense in-depth is to spread out your defense posture. So you can do that
00:01:31through your workforce and your appliances, right? So right off the bat
00:01:34there and the first two bullets we're doing both of those defense in-depth and
00:01:38we have procedural controls in place to help with that, right? So we have an
00:01:42overview. We're going to discuss an overview of physical security and
00:01:45controls. So like with physical security we'll be talking about that quite a bit too
00:01:50when we get to the cloud part of this course. Understanding incident management
00:01:54process. So what does it mean to handle incident management? We'll go we'll get
00:01:58into that. Overview of vulnerability assessments and penetration testing. So
00:02:03we're going to be discussing that quite a bit along along the way. The difference
00:02:09between a vulnerability assessment and penetration testing which together those
00:02:13are called a security assessment. So most of the time when people order a
00:02:17penetration test that is not what they get. They get a vulnerability scan, right?
00:02:21Which is not what you want. You need to understand that cold. And then an overview
00:02:26of information security acts and laws. So we'll get into that as well. So we're
00:02:30going to be discussing information security overviews, information security
00:02:34threats and attack vectors. Like where are threats and attacks coming from? What
00:02:43posture does my network have that can be attacked? Where are my weaknesses? Where do I
00:02:48need to spend money hardening? That kind of stuff. So that's kind of what number two
00:02:52is about. And then number three, hacking concepts, types and phases. So what is the
00:02:56life cycle of a hack? What does it look like? How am I going to be susceptible to
00:03:00this kind of thing? You know what I mean? How is this going to be thrown at me? We're
00:03:03going to talk about that so you can understand it. The more you understand how
00:03:06they think, the more you can understand how to defend. And we're going to be
00:03:09talking about both of those so you'll get that. So we're not training people how to get into
00:03:13your network. You need to understand 100% how they think and what they do and be able
00:03:17to do what they do to be able to defend properly. We are training you to be defensive, not offensive,
00:03:24even though that is what they said the class was about. So ethical hacking concepts and
00:03:29scope. So we're going to discuss ethical hacking, the concepts of it and scope and
00:03:34the differences between hacking concept types and phases, right? So we're going to compare
00:03:38and contrast there a little bit. And then we're going to have a discussion about information
00:03:42security controls, what those may look like, what's available today. And then information
00:03:47security laws and standards. So the internet is an integral part of business and personal
00:03:54life. What happens online in 60 seconds? So we have YouTube, Pinterest, Google, WordPress,
00:04:02email, Amazon, people buying, selling, using their computing power. It's not just about shopping,
00:04:10Amazon has a lot of stuff, watching movies, entertainment. We have Snapchat, Skype, people
00:04:15communicating. iTunes, music, it's huge. Video is also huge. Instagram, Twitter, people communicating,
00:04:23letting each other know what's going on. That's a huge attack vector right there. Facebook, YouTube,
00:04:30so on and so forth. So this is kind of a breakdown of what happens in 60 seconds on the internet.
00:04:35And we're going to discuss some breaches along the way of this course. So for example, there
00:04:42was a data breach at Target and Home Depot. And the IRS just had a big one as well. So
00:04:49did the government. They had some information stolen from a bunch of military personnel that
00:04:55had security clearances. So then they can either trick someone into thinking that they're one
00:05:00of those people and get a job. And maybe they can fake that that security clearance is theirs
00:05:06and be exposed to that sensitive information. Big, big problem with that, right? The IRS has record
00:05:12stolen, which is giving people identities. So now those people can present those identities and file
00:05:18more taxes and get money free back from the government. For somebody else that paid in,
00:05:22they get their refund. So the people that paid in all that extra money that they shouldn't have paid in,
00:05:26people will think that, um, I get my tax money back that it's money from the government, but really it's
00:05:31just overpayment along the year. What you want to do is you just want to pay in enough. So I bet that
00:05:35people are going to learn this fact now and probably start paying less and less in so they get it about
00:05:41just right, right? Because you're giving the government free use of your money for that extra time,
00:05:46that whole year. So there's a chart floating around out there about the year of the mega breaches.
00:05:52So we've had really big breaches now, but the thing is, is they're just coming to light. Those people
00:05:57have been owned for a long time. They've been, they've had people, their networks have been
00:06:01compromised for a long time. They're not new. Uh, they're just becoming one, they're becoming more
00:06:06and more public. So they've been going on. They're not new. And then the number of records stolen before
00:06:13they catch it is new. So people are stealing massive amounts of information because of the network speeds
00:06:20and storage on the other end is becoming cheaper and cheaper. They have a place to store. Usually
00:06:25they just use your network as the repository. They just go and got what they needed. So if you want
00:06:316,000 credit cards, I'll go get you 6,000. You want another 6,000? I'll get you another 6,000. They
00:06:36just go back and forth to the network and get it. Well, today our controls are becoming a little better.
00:06:40Um, people are starting to check this stuff more. They're finding out where, how people are getting in
00:06:45through penetration testing and security assessments. Um, so we're starting to understand that things
00:06:51are happening. They're putting, um, monitoring deep packet inspection over encrypted channels.
00:06:57So we're starting to see that there are hackers on networks. And so it's becoming a little more public.
00:07:02It's not, oh my gosh, what happened this year? Why are there so many breaches? These things have been
00:07:07going on for years and years. They're just finding out about them. So it's just, uh, it's not something new.
00:07:15Um, some data breach statistics. There were about 3 million data records lost or stolen in 13.
00:07:45Um, so it's not something new. It's, uh, going on all the time. They really started being discovered
00:07:54big time in 2011. So more and more and more we're finding that networks are owned. They just had, uh,
00:08:01a company in Silicon Valley last two weeks ago. They found out that there were some, uh, nation state
00:08:07actors on their network and wondering why are they on our network? We don't have anything that they would be
00:08:12interested in. Well, it wasn't what they were interested in. They were selling software to
00:08:17another company and the nation state was interested in that company. So they attacked the nations or this
00:08:23company because they were a low hanging fruit. They were easy to get in. They didn't have a bunch of
00:08:27network infrastructure and security. They got ahold of the software tainted that and then fed it over
00:08:33to the other company. That company then put that software in production. And now they had a back door in.
00:08:37So don't underestimate the lengths at which hackers will go to get on your network. They will go to
00:08:43great lengths to get onto your networks. So again, uh, there's many reasons people do this kind of
00:08:49stuff. Not again, this is the first time you're probably hearing it, but there's a lot of reasons
00:08:53why people will want to get into your networks. So, uh, from theft, political gain, um, hacktivism,
00:09:01all of this kind of stuff. There are a lot of reasons. So trends in 2014. So we have source code
00:09:08leaks, old school malware techniques, growth of 64 bit malware, which of course it's going to happen.
00:09:14It's just software, right? Everything's trending in that direction. Malware researcher evasion. So the,
00:09:20the tactics that we use to detect them, they're learning that. So one takeaway from that is this
00:09:25is a tit for tat game. For everything we do, they'll come up with something else. This goes on
00:09:30all the time. I always tell people when you're breaking into this industry, you're going to have
00:09:35to constantly learn like a surgeon or a doctor, right? One of the reasons I didn't go to medical
00:09:42school when I was in college is because I'm like, man, I don't want to spend the rest of my life
00:09:46learning. Well, boy, did I make a mistake. So I got into engineering. I went into software engineering
00:09:51and I do nothing but learn every single day. When I get up in the morning, I have to read and read and
00:09:56read. Not only does it change monthly, it changes daily, hourly. So it is, it is constant. Every time
00:10:02I turn to look and read more stuff, I'm like, how did I not know that? How did I not think about that?
00:10:06It's constant. So if you have the choice, if you're on the fence about medical school or not, go to medical
00:10:11school. So it's probably going to be less learning for you. So we have mobile SMS forwarding malware
00:10:17that's been around since 2012. They're becoming ubiquitous, so widely used. Phones are a huge,
00:10:24easy, low hanging fruit and a huge target today. The mobile space is a huge target. It can actually
00:10:29circumvent all the multi millions of dollars we put on our network infrastructure. A cell phone can leak
00:10:34all the data and not be detected at all. Account takeover, attacks on corporate and personal data,
00:10:41exploit kits, social engineering, all kinds of stuff like this. So we have some malware trends
00:10:49that we were just discussing. And we're going to talk about attackers increasingly lure executives
00:10:55and compromise organizations via social networks, right? So everybody wants to be out on LinkedIn
00:11:01and branded me has got this new thing where they're deeply invading all the people that you know and
00:11:06stealing all of your information from LinkedIn. People are starting to post things on LinkedIn that are
00:11:10personal. So everybody's looking for a new way to switch off of LinkedIn, right? Because it's becoming
00:11:14the Facebook. So that's the problem. But there's a lot of information. People just put too much
00:11:20information out there. If you're in the security industry, it's probably not even a good idea to
00:11:26publish where you work because they know what you know. So if Timber works at Company X and Timber
00:11:34knows Cisco and Timber's a Cisco guy or just a Juniper guy or just a Gigamon guy, then I know what
00:11:42network gear they're using at that company, right? So if you're a specialist, if you're highly
00:11:47specialized, you should probably not be putting what you do on LinkedIn, okay? So you can put what you
00:11:56want on LinkedIn. You can put what you do and what you know, but then don't put where you work because
00:12:01now you've just linked those two together. And now I've got all the information I need.
00:12:06Okay. I just need a set of Cisco exploits because Timber knows Cisco and he works at Company X, right?
00:12:11There you go. Boom. That's a big problem. So you just leaked a whole lot of information. Of course,
00:12:15they can scan the network and, you know, see where you're going. There's other ways to find it,
00:12:19but make them work for it. Don't, don't just give it away out on social networking. So it's not,
00:12:24not everybody needs to know your business. Not everybody needs to know where you work today.
00:12:27Put that on your resume, keep it encrypted and send it out when people need that information.
00:12:32That in itself is responsible security. And I look for that when I go to
00:12:38socialize people to my management or something like that, or the companies where I'm working,
00:12:42I'll say, Hey, look, you know, this guy's pretty sharp, you know, but he does expose a lot of
00:12:47information. You know, people tend to be very proud of where they work and stuff like that. So they want
00:12:51to socialize that and spam that out everywhere. Put it on Twitter. Hey, look where I'm working today.
00:12:56You know, this, this can be a problem if you work in security for people that work in
00:13:00marketing. Hey, that's great. But for people that work in security, you may want to rethink that
00:13:05kind of thing. So that's just one bullet off of here. Right? So then we have Java remains highly
00:13:10exploitable. It's a feature you have to deal with it. So you better, if you're going to be using Java,
00:13:15you better have teeth on your network that can arrest it. So one of my little sayings is something that
00:13:19I've learned is you can't keep people out of a network. It's naive to think that, um,
00:13:24at some point they're going to get in or at some point they may have been there a long time before
00:13:28you even got there and you're just trying to get spun up. It takes you a while to detect it and like,
00:13:32oh, I see somebody's on our network. What do we do? So a good security program is something that will
00:13:38catch a breach early, catch it very quickly, and then give you the tools you need to eradicate those
00:13:44attackers as you discover them. Whether it's a new discovery or an old discovery, you have to be able to
00:13:51get them off of your network. So part of the exercises that I've been on are just trying to
00:13:56figure out where this guy's at today, which machine is he in today, and then get rid of him.
00:14:01And it's like almost impossible in some networks to do that. It's insane the stuff you see out there
00:14:06that people set up. They have all these different ways to get in their network and they're not
00:14:11properly structuring their network security appliances and you think you've got them blocked
00:14:17and then all of a sudden he shows right back up and you're like, what the heck is going on here?
00:14:21And then you start digging more and more into the network and you realize, oh my gosh,
00:14:24they've got this other whole connection to the network that's completely insecure
00:14:28because they procured an office and they forgot to add it to the network diagrams for people that
00:14:34were doing the architecture of the system, the system architecting. So it's a big problem.
00:14:39Java, if you're going to have things like this, then part of the expense of bringing this in is
00:14:44you've raised a risk. Now you have to mitigate that risk in some way. So if you're going to bring a
00:14:49risk in, that's fine. We can have networks that are very risky, but put the tools in place to arrest
00:14:55the problems as you find them and give yourself, give your engineers the tools to discover the
00:14:59problems, right? So you want to have monitoring of your network in place. You might need to do URL
00:15:04checking, where are things coming from, be able to shut down networks in Russia if you see them
00:15:10connecting to your network. If that's not normal, you know, that kind of thing.
00:15:26And attackers are more interested in cloud data than your network. So yes and no. So this is a
00:15:45double-edged sword. So I hear this in conversations quite a bit. So people say, I don't care about your
00:15:52corporate machines. I just want to get on your cloud and then I want access to all of the data
00:15:57that you're storing in your cloud. But well, I mean, absolutely that is the the golden goose
00:16:03because that's where everything is stored. Financial data, everything, right? But what if you're using
00:16:08a company like Salesforce.com who has hopefully a really good security infrastructure and it's very
00:16:16difficult for me as an attacker to get in as one guy to get into Salesforce.com. So I'm thinking
00:16:23about it and I'm like, well, what if I just compromise the guy's machine, which is not
00:16:28a hardened machine because this company doesn't care about security because they have all their stuff
00:16:32in the cloud. So why would I care about security? Why do I need to spend money on that? That's what
00:16:36I pay Salesforce.com for, right? Ah, but you have an endpoint and you use that endpoint to access that
00:16:42data. Okay. So once you either a download it to that machine or B you log in from that machine.
00:16:48Now I can use your machine as a pivot to get in there and get all of your Salesforce data. So that's
00:16:53the kind of stuff we're going to be talking about attack vectors, right? And why you need to encrypt your
00:16:58endpoints and why you need to have security on your endpoints and monitoring on your endpoints,
00:17:03whether those people are remote or local or whatever traveling salesman, you know, you need to have the
00:17:08right tools for the right job for your network engineers. Otherwise a breach is inevitable
00:17:13and you better plan accordingly, right? You better hire a PR firm. You better be ready to go when
00:17:17it happens. And then if it happens, nobody panics. You've got a lockstep response and hey, that's fine.
00:17:23That works. If that works for your company, then that's fine. That's a security program, right? You can
00:17:28do it however you want, but you better be ready to respond, you know, appropriately. If you want to hire
00:17:33quality security engineers, they're not going to work at a company or, you know, this, I'm talking to the
00:17:38security engineers that are up and coming here. So you may not want to work at a company like that
00:17:42because in the event of a breach, your name will be attached to it. So you better think about that.
00:17:48Whenever you go for an interview, you want to interview them as well. What kind of stuff do you
00:17:51have? Oh, you don't have anything? Yeah, that's why we're hiring you. We don't have anything. Come help us
00:17:55secure our network. Well, gee, I just started, I just got my CEH and Timberwolf told me that I don't really
00:18:01know anything yet. So do I, is that a smart thing for me? So you may want to think about that. It might be a good
00:18:07opportunity for you if you think you've got the chops for it, but just make sure that they have
00:18:11a budget and stuff like that, that they're going to spend money on the program. They're going to buy
00:18:14their tools. They're going to give you some stuff that you can play around with and give you some
00:18:18freedom to kind of go and hunt for stuff as well, which means you need a team of people. One guy
00:18:22cannot do all that or one lady cannot do all that, right? So some people say the sheer volume of
00:18:27advanced malware is decreasing. I don't know if that's true. I don't necessarily agree with that.
00:18:32Maybe the families of it are decreasing, but the actual malware that's out there is getting ever,
00:18:37ever, ever more and more complex and just huge in its actual surface of what it does. Even the
00:18:45binaries are getting bigger and bigger. So a lot of times you'll have one little bitty piece of
00:18:50software that would come in and drop all of this stuff on your machine, like rootkits. They're really,
00:18:53really small. They come in and then they bring down all the big stuff that's going to need to be running.
00:18:57So I don't know that I agree that people say the sheer volume of advanced malware is decreasing.
00:19:03That's probably a farce. Red Kit, Neutrino and other exploit kits struggle for power in the wake of
00:19:10the black hole. Arthur arrests. So that's old school. That's not necessarily current as of today. What
00:19:19happens in these things is that the source code is released and people go and start doing little
00:19:23twists and bends on this kind of thing. For example, Zeus Kit is out there on GitHub. The Zeus Malware
00:19:29Kit is out there on GitHub. The 2.8 version is. There are many, many, many later versions that
00:19:35do a lot more advanced things than just what 2.8 did. There's a whole bunch of stories there which
00:19:40we'll get into later and we'll talk about some of the history of this malware family and stuff.
00:19:44So a minute ago we were talking about the sheer volume of advanced malware is decreasing and I'm like,
00:19:48I don't necessarily agree with that. But just remember for the test that that is true. That's
00:19:53a fact. The sheer volume of advanced malware is decreasing for the test. The next bullet is we
00:20:00want to talk about the mistakes made in offensive security due to an attribution of an attack source.
00:20:05So mistakes are made in offensive security due to misattribution of an attack source. So people are
00:20:11attributing things to an offensive attack but really you're just trying to test your own network but
00:20:18you got it wrong. You're testing someone else's network. So that's a big problem, right?
00:20:23Cyber criminals are targeting the weakest links in the data exchange chain. We talked about that a
00:20:27minute ago. They are actually attack a separate company as a vendor to the primary attack victim,
00:20:33right? So if I can't get directly into the victim, Salesforce.com for example, I'll go either
00:20:37after a user or a supplier to Salesforce.com and then they deploy that infected software and now I've
00:20:44got my in, right? I've just gotten my back door. So you as a company, if you're going to be an
00:20:50engineer at Salesforce.com and somebody says, hey, here's some software I want you to run as part of
00:20:54an update on that last software I gave you, you better check it, right? You want to check it and
00:20:57make sure there's no back doors in there. So major data destruction attacks are increasing.
00:21:03So there are data destruction attacks. So people are actually destroying data again,
00:21:08which is a rare thing. People are erasing networks and stuff like that,
00:21:12data off of networks. Usually they just let it sit there and access it as they need to.
00:21:17So for this last bullet, one of the examples of that is like BitLocker. They're encrypting all of
00:21:23your data and then charging you money to try and get it back or they'll erase it.
00:21:41So some essential terminology for this course are going to be hack value. It is a notion among hackers
00:22:02that something is worth doing or it's interesting. So people will hack attack and crack just because it's
00:22:09interesting, not because they want to make money off of it, not because they want to make some kind of a
00:22:14political gain, just because it's interesting, they'll do it. We have the concept of a vulnerability,
00:22:19which is the existence of a weakness, a design or implementation error that can lead to an unexpected
00:22:24event compromising the security of the system. So you make one little mistake and then someone out there
00:22:30will be poking around at every little thing looking for a problem. For example, if someone left off
00:22:34a default case statement off of a switch statement in C or C++, if I left off that last catch-all,
00:22:45then that could be a problem that can be used to exploit machines and software.
00:22:50So we have this concept of an exploit, which is a breach of an IT security or an IT system security
00:22:56through vulnerabilities. So exploitation of a vulnerability means I take advantage of the
00:23:02vulnerability. I actually can compromise the system. Not all vulnerabilities are exploitable.
00:23:08Okay. So not all vulnerabilities are exploitable. That is an important point to understand for real
00:23:13life. I don't know that you'll see that on, actually, I think it is a test question too.
00:23:17Are all vulnerabilities exploitable? No, they are not.
00:23:20So a payload, a payload is a part of an exploit code that performs the intended malicious action,
00:23:26such as destroying, creating back doors and hijacking computers. So the payload is not the thing
00:23:34that exploited your system. The payload is what they're trying to drop on the system after it's
00:23:39been exploited, right? So we have a vulnerability. We have an exploit that takes care of that or exploits
00:23:47that takes advantage of the vulnerability. And then it will drop a payload on the machine to try
00:23:52to get it to run. And that's the actual thing that will talk to the hacker and say, Hey, I'm installed.
00:23:56What would you want me to do today? What would you like to do today? And then we have a zero day attack,
00:24:01which is usually spelled with a zero D-A-Y. And it's an attack that exploits computers application
00:24:08vulnerabilities before the software developer releases a patch for the vulnerabilities. So there's
00:24:13zero days that we've known about it since the patch was released. That's where the name comes from.
00:24:18So a zero day attack is just, um, I, I just discovered something today and I have not told
00:24:24the manufacturer about it. So the manufacturer may or may not know, but the point about a zero day,
00:24:31the distinction is, is that there's no patch available for that zero day attack.
00:24:36So if you hear it about an O day or a zero day, then you're like, Oh no, what do we do? So you,
00:24:43there's other ways to mitigate the problem. You need to understand how the attack works. You go and
00:24:47do your research and then you figure out how can you mitigate it since you don't have a patch. Maybe
00:24:52you patch it yourself. Maybe you have your security appliance look at, Hey, here's the signature for
00:24:57that zero day attack. Let's go ahead and kill this connection. So it could be as simple as that. So zero days
00:25:02don't have to be the end of the world, uh, once you know about them, but it takes a manufacturer
00:25:07sometimes a little bit of time to put out a fix for a patch for them. So daisy chaining,
00:25:13it involves gaining access to one network and or computer, and then using the same information to
00:25:18gain access to multiple networks and computers that contain desirable information. So gaining access
00:25:24to one or more networks and or computers, and then using the same information to gain access. So you just
00:25:29go from one to the other, to the other. So you can do it from here, boom, boom, boom,
00:25:33or you can do it along the way, boom, boom, boom, boom, boom, right? So you can pivot from one
00:25:39computer to the next down the way. So you're daisy chaining. Um, doxing, publishing personally
00:25:46identifiable information about an individual collected from publicly available databases and social media.
00:25:52So doxing is just going out and collecting a bunch of information on a target and then publishing it
00:25:57somewhere. So that's all it is. So it might be at a paste bin, it might be an encrypted paste or
00:26:03something like that. So they're publishing it to their team or a team they may want to work on,
00:26:07something like that. A bot is a software application that can be controlled remotely to execute or
00:26:13automate predefined tasks. So we have a bot and then we have a botnet, right? So that's a network of bots.
00:26:20So a bot is just a program that just sits and listens and does what it's told to do.
00:26:25So we have some elements of information security. Information security is a state of well-being of
00:26:33information and infrastructure in which the possibility of theft, tampering, and disruption
00:26:37of information and services is kept low or tolerable. So we have confidentiality, integrity, availability,
00:26:45authenticity. So we have that, um, and we also have non-repudiation. So these are a bunch of key
00:26:50concepts. So we have the CIA triad in here, which you should have heard about already from Security Plus.
00:26:57So confidentiality, integrity, and availability. Um, so confident, let's go over them again,
00:27:04just to refresh your memory. So confidentiality is the assurance that the information is accessible
00:27:09only to the authorized, um, only to those authorized, uh, to have access. And then integrity is the
00:27:17trustworthiness of the data. Has it been tampered with availability? Is it up? Can I access it from
00:27:23my remote connection? And is it authentic? The authenticity refers to the characteristics of
00:27:28communication, um, document or data ensures the quality of being genuine. So is it authentic? Has it
00:27:35been tampered with? So that goes back to integrity, right? Is it the same as it was when it was
00:27:41published? And is it authentic? Is it real in the first place? And then the guarantee, um,
00:27:49non-repudiation is a guarantee that the sender of the message cannot later deny having sent the message
00:27:55and that the recipient cannot, uh, deny having received the message. So we have non-repudiation.
00:28:01So we know that these two communicated in the case of, uh, espionage of some sort, whether it's corporate
00:28:07or, you know, governmental, that kind of thing, nation action, nation state actors, uh, we can prove that
00:28:13they were communicating in some fashion. It could also be that, you know, you sent this document,
00:28:17you received this document, that kind of thing. Non-repudiation is usually accomplished through,
00:28:22um, the PKI infrastructure, the public key infrastructure.
00:28:36Hacking phases, uh, reconnaissance. So we're going to talk about reconnaissance, scanning, gaining
00:28:58access, maintaining access, and clearing your tracks. So what is reconnaissance? Reconnaissance refers
00:29:04to the preparatory phase where an attacker seeks to gather information about a target
00:29:09prior to launching an attack. It could be the future point of return noted for ease of entry
00:29:14and an attack when more about the target is known on a broad scale. So the recon, we can say, hey,
00:29:21this computer is susceptible to this vulnerability, put it in a box, and then when we're ready to actually
00:29:25go and perform the attack, we pull that recon information out and then we start formulating
00:29:30an actual plan. That's what they're alluding to there. And then reconnaissance target range may
00:29:35include the target organization's clients, employees, operations, networks, and systems.
00:29:40Again, social engineering is a big one here. And then we have a couple of reconnaissance types. We
00:29:45have passive and active. Passive reconnaissance involves acquiring information without directly
00:29:50interacting with the target. For example, searching the public records of news releases. So you just read
00:29:56the news and you gain information that way there's no way they could possibly know that you have that
00:30:01information and that you're starting to form a plan of attack, right? So technically that's true,
00:30:06but the government might know that, hey, somebody's reading this, you know, Al Jazeera news or something
00:30:10like that, right? And then active reconnaissance involves interacting with the target directly by any
00:30:17means. So for example, telephone calls to the help desk or technical department or actually touching their
00:30:22network is typically what it involves in some way, shape or form. Touching the network could be a
00:30:27phone call. It could be touching the wires on their network, snooping, scanning their appliances, things
00:30:34like that. So now we're going to get into scanning, which is separate from recon. So scanning is an active,
00:30:44not a passive thing, right? So we have a pre-phase attack. Scanning refers to the pre-phase attack when
00:30:50the attacker scans the network for specific information on the basis of information gathered
00:30:55during reconnaissance. So we use the information we got during reconnaissance and then we start
00:31:00scanning those hosts to look for vulnerabilities and different little issues that we want to
00:31:04identify. Scanning can include the use of dialers, port scanners, network mappers, ping tools,
00:31:11vulnerability scanners, etc. So what are all these things? Dialers are referring to the old telephone
00:31:17dialers looking for companies that still have modems that answer on their networks. Like for example,
00:31:26AOL still has the huge array of dialers in their networks. So they can have dial-up phones that will
00:31:33listen for when your stuff calls, they'll answer. You may find these on larger companies like IBM,
00:31:38for example, still has dialers around. And you may be able to exploit those because they may have been
00:31:43forgotten or left off the big security plans of today and then they're easy back doors and people
00:31:49don't tend to monitor them because they don't understand them. Then we have network mappers.
00:31:54So you're building a network footprint of their network so you know what it looks like.
00:31:58We have ping tools so we can ping their network, do ping sweeps and that kind of information.
00:32:04These don't generally work so we have a LAN and then we have the WAN. So this is our line. We have the
00:32:10LAN, the local area network and the wide area network. If you're using a ping tool, usually it
00:32:14won't work from the outside but it will work on the inside. Typically it's disabled on the outside
00:32:20the WAN port. And then we have vulnerability scanners. We're using tools to look for known
00:32:25published weaknesses in software. For example, in Windows, could be in Cisco, could be in Juniper,
00:32:31could be in Gigamon, whatever the technology is, could be Palo Alto networks. Attackers
00:32:36extract information such as live machines, ports, the status of those ports, the operating system
00:32:45details, what version of telnet are we looking at, what version of FTP, what version of SSH,
00:32:51what version is the web server, device types, system uptime, how long has this thing been up and
00:32:58running, etc. We gather all this information before launching an attack.
00:33:02So the hacking phase is gaining access. So now we're going to talk about gaining access to the
00:33:08system. So we've done our recon, we've done our scanning and now we're going to gain access.
00:33:12So gaining access refers to the point where the attacker obtains access to the operating system
00:33:16applications on the computer or the network. And the attacker can gain access at the operating
00:33:24system level, the application level or the network level. So there's a lot of ways you can get into a
00:33:29company, a wide surface. And then an attacker can escalate privileges to obtain complete control
00:33:34of the system in the process. Intermediate systems that are connected are also compromised. So I gain
00:33:40one thing, then another, then another, then another. We knock them down like dominoes, right? And then
00:33:44examples include password cracking, buffer overflows, DOS, which is denial of service, session hijacking,
00:33:51etc, etc. So maintaining access. So we've reconned, we've done scanning. Now we've gained access to a
00:33:59system. Now we want to maintain that access. What we call persistence, right? So we want to main
00:34:08maintaining access refers to the phase when attacker tries to retain his or her ownership of the system.
00:34:14So attackers may prevent the system from being owned by other attackers by securing their exclusive access
00:34:19with backdoors, rootkits, or Trojans. And there's different types of each one of these and we'll
00:34:24talk about them later when we get into those detailed sections. So we'll define them later what they are.
00:34:30Rootkits dig into the system in certain ways and then Trojans do certain things. All of these are very
00:34:35serious problems.
00:34:49So attackers can upload, download, or manipulate data applications and configurations on their own
00:35:08systems. So once they have ownership, a lot of problems can ensue from there, especially if they've
00:35:15been there a while. Can you imagine if you're a software company and you've been owned by China
00:35:21for 10 years or even all you can go back and say is, well I know they've been here for a year but
00:35:26that's all we know. Imagine the repercussions that will stem from that. Who have you sold software to
00:35:31in the last year, right? And say you're a Fortune 500 and you've got to go to those companies and say,
00:35:37um, sorry we've been owned for the last year and there's been back doors. Man, can you imagine that?
00:35:44Can you see how serious security is for a problem? For just a small software vendor, right? Maybe you
00:35:50don't care. Maybe, you know, you're like, well we didn't say that it was free from defect, right?
00:35:55But then they're still going to sue you. So you're still going to have to be dealing with a lot of fallout.
00:36:00So security is an important thing.
00:36:02So you have to do what's called due diligence, which we'll get into that and talk about that later.
00:36:08So attackers use the compromised systems to launch further attacks. So they could be into
00:36:11other organizations in the case of a software company or other systems that you own on your own
00:36:16network. So clearing your tracks. Covering your tracks refers to activities carried out by an attacker
00:36:23to hide malicious attacks. So first of all, we've done the recon, we've done the scanning, we've gained
00:36:28access to a system. Now we've installed persistent access and now we want to go ahead and clear our
00:36:33tracks, right? So we want to hide the malicious acts that we've done so far so that people can't tell
00:36:38what we did, when we did or, you know, how long we've been doing it. So the attacker's intentions
00:36:45include continuing access. We talked about persistence and then we talked about unnoticed and uncaught.
00:36:51So we don't want to raise our posture of getting caught by leaving stuff in the logs one night on the
00:36:57weekend. A security engineer happens to be drinking at home and he's like, Hey, let's go check out the
00:37:02logs. And we're going to be just kind of trolling our logs or something, right? I'm not promoting
00:37:06doing that while you're drinking. I'm just saying this is something that's not uncommon. And then
00:37:12all of a sudden he notices, Oh, that doesn't look right, but it never got caught before. It didn't get
00:37:18caught by the SIM, didn't get caught in previous trolling, but now all of a sudden he's caught it.
00:37:23So now he's onto you. So you want to erase that kind of stuff from the logs. When you're an attacker,
00:37:28they do this routinely. That's one of the first things they'll do. And then that's why we're going
00:37:32to get into log shipping and stuff like that later. Um, you want to take a copy of your logs or there's
00:37:38ways you can do it. It's shipping. You do it, you log in batches and then you ship those batches off,
00:37:43or you can log and then have a transactional log. So when you're shipping it off over here,
00:37:48it's a dead drop. It's only a one way, right? Nobody can get in there and delete that stuff,
00:37:52right? Then you've got a back channel to access that. Hopefully that's secured very well.
00:37:58Then you can have an unadulterated log. So that prevents this kind of thing of clearing the tracks,
00:38:04right? So we're talking about offensive strategies and defensive strategies. Okay. So
00:38:10we're talking about both sides of the fence here. The attacker overwrites a server system logs
00:38:14applications to avoid suspicion. It's not really suspicion. It's detection period, right? So,
00:38:23but for the test, we overwrite logs to avoid suspicion. Okay. And attackers always cover their
00:38:30tracks to hide their identity. So this is one way that they'll cover their tracks to hide what they
00:38:36did. It doesn't necessarily or unnecessarily hide their identity, right? So this is a little bit,
00:38:42I have a lot of problems with the stuff in these slides. So I tend to call them out. My apologies
00:38:46for that. It irritates me when they do this kind of stuff, but it's not necessarily hiding their
00:38:50identity. They're just trying to cover their tracks of what they did, right? They may or may not care
00:38:55about their identity. So usually there are many hops away from the system. They're not directly accessing
00:39:00it from that last hop. So for example, if I'm accessing this from my office or my home office at home,
00:39:07so I'm accessing this from home, I'm not going to break into the system from my house and then you
00:39:13can directly come back to my house. It's not what people do. There are many, many hops away, including
00:39:18other countries. So good luck getting warrants for that. It's difficult for them to do for people that
00:39:22know what they're doing, right? So the hops where they're coming from are not so important. They may let
00:39:28you know that they may not hide that at all, but what they do hide is what they're doing in the system.
00:39:34So I may leave a trail of log data that's going to take you on a wild goose chase too.
00:39:40So you want to validate, don't get too excited. Just work the problem, work the problem. What are
00:39:45they telling you? What are they not telling you? That kind of stuff. So it's not uncommon to find false log
00:39:50entries as well.
00:40:03Okay, now we're going to talk about ethical hacking concepts and scope. So this is module four
00:40:22of this section. So ethical hacking focuses on simulating techniques used by attackers to verify
00:40:28the existence of exploitable vulnerabilities in the system security. So we're going to focus on
00:40:34simulating techniques used by attackers to verify the existence of exploitable vulnerabilities in the
00:40:40system security. Ethical hackers perform security assessment of their organization with permission of
00:40:47concerned authorities. So ethical hackers perform security assessments of their organization with
00:40:53permission of concerned authorities. So you don't get permission from someone that's concerned about
00:40:59it. You get permission from the owner of this thing. Okay. So again, this definition is a little bit
00:41:04off, but for the test, just remember this is the answer. But in real life, you don't get permission from
00:41:10someone that's concerned about security. Okay. That's not good enough. You need to get permission from the
00:41:15owner, the responsible person of that person responsible for that system.
00:41:21Why ethical hacking is necessary? To beat a hacker, you need to think like one. Ethical hacking is
00:41:27necessary as it allows counterattacks from malicious hackers by anticipating methods used by them to break into
00:41:33systems. Reasons why organizations recruit ethical hackers. They use it to prevent hackers from gaining access
00:41:41to organizations information systems, to uncover vulnerabilities and systems and explore their
00:41:46potential as a risk, and to analyze and strengthen an organization's security posture, including policies,
00:41:52network protection, infrastructure, and end user practices. So this is why it's necessary.
00:41:59So it's also necessary because you need to understand your enemy and to understand your enemy, you need to
00:42:05know how they think and what they know. So that's why it's important that you learn these techniques and tools.
00:42:10So ethical hackers try to answer the following questions. What can the intruder see on the target
00:42:16system? Reconnaissance and scanning phases, right? What's visible to them? What can they see?
00:42:22What can an intruder do with that information? Gaining access and maintaining access phases.
00:42:27Does anyone at the target notice the intruder's attempts or successes? Reconnaissance and covering
00:42:32tracks phases. If all of the concepts of information are adequately protected, updated, and patched,
00:42:37like do they notice that? You know, if they are updated and patched, did they notice it?
00:42:42Okay. So how much in time and effort and money is required to obtain adequate protection? Is it
00:42:47something we can easily protect or is it going to take a lot of work and resources? Something we may
00:42:52or may not be able to afford. Are the information security measures in compliance to industry and legal
00:42:59standards? So skills of an ethical hacker. Technical skills, has in-depth knowledge of major operating
00:43:06systems such as Windows, Unix, Linux, and Macintosh. Has in-depth knowledge of networking concepts,
00:43:11technologies, and related hardware and software. They should be a computer expert adept in technical
00:43:17or at technical domains. So this already goes to show you where you are now. If you're struggling
00:43:24with this, you probably need to go back and learn a lot more stuff, right? To make you very successful
00:43:30in this field. So, or you can OJT it, but it's better if the more experience you have, the better,
00:43:36right? So they have knowledge of security areas and related issues. They have high technical knowledge
00:43:43to launch sophisticated attacks. And the non-technical skills of a certified ethical
00:43:49hacker or an ethical hacker. Some of the non-technical characteristics of an ethical hacker include
00:43:56the ability to learn and adapt new technologies quickly. So you want to understand a theory so
00:44:01that when new stuff comes out, you're like, oh, okay, I get it. Strong work ethics, a good problem
00:44:06solving and communication skills. Committed to organization security policies. So you want them
00:44:15to be on board and to follow your security policies, right or wrong. Awareness of local standards and laws.
00:44:21And now we're going to get into information security controls. So IA, information assurance. IA refers to
00:44:31the assurance that the integrity, availability, confidentiality, and authenticity of information
00:44:37and information systems is protected during usage, processing, storage, and transmissions of information.
00:44:43So all phases of data of the data life cycle, right? That's what they're alluding to here, the data
00:44:48lifecycle. Some of the processes that help in achieving this information assurance include
00:44:54developing local policy processes and guidance, designing network and user authentication strategies,
00:45:01identifying network vulnerabilities and threats, identifying problems and resource requirements,
00:45:07creating a plan for identified resource requirements, and applying appropriate information
00:45:13information assurance controls, performing certification and accreditation, providing information
00:45:19information assurance training.
00:45:34So information security management programs establish a combination of well-defined policies, processes,
00:45:55procedures, standards, and guidelines to establish the required level of information security.
00:46:00So there's a complex thing going on here that you'll learn about in CISSP,
00:46:07an overarching program, and we're just one little piece of that program. A CEH doesn't fit too well in
00:46:13one little box, right? There's going to be a lot of overlap. You're going to be working in compliance,
00:46:18governance, policies, and securities, all these different sections. So this is going to discuss the
00:46:25management framework, right? That's what they're alluding to here. But understand there's a lot of different
00:46:31pieces where you're going to play. So threat modeling. Threat modeling is a risk assessment approach.
00:46:40It is a risk assessment approach for analyzing security and applications by capturing, organizing,
00:46:46and analyzing all of the information that affects the security of an application.
00:46:51So you want to identify the security objectives, which helps to determine how much effort
00:46:56is needed to put on subsequent steps.
00:47:01An application overview. So we started out with identify security objectives, application overview,
00:47:07and then we're going to go to decompose the application, identify threats, and identify vulnerabilities.
00:47:12So we talked about the identify security objectives, but once again that's in determining how much effort
00:47:17is needed to put on subsequent steps, right? Where do you want to spend your energy and resources?
00:47:25And then the application overview. Identify the component, the components, the data flows, and trust
00:47:30boundaries. And something else that they're leaving out of here is something called a data gate as well. You want to
00:47:36identify where your data gates need to go. We'll talk about that later. And then we want to decompose
00:47:43the application. They help you to find more relevant and more detailed threats. So you want to find more
00:47:50relevant and more detailed threats. And then you want to identify those threats. So identify threats
00:47:55relevant to your control scenario and context using the information obtained in steps two and three. So you
00:48:01might find stuff that's more relevant to you than another team might find and something else that's more relevant to them, right?
00:48:09So identify vulnerabilities. Identify weaknesses related to the threats found using vulnerability categories.
00:48:15So you want to identify these vulnerabilities.
00:48:21Enterprise Information Security Architecture, EISA. Enterprise Information Security Architecture. EISA is a set of requirements,
00:48:28processes, principles, and models that determine the structure and behavior of an organization's information systems.
00:48:35The goals are, one, to help in monitoring and detecting network behaviors in real time, acting upon internal
00:48:43and external security risks. Number two, helps an organization to detect and recover from security breaches.
00:48:49Number three, it helps in prioritizing resources of an organization and pays attention to various threats.
00:48:55Number four, benefits organization and cost perspectives when incorporated in security provisions such as incident
00:49:03response, disaster recovery, event correlation, et cetera, et cetera, helps in analyzing the procedure
00:49:10needed for the IT department to function properly and identify the assets. So number six, it helps to perform risk
00:49:18risk assessment of an organization's IT assets with the cooperation of its IT staff. So it's going to help to
00:49:25perform the risk assessments of an organization's IT assets with the cooperation of the IT staff.
00:49:31So those are the six steps of the Enterprise Information Security Architecture.
00:49:37Network Security Zoning. Network Security Zoning mechanisms allow an organization to manage a secure network
00:49:43environment by selecting the appropriate security levels for different zones of interest and intranet
00:49:50networks. It helps effectively monitoring and controlling inbound and outbound traffic.
00:49:55So this is zoning, right? So we have different zones. So let's talk about the different zones.
00:49:59So here are a couple of examples. You have an internet zone, an uncontrolled zone and is outside the
00:50:04boundaries of the org. You have the internet DMZ controlled zone as it provides a buffer between the internal
00:50:10networks and the internet. And you have a production network zone. Restricted zone as it strictly
00:50:17controls direct access from uncontrolled networks or you hope it does. In most cases it won't be a strict
00:50:25control but you have some control. You have more control than you do over the DMZ. And then intranet zone,
00:50:31controlled zone with no heavy restrictions. So intranet zone, controlled zone with no heavy restrictions.
00:50:38So for example, accounting to marketing. You don't have as many controls between those two
00:50:45groups. And then you have a management network zone. Secured zone with strict policies. So you have a
00:50:51management zone where you have access to certain things but you can't read everyone's mail, right?
00:50:56You might be able to read most of the company's mail but not everyone's, something like that.
00:51:00And then I wanted to go back to one of these restricted zones, uncontrolled networks. So the production network
00:51:06zone. In real life, that's not really a fair definition. For example, the one difference
00:51:12might be between the internet and the production. You may not have direct, strict access control.
00:51:20You may have some access control. You may be doing some URL checking and validation. But on your internet
00:51:25DMZ zone, you're going to do a lot less of that because, for example, you might want to allow people
00:51:30from Russia to hit your web server. You might want to allow people from China to hit it. But in your
00:51:34production network zone, you may not allow that kind of thing, right? So there's a little bit of a
00:51:38difference. You may not allow communication to Russia or China at all. So that might be one example.
00:51:44For example, like Netflix. Netflix won't allow, they'll allow you to access their servers from
00:51:49overseas but you won't actually be able to play a movie unless you're on a VPN. So that's one example.
00:51:56The internet DMZ won't allow overseas consumers to access the movies on their service yet. I think
00:52:06they just started one company. But their production network zone, the salespeople might be spinning up
00:52:10a project where they're already starting sales. So in that case, it might be the opposite. They allow
00:52:14it in the production network zone, but not in the internet DMZ. So those are just two kinds of examples.
00:52:44Information security policies. Security policies are the foundation of security infrastructure.
00:52:51They are their procedural controls. The management says this is what the rules are and we have to play
00:52:55by those rules and everything should be enforcing those policies. And that's what they mean by it's
00:53:00kind of a foundation of security infrastructure, right? It's kind of the basic premise for where
00:53:04all the rules come from or it should be. So information security policies define the basic security
00:53:10requirements and rules to be implemented in order to protect and secure organizations information systems, okay?
00:53:17So the goals of the security policies,
00:53:20we want to maintain an outline for the management and administration of network security.
00:53:26We want to protect an organization's computing resources.
00:53:30We want to eliminate legal liabilities arising from employees or third parties.
00:53:35We want to prevent waste of a company's computing resources and we want to prevent
00:53:40unauthorized modification of the data. We want to reduce risks caused by illegal use of system
00:53:45resources. We want to differentiate the user's access rights. So make sure that not everybody has the
00:53:52same rights. We want to be able to control those and then protect confidential proprietary information
00:53:57from theft misuse and unauthorized disclosure.
00:54:02So we have several types of security policies. We have a promiscuous policy,
00:54:06a permissive policy, a prudent policy, and a paranoid policy. I guarantee you, you will see a test
00:54:12question off of this slide on the test. No restrictions. Which policy is that? A promiscuous one.
00:54:20So a promiscuous policy has no restrictions on usage of system resources. You can use it for whatever you
00:54:26want. And then a permissive policy begins wide open and only known or dangerous services attacks or
00:54:32behaviors are blocked. So as you identify things like, Hey, we're going to start off with this list
00:54:37of blocking, but for the most part, we're going to let people do what they want to do. And as they
00:54:40abuse it, as we identify things, we'll go ahead and start locking it down. So it should be updated
00:54:45regularly to be effective. So it's kind of a constant feedback loop. Hey, you know, these people keep
00:54:50going to this porn site and we keep getting malware from this porn site. So let's go ahead and start
00:54:54blocking the porn sites, right? That's kind of how a permissive policy works.
00:54:58A prudent policy. It provides maximum security while allowing known but necessary dangers.
00:55:06So you kind of manage your risk. We know we have some risk and here's the list.
00:55:10And that's the only thing that we allowed in are these specific risks. We know about them
00:55:14and we're managing them. It blocks all services and only safe necessary services are enabled
00:55:20individually. Everything else is logged. So it's the opposite of the promiscuous policy. The promiscuous
00:55:26policy allows everything, right? Actually, I guess it's the opposite of our permissive policy.
00:55:33So the permissive policy starts wide open and then they close it as they need to. The prudent policy
00:55:41starts out completely closed and then they only open what they have to open. So there's the
00:55:47permissive and the prudent. Those are opposites of each other. And then there's the promiscuous
00:55:52and the paranoid. The paranoid forbids everything. No internet connection or severely limited internet
00:55:57usage. So the paranoid is kind of the opposite of the promiscuous. So there's four policies there.
00:56:04Promiscuous, permissive, prudent, and paranoid. You need to know these and you need to understand the
00:56:09differences between them. So let's get into some examples of security policies. We have an access
00:56:16control policy. It defines the resources being protected and the rules that control access to
00:56:21them. We have the remote access policy. So that's for people that are accessing our systems and computing
00:56:27resources remotely. Here's the rules that apply to them. Firewall management policy. It defines access
00:56:33management and monitoring of firewalls in the organization. The network connection policy. It defines
00:56:39who can install new resources on the network, approve the installations of new devices, document network
00:56:45changes, et cetera, et cetera. So that's an important one, right? Hey, I want to put this new security
00:56:49policy in. I mean this new security appliance in. Whom do I talk to about that? So you can go reference
00:56:54that information probably likely right out of the policy, right? Or some addendum to it. Passwords policy.
00:57:00It provides guidelines for using strong password protection on organizations resources or gives you
00:57:05at least what the definition is. You need to know what it is, right? You need to know what it is for vendors
00:57:10and stuff like that. You can't just go and arbitrarily change a password policy. That would impact
00:57:14thousands of systems potentially in any decent sized organization. So user account policy. It defines the
00:57:21account creation process and authority rights and responsibilities of user accounts. So user account
00:57:27policy. Information protection policy. It defines the sensitive levels of information. Whom may have
00:57:34access. How is it stored and transmitted? And how should it be deleted from storage media? So the full data
00:57:40life cycle is addressed here, right? Information protection policy. From birth to destruction.
00:57:46And special access policy. This policy defines the terms and conditions of granting special access to
00:57:51system resources. So we have a short term project. We're going to do something out of the norm.
00:57:56We're going to use a special access policy. Email security policy is created to govern the proper usage of
00:58:01corporate email. So from soup to nuts about the email. An acceptable use policy, an AUP. Acceptable use policy.
00:58:10A-U-P is how you'll see it abbreviated all the time. You might even see that on the test. So keep
00:58:14that in mind that this could be a test question. The AUP says what? And your answer would be,
00:58:19it defines the acceptable use of system resources. AUP is acceptable use policy.
00:58:40privacy policies at the workplace. So employers will have access to employees personal information
00:58:57that may be confidential and that they wish to keep private. So the basic rules for privacy policies at
00:59:03work are as follows. Inform employees about what you collect, why, and what you will do with it.
00:59:10Limit the collection of information and collect it by fair lawful means.
00:59:15Inform employees about the potential collection, use, and disclosure of personal information.
00:59:21You want to keep employees personal info accurate, complete, and up to date. Provide employees access to
00:59:27their personal information and keep employees personal information secure.
00:59:34Steps to create and implement security policies. So the following is going to be all about protecting this
00:59:41employee workforce data.
00:59:47So steps to create and implement security policies. Perform risk assessments to identify risk to the
00:59:53organization's assets. Learn from the standard guidelines and other organizations. So there's a
00:59:58lot of best practices and things of this nature. So you could just search for best practices on whatever
01:00:04it is you're trying to do. Best practices for firewalls, best practices for protecting data, stuff like that.
01:00:12PCI guidelines, for example, may be relevant. You know, this is what they're getting at there.
01:00:16PCI is the payment card industry. There's also HIPAA, the Hospital Information Privacy Protection Act.
01:00:25And then number three is include senior management and all other staff in policy development. So get
01:00:30all of the input from all the relevant people along the workflow path. Socializing this early will help
01:00:39them understand the whys and the hows. And if there's questions, you can get them out of the way. You might be
01:00:44able to circumvent issues that will come up right off the bat. You want to set clear penalties and enforce them.
01:00:51Make a final version available to all staff in the organization. And they actually have to sign it,
01:00:56which they're going to talk about in six. So ensure every member of your staff read, sign and understand
01:01:02the policy. And that understanding the policy is a key one. So if you don't offer as an organization,
01:01:08if you don't offer any training to them, then that's going to be a problem, right?
01:01:12So this isn't specific for certified ethical hacking, but these are things that they need to understand,
01:01:16right? So these are things that you need to understand. You know, you need to know what these
01:01:20policies are. Why? So that you can, when you're doing your security assessment, you can include
01:01:26this kind of thing. Are they enforcing the policies they have in place? That's why this is relevant to
01:01:31you. So don't tune this out. So they also want to deploy tools to enforce policies. Now that's where you
01:01:37come in, you're going to be testing these tools, right? You want to train your employees. We talked
01:01:41about that, educate them about the policy and have proof, have them sign off on attendance sheets,
01:01:46that kind of thing. And you want to regularly review and update the policy. So every time you
01:01:50come back to do a follow on assessment, you know, there's a security assessment versus a penetration
01:01:56test. Penetration test is just trying to break into the network and maybe pivot, see what you can get
01:02:00into. A security assessment is everything. It takes everything into account. Are they enforcing the
01:02:05policies? If we're just doing a penetration test, we may not care if they're enforcing the policies.
01:02:10We're only getting paid to breach the network. Let them figure out what to do with the information,
01:02:14right? So HR legal implications of security policy enforcement. So HR implications of security policy
01:02:24enforcement are as follows. The HR department is responsible for making employees aware of security
01:02:30policies and training them and the best practices defined in a policy. So this also insinuates that in your
01:02:38policies, you better be pushing best practices, right? Which is absolutely what you should do. There's
01:02:44something called due diligence that you need to adhere to. If you haven't heard about that yet, you'll hear
01:02:48about it a lot, especially in this class. Due diligence is an important thing. HR departments work with
01:02:55management to monitor policy implementation and address any privacy or policy violation issues.
01:03:02So they will help figure out what the penalties are, whether or not the person is going to be
01:03:06terminated or not, that kind of thing. The legal implications of security policy enforcement.
01:03:11Enterprise information policy should be developed in consultation with legal experts, so your legal
01:03:17teams at the company, and must comply to relevant local laws. Enforcement of a security policy
01:03:23that may violate the user's rights in contradiction to local laws may result in lawsuits against the
01:03:30organization. So you don't want to stray from the formula, just kind of follow the best practices. What do
01:03:35most people do? Physical security is the first layer of protection in an organization. So you have to
01:03:42have physical security, security guards, turnstiles, man traps, whatever is mandated by the organization's
01:03:48security posture, right? Whatever defense condition they want to maintain. And this involves protection of
01:03:53organizational assets from environmental and man-made threats. So what if somebody smash and grabs
01:03:5820 laptops? Are they encrypted? Can you remote wipe them? That kind of thing. Can you tell where they
01:04:05are? Can you go and if somebody nukes it and reinstalls the OS, can you self-heal it? That kind of thing.
01:04:12There's software out there to help do that on like some manufactured laptops, a popular brand.
01:04:18So to prevent any unauthorized access to the system resources. So these are the reasons why we want
01:04:24to have physical security, right? So why physical security? To prevent any unauthorized access to
01:04:29the system's resources. So that's keeping them out of the building altogether, right? So there's no way they
01:04:35can get to the laptop unless they smash the glass. And then if they do, what are they going to get?
01:04:40So your laptops, you may have a policy that requires you to turn them off so that the encryption keys for
01:04:47the hard drive can't be snatched out of the memory. This is an important thing. Another thing is that
01:04:54with related to physical security, for example, is if you have something in the trunk of your car and
01:04:59it's beaconing for wireless, that's detectable. People can pop the trunk and grab your laptop.
01:05:04Number two here is to prevent tampering and stealing of data from the computer systems,
01:05:09to safeguard against espionage, sabotage, damage or theft. So if you're writing software,
01:05:14this may be very valuable to someone. If they're after one of your customers,
01:05:18for example, it's a popular thing these days.
01:05:21And also to protect personnel and to prevent social engineering attacks.
01:05:32So if I get your laptop and I have your email, I can see how you're talking, what you're saying,
01:05:35these kind of things. And in a couple of months after you've recovered and this has kind of gone
01:05:39away, then I can start using my social engineering skills to go and attack the people that you're
01:05:45interacting with. And physical security threats, we have environmental threats like floods, fires,
01:05:50earthquakes, and dusts. You know, just dust in general could cause problems to your server
01:05:56environments. And then we have man-made threats like terrorism, wars, explosion, dumpster diving
01:06:02and theft, vandalism, this kind of thing. Everybody's after copper these days. So if you have a data
01:06:06center that's not manned, people may go and mess with that facility. So you want to make sure you have
01:06:11good security there, cameras, that kind of thing.