9 hours 49 minutes
having a good vulnerability assessment program leads into pen testing. Usually vulnerability assessments come early in a pen test, but we offer consider them to be two separate activities.
The idea with the vulnerability assessment is re collecting information and looking for known weaknesses. Do you have ports open to have weak passwords? Do you have a system that is in patched? That's the type of stuff that a vulnerability scan would do for you
Now Microsoft is a tool called Microsoft Baseline Security Analyzer that will scan a system or a range of systems. Looking for those types of weaknesses is not active.
It's going to document weaknesses for us. But there's no attempt to exploit the weaknesses or compromise a system.
That's where vulnerability, analysis or assessment ends gathering information.
The next step is often to try to take those vulnerabilities and exploit them. Can I compromise the system through those weaknesses? A vulnerability assessment might say you have Port 80 Open doesn't mean I can exploit. That doesn't mean I can inject malicious code throughout Port 80. That's the next step in a pen test
with penetration testing. We're never trying to break something. Sometimes we break things really important before you start a vulnerability analysis or a penetration test that we get approval and sign off from our senior management.
That's something known as a get out of jail free card, because what we're doing with vulnerability, assessments and exploitation is a hacking our network.
It is only ethical hacking if we have permission, so we want to make sure that we do.
That exploit takes things in the next step.
The way I want you to think about it is if you know if you're in compliance with policy, you audit.
If you want to know if there are any weaknesses, a vulnerability assessment.
If you want to know if you're capable of withstanding an attack, that's your pen test. That's the information a pen test will give you.
We've got steps for penetration testing.
This assumes that the Attackers coming from the outside, that they have no internal knowledge of the environment. But they're just trying to mimic an external attacker.
We started with gathering information. Usually that's from the Internet.
For most organizations, there's quite a bit of information out on the Internet.
Can I figure out what your locations are? Your principal officers. Can I find enough information that maybe I could use a social engineering attack to get on the network?
The next thing is the threat model.
With penetration testing, we investigate, get our information about a system, then try to figure out from an attacker's perspective what the most appealing things are.
You sat there at the class. Certain servers are very appealing to us, like a DNS server or domain controller, because those are so powerful in the network.
When we're doing the pen test, we try to think like an attacker.
What are the threats that are most likely to materialize?
Then we're going to scan for those threats with their vulnerability analysis and try to exploit them
after the exploit. Whether it's successful or not, document lessons learned. What did we find? What worked, What didn't work. We take that information and formalize it, then reported to our senior management
penetration. Testing really does start off with a vulnerability analysis, then moving up to an exploit phrase.
The ultimate goal here is to determine if we can withstand an attack.
We have to conduct pen testing on a regular basis. Because of that landscape is always changing.
Wrapping up this section on access control
the first and what I think is the most important step to security segmentation
isolating your most trusted resources from less trusted entities. Make sure that untrusted going back
make sure that untrusted entities can't access what you want to protect.
If untrusted entities need access to what you're trying to protect, then force them through a firewall or some other interphase that inspects their activities.
We can segment, and we can have a subset of our network, a DMZ.
We can use different subnets using a router. Subnets can be created with the villain a virtual Elian on a switch as well.
We isolate our traffic
now user accounts we control who has privileged accounts. We review those user accounts for too much permission and privilege and make sure we're following those ideas of the principle of least privilege and need to know
we use access control lists of our resources, but also on our firewalls on our filtering devices, so that if we set, if that and logic,
if traffic appears this way, then block it. If traffic appears that way, then allow it.
You specify our rule sets when we're looking to block or allow
honey pots. Are detective there for use after an attack has come into the DMZ, perhaps, and they're looking for a system to attack, and the honeypot looks very desirable.
Then afterwards, I go back and review the logs, and I get that additional information about the attacker
then. Last but not least, penetration testing usually begins with that vulnerability. Assessment collects information that's then used to try to explain the weaknesses.
Then, of course, after the pen test, after the exploit, we document what we found and we present that information to senior management.
I will mention at no point in time does a pen tester correct problems that they found the simply document
that wraps up our Chapter six. We talked about physical security and to never underestimate the importance of physical security in your environment.
Security guards, door locks, controlling access to and from the building with swipe cards or other devices, Physical security is always going to be important.
Then we looked at using single sign on and authentication something. You know something? You have something you are.
We also said you can use somewhere you are something you do But what's most important about authentication is that we require multifactor authentication
you authenticate with more than one type
We talked about. How desirable single sign on is simply because it alleviates some of the effort users have to keep up with. To keep up with numerous passwords
makes it easier for the administrator because there's a single password database that they control.
They have a single point of authentication policy
and winds up working well for both users and administrators. But don't forget those ideas of keys to the kingdom in case those credentials are compromised
for authentication. We looked at network authentication with Kerberos, then authentication with Federated Trust with S A. M. L or open ID connect.
We reference some ideas with wireless security, like rogue wireless devices, rogue access points and evil twins.
We then looked at common attacks like denial of service, logic, bombs and man in the middle attacks.
Finally, we wrapped things up with access, control and hardening our devices services. To make sure that we have access to these resources is very difficult to obtain.
That wraps up Chapter six for us. We're almost to the end. We come in with chapter seven right after these messages.