13 hours 9 minutes
Hello and welcome to another penetration testing execution Standard discussion. Today we're going to be looking at Threat agent of community analysis within the threat modeling section of the Pee test standard.
So a quick disclaimer, any tools or techniques that we discussed during the pee test videos could be used for system hacking. And so anything that we demonstrate or discuss should be understood by the user and the user's should research laws and regulations within.
They're given regions or areas. While we're having fun learning or apply in this standard
to our penetration testing efforts, we want to ensure that we don't break any laws within our given area. So what are the objectives for today's discussion? Well, today we're going to discuss defining relevant threats and what that looks like.
We're going to discuss internal and external examples,
and we're just going to look a employees and management at a high level. This should be a brief discussion, and it's pretty straightforward with respect to what we're looking at. So defining relevant threats, okay, keyword relevant here
when defining the relevant threat communities and agents. A clear identification of the threat should be provided in terms of location, the specific community within the location. Okay, so the specific community and any additional relevant information that would assist in establishing
capabilities and motivation for that specific agent or community. And we'll talk about some of those motivators in a later discussion as well.
So when we look at internal external examples of threats,
this could be a way that you could lay this out and put it together again. If you've got a separate methodology or system that you use, please stick with it. But if not, this is a good starting point. So employees, whether knowingly or unknowingly, can be a threat to an organization
executive and middle management and administrators. So folks that have,
um, elevated access to systems
developers, engineers, technicians, contractors, you know, in those cases, if they've got external access, if they're outside of the network or if their internal, whatever the case, may be general user community. And so if you've got users within the network
and remote support definitely remote support for software applications and things of that nature. So these air folks that have knowledge of the organization
that are inside the organization day to day
and you know they could be motivated by different things. Or, you know, there could be again accidental exposure to malicious software. Or they could accidentally let it loose so they could do it on purpose if they're motivated by greed or if someone approaches them because they're in
financial crisis or if they become disgruntled.
You know, these are definitely
potential risks or threats to the organization.
Now. Business partners may not be internal to the organization, but they may have a say so in the organization that may have access to certain things they may have knowledge of the organization that could be used. Thio potentially cause harm competitors,
contractors These air contractors that aren't in the organization like internal to it day to day
suppliers because they've got intimate knowledge of the organization. They provide, AH, particular service or they protect provide a particular product. They could be a threat or a risk vector for the organization.
Nation states in some cases organized crime activists and script kiddies. These really depend on
whether or not you're a target for some of the larger nation states organized crime syndicates. But if you get some type of ransomware on a system, if you've ever fallen for any type of social engineer, and it's likely that you were a victim of one of these four categories.
So this is just again a high level way that we can map out threats on dhe kind of start to look at some of the different areas or vectors that could be of risk to the organization. When we look at employees specifically these air persons working directly for the company under a part time or full time contract of some sort.
In general, they're not regarded as posing a severe threat at a CZ. Most of them are relying on the company to make a living right, and, assuming they are treated well, they're inclined to protect the company rather than hurt it. You don't want to bite the hand that feeds on DSO. You're being treated well,
Most times you're satisfied with your employer. You want to protect your employees interests, and you know you work to elevate your employees.
So oftentimes, in data loss incidents, it's accidental in nature or the, you know on the laptop was stolen. It's typically not malicious now, in rare cases, they be in employees could be motivated by outsiders to assist in intrusion.
Oh, are they may engage in malicious acts on their own.
Um, while the skill level Mayberry, it's usually low to medium in the threat level, for for the folks like employees, it get disgruntled and try to attack the organization.
All of this includes executive management as well as middle management.
Now I would say that this is true for maybe an accounting firm or something of that nature, but I would think there would be an elevated level of risk to the organization for things like developers, administrators of systems, things that make nature. They could easily lock out a system or cause a lot of information to be misplaced
in one swoop based on level of access. And so I would consider those employees to be a
higher risk if they were ever disgruntled or engaged by 1/3 party that provided some type of gain or incentive for them to do so.
So let's step and do a quick check on learning. So true or false suppliers are considered potential internal threats win determining threat agents.
Well, as we discussed, suppliers are considered external parties, so they would not be considered an internal threat to the organization when determining threat agents. And so this statement, as provided, is false in nature. So suppliers air considered external parties that provides some type of good
service, et cetera, that aren't
day to day employee's contract and employees within your organization.
So in summary,
we discussed the relevant threats and how we define those. We looked at some internal external examples, and then we overall kind of discussed employees, middle and executive management. Their role as far as being a threat, is rather minimal,
even with employees who have elevated access it maybe mid tier at best. You know, hopefully, if you're treating employees well
and they're happy, then there's typically not a reason for them to go out and maliciously damage a system, destroy system or cause harm to the employer. So keep those things in mind when you're doing threat modeling. And again, if you've got a different process for laying those out or mapping those
my own means, use that. But if you don't have a place to start, that table is a pretty easy waited to start visualizing your threats, um, and risks to the organization. So with that in mind. I want to thank you for your time today, and I look forward to seeing you again soon.
Kali Linux Fundamentals
In this Kali Linux course you will learn about the industry standard tool for penetration ...
1 CEU/CPE Hours Available
Certificate of Completion Offered
How to Use SET (BSWR)
The Set or Social Engineers Toolkit is a commonly known open source framework available on ...
Certificate of Completion Offered