Time
13 hours 9 minutes
Difficulty
Intermediate
CEU/CPE
13

Video Transcription

00:00
Hello and welcome to another penetration. Testing execution Standard discussion. Today we're in pillaging part two of our post exploitation discussions. Now is a quick disclaimer. The Pee test videos do cover tools and techniques that could be used for system hacking.
00:17
So many tools discuss their used should be researched and understood by the user prior to their use.
00:23
And again please research your laws and regulations regarding the use of such tools in your given area to ensure that you do not break the law. Now, today's objectives are pretty straightforward and continuation of our first pillaging video. We're going to review backup systems. Network Service is sensitive data
00:41
user information review to cover things like on System's Web browsers and I am clients
00:46
and a review of system configurations. So all of this is going to help us to further understand how the network is laid out and what information we could then use to further exploit or move through our systems.
01:00
So back up systems are great because they usually are an agent or a piece of software with the purpose of backing up data, and it provides a great opportunity for the attacker for various things. It allows us to enumerate hosts and systems. Service is,
01:15
and we could potentially get credentials to host and or service's and access to backup data.
01:21
And in most cases,
01:23
folks do a few things. Depending on the environment. They could back up every system,
01:29
but in most cases they strategically backup systems and files because those would be considered critical and necessary to continue operations. And so this could also be a finding in that if you're able to access systems that air, having data sets backed up, I would review those data sets to understand what they are and what the value of those are to the organization.
01:48
Now we can also look at networking Service is like radius and attack us. So in this case, it would allow you to again enumerate users, enumerate hosts and systems, compromised credentials and show risk of denial of service if alternate methods are not present. And so
02:07
in this case, if radius were to be taken down or something of that nature, would you be unable to authenticate and do the things you need to do to operate and function?
02:15
Now getting into sensitive data, we can do some key logging now monitoring keystrokes. It is possible to detect sensitive information in P. I so don't know what the legality of this is. If the user is, say, Channing on private, I am on company time or software.
02:32
So I mean, if you're if you're an expert and, you know, let me know. But I'm assuming
02:38
that if there is no, um,
02:42
security policy on the use of company equipment and that the employees Earth has the right to monitor that activity, we could be in violation of some laws there. So if the company says that all data on the network could be monitored than it should be okay,
02:55
if the second bullet in protect yourself is present and it states that the use of equipment can be monitored and no personal use is permitted, Yes,
03:05
if the policy does not cover personal user Oh, our ownership of data, then no, I would not take the time to do key longing and things of that nature. So always ask those questions and ensure that key logging doesn't get you into any trouble now
03:20
on system information that we could gather history files could be great. So recent commands Maybe that had been executed. Reading through these can provide information on the system, data locations, other sensitive data, encryption keys or great interesting documents. So I looked for things like password dot
03:38
and then use a wild card there, and that will help you to maybe find password information that's stored on the system.
03:43
A specific application parameters are great and then individual application history that could be found on the system. Remember, we want to store passwords if we take any off the network or make a copy of something
03:57
we want to make sure we stored in an encrypted fashion. And any time we put that data in a report, it needs to be redacted and completely removed,
04:04
continuing with system configuration. Password policies were great because then we can understand the mental in length. And, um,
04:15
that will help us to understand whether or not we could do brute forcing effectively whether or not they force people to reset passwords etcetera.
04:21
And then if we can get our hands on wireless network information and keys, that could be great because then we could connect to a different segment of the networking, continue to get a new view of how things look and potentially get into other systems that we may not have been able to get to on the land network alone.
04:38
So let's do a quick check on learning. True or false key, logging can be a violation of the user's privacy, depending on the company's security policy.
04:48
All right, so yes, key Logan can be a violation of the user's privacy, depending on the company's security policy of the company. Policy clearly states that they could monitor information long information that they own all information. You should be good for the longing.
05:03
If it does not, and it allows for personal use on systems, then you may not want to do key logging. Always check with counsel
05:10
and ensure that you fully understand whether or not you'd be in violation of any laws. Here. Sochi Logan can be a violation of user privacy. Depending on the company, security policy is a true statement.
05:21
Now let's jump over to our summary. So we discussed backup systems and how those air beneficial we looked at. Network and service is sensitive data user information review coverings on system's Web browsers and I am clients, and we discuss system configuration
05:39
again, This is the tip of the iceberg, these air all touched on in the pee test standard.
05:44
But from the testing standpoint, if you're not covering some of these areas where you don't have a good check, let's list our methodology laid out for pillaging or what happens when you exploit a system.
05:54
It may be worth revisiting if the engagement ends, and it's just Hey, look, we got into the system and that's the end of it. Write the report,
06:00
then That is the way that that is. So with that in mind, I want to thank you for your time today, and I look forward to seeing you again soon.

Up Next

Penetration Testing Execution Standard (PTES)

In this course we will lay out the Penetration Testing Execution Standard (PTES) in all its phases and their application for business leaders and Security Professionals alike.

Instructed By

Instructor Profile Image
Robert Smith
Director of Security Services at Corsica
Instructor