13 hours 9 minutes
Hello and congratulations on completing the post exploitation section of the penetration testing execution standard. So what should we have learned so far? Well, we looked at the purpose of post exploitation and we discussed what it was and what it was not.
We looked at the rules of engagement again to ensure that we understood what those were in the post exploitation phase
protecting your client as well as protecting yourself, making sure that we don't do any home and that we keep the rules of engagement in mind when we're working with our client
infrastructure analysis where we discuss network configurations such as interfaces rounding the N S servers catch Dean EST entries and discussing network service is overall helping us to further map the network and find areas that we can attack. We then discuss pillaging, which covered a multitude of things such as programs,
service's database, servers, directory service and service's deployment Service's virtual ization messaging, monitoring and management applications and Softwares.
On service is backup systems. Networking service is sensitive data, user information and system configurations. Remember with any pillaging,
ensure that any data that you would be taking off site is discussed with the client, and they understand where that is going and you know what you should and should not be touching. We discussed high value such profile targets, discussed what they were, why they should be sought and why we should take precautions with them and how we take precautions with them.
These could be things like executives, upper management,
payroll servers and things of that nature that could be detrimental if a client were to lose that system or have it damaged. We talked about data exfiltration and looking at how we map out possible ex filtration paths, testing those paths and measuring control strengths
such as response time and whether or not data loss prevention systems actually keep you from expel trading data.
We looked at persistence mechanisms like back doors and ah, few examples of those like alternate channels and root kits. We looked at the installation and or modification of service is discussed, creation of accounts and in all of this, making sure that we used secure credentials and best practices. When setting these things up,
we looked at system pivoting toe, help us further get into the infrastructure of the organization we looked at from compromise system pivoting and through compromise system pivoting both of which, at any given time, you should have a meeting with the client to determine if certain goals have been met that they set out to meet at the beginning of testing.
Cleanup is a must for any engagement. That's why we touched on it last. And so we clean up because we want to leave the client network in a better state than we found it. We do things like remove accounts, binaries and Softwares that we put in place. And by doing so, we ensure that the client is not accidentally compromised because of our
leaving of these things or negligence.
So congratulations again. And with that in mind, I want to thank you for your time today, and I look forward to seeing you again soon.
Exploitation and Mitigation: MSHTML Vulnerability (CVE-2021-40444)
The MSHTML Windows remote code execution vulnerability (CVE-2021-40444) identified in September 2021 could allow a ...
2 CEU/CPE Hours Available
Certificate of Completion Offered
Kali Linux Fundamentals
If you’re interested in penetration testing and ethical hacking, then this Kali Linux course is ...
1 CEU/CPE Hours Available
Certificate of Completion Offered