ladies and gentlemen, welcome to post exploitation, persistence and continued access.
This is part zero. The introduction and I will be your host slash me slash best friend for the next eight hours or so.
not this. This is not me. This is, in fact, a goat. This, however, is me. There's my address
on the cyber ery dot i t website
where you can get a hold of me. Tell me how awesome this class was. Something terrible. It was asked questions, Whatever.
This is why we're here.
You want to do this? You want to be the overly hacks or who's stealing passwords and data obviously, completely legitimately. Because someone paid you to do it.
Preferably, you know, the company who you're stealing the data from, paid you to do it. Not like the mob or something like that. But you know, none of my business. I'm staying out of it.
So we're gonna start out learning about post exploitation. For those of you uncertain as to where exactly that falls. Post exploitation comes after exploitation. Pretty straightforward name.
You make your way into a system, you gain some sort of access to a system. You use that access to
get higher credentials, preferably root access. We're going to most of the stuff that we do here on the assumption that you have root access.
and then you start doing the interesting stuff. You start doing data analysis, you start doing network analysis, you start seeing what's going on on the network, see what data you can get ahold of.
Then you start putting in back doors. You start excell trading data. You start
dropping your own stuff.
Um so is to get the things out that you want. After that, you're going to actually start creating a means by which to re access a network
you're going to put in the actual backdoors. You're going to create the persistence mechanisms, whatever you might need to do to continue access, persistence and continued access is the goal, and that's what we're gonna do.
who is this class for? If you're here hoping to come a pen tester or if you want to learn about some interesting tools, this class is for you.
If you want to become a security professional, it's gonna give you a good idea of what the bad guys do or what the good guys who work for the bad guys do.
This is a very high level overview of the concept, and it's not for someone who's already a professional in the field.
You're going to be given a basic idea of how these practices work against a normal and user. You're not going to be learning how to assassinate an I. D. S or take down the CEO's machine or anything like that.
You're going to be learning how to actually
get data out, find out what data you're trying to get and then cover your tracks.
and then again, of course, what is post exploitation? The answer. That is pretty simple. Whatever comes after gaining access to the first machine, everything after exploitation is post exploitation by definition.
All right, first thing we're gonna start out with are your rules of engagement.
Simply put, if you don't have permission to do this,
Computer Fraud Abuse Act. It's ah, it's a hefty little piece of documentation, but it's worth the read.
Fines have reached several $1,000,000 for people who have broken the computer fraud and Abuse Act, and people have been awarded up to 50 60 years worth of jail time,
not dimensional. Besides all of that, it's kind of rude, you know, it's not your stuff. Don't touch it. Easy is that
expectations, permissions and all the paperwork.
You want to speak with your client, your customer Before you begin,
you're going to want, identify what they do and don't want you to do, and they're going to get it. On paper,
you're very often going to find yourself working in stir production network. And though the big red button that says self destruct is very shiny,
you're not going to want to press it.
Ah, a single hour of downtime for a company like Facebook can be millions or even billions of dollars when all things were said and done.
So they're going to be slightly miffed at you if you make that mistake. So I recommend against it
under the heading of protecting the client, we're gonna go through some quick things that you're gonna want to do before you actually start in on this. Unless you've previously agreed you're going to make no modification to anything they call critical.
The reason why you would want to do that would be to further escalate privileges on the network, to get access to specific data or to cause the dial of service.
All modifications, including configuration changes executed against the system, have to be documented.
Anything you do, write it down.
If you don't write it down, you didn't do it
or you didn't claim to have done it, and they're going to get mad.
That's a very detailed list of actions that you take should be kept.
It's not only done to protect you and say this is what I did It was all in line with what you said I should do. It's also so that when you're done, they can reverse what you've actually done.
Private and user data needs to be
in some way obfuscated or covered.
You're going on. Lee actually collect that
if you actually have permission from the client. The client Acceptable use policy states that this can be done,
and the client has confirmation that all of the employees understand that that's the case.
It's very, very dangerous to dig into someone's computer history. You can get bank information, you can get lots and lots of stuff they really aren't supposed to have, sir. Going to want to be sure, if not doing that
of not getting into personal data. You're not so slow. Getting into
passwords should never be in your final report or in any documentation.
If they are, they need to be masked so that you can ensure that no one's going to recreate or guess the password.
MP five hashing used to be the go to, but it has lots of collisions, so shallow one is usually good. Way to go or just don't include it. Just put in, ah, blanket password that wasn't actually used. Bacon substitute in for a password.
You do this to safeguard confidentiality and to maintain integrity. If any one person knows all the passwords, that's a danger.
And, of course, any method or device you used to maintain access,
Um, or whose removal
could cause downtime you should not implement unless you have written consent to implement it again. That's for the simple fact of an hour of downtime Can destroy a company's bottom line, and they will destroy your bottom line intern.
Any method or device you used to maintain access should have some sort of log in.
That's simply done so that if you're using it against a production server,
you're going to be able to ensure that no one else is going to get in. That's not part of your test.
Um, any data you gather should be encrypted and on your system.
Any information that could contain sensitive data needs to be sanitized,
and then all gathered data should be destroyed after your client is accepted. The final report
your method used in perfect destruction will be provided to the client.
A few more things. If it's regulated by law,
then you need to make sure you're following the law. Simple is that
never break the law. When you're doing this, it gets you in lots of trouble. Remember the Computer Fraud and Abuse Act I mentioned earlier?
Third party service is for pastor. Dragging should not be used.
There should not be any sharing or any data
that is exchanged with third parties that client consent.
If evidence of a prior compromises found, then you need to save. You need to stop all actions
you need to save everything you've done,
and you need to show your client what happened
Then again, no log should be removed, cleared, modified unless specifically authorized to do so.
Protecting yourself due to the nature again, you have to cover all of your bases and make sure you know what you're doing.
Insure your contract and statement of work to sign by. Both declined, and the provider
and everything is represented inside of that contract
obtained a company of security policies as well as the acceptable use policies.
Confirm you're not breaking any laws. Use full drive encryption. Discuss an established with the client. The procedures to follow in case of compromise.
Check for laws again, just over and over again. Make sure you're not breaking the law.
That's very, very important.
Now for most of what I just went over the paperwork, the documentation, all the legalities. They aren't really going to be something that I'm going to cover directly in this class. It's not going to be something you need to know because you're going to be targeting
your own VM your own system. I'm going to show you how these practices are done
so that you can more easily learn them again. This is a very high level course, very high level overview and the intent of it is to give you a sense of how these things work.
So you're not going to go into it actually, navigating through a corporate network, you don't need any major things. All you really need are an open source. V. M. I personally tend to use VM where, which isn't open source. But they do have of'em or player, which is free for use virtual boxes, of course, free for use as well.
And then you're going to want a couple of the EMS. My case I'm using Lennox and that I'm using Windows seven machine,
um, with possibly some touching on Windows eight elements as we go. But
primarily you're just going to want to have access to both operating system so that you can learn all of the things that you're about to go through. Other than that,
just a willingness to learn and an excitement about the subject. So
with no further ado, we're going to go ahead and dive in,