Now this one was pretty straightforward.
We were taking the ability to clear an event log.
In this case, I'm gonna be clearing the system.
I'm gonna zoom in real quick
and show you what I'm doing here.
And then I'm also using NetExec in order to do this
without going through Meterpreter.
Something you can do basically in the terminal line
of Kali without having to go through
the whole MSF console setup and stuff.
Now here, we're using NXC, that's the NetExec command.
Use the protocol WinRM because it's known
by that domain controller and trusted inside the firewall.
Target IP, username, password, verbose.
And then the actual command,
which is the second part of our challenge here,
which is wevetutil clear system.
And I'm going to go ahead and execute this.
And we'll wait for the response.
And you should be able to see it right here.
Executing command, executing process.
So I just went through it, it didn't give us any errors.
And that's because in the command prompt
when we do run this, we don't get any kind of response
other than just it goes to the next C prompt.
And with that, I kinda wanna wrap up
and cover a couple of things real quick
as we begin to close this course.
As a pentester, there is no one answer
for every single issue.
And no one issue has one definitive answer
for how to do something.
Each pentester is going to perform differently.
They're going to have their standard flow
of how they operate and different practices
and tools that they prefer.
The actual idea of a pentest
is going to follow a basic outline.
But really, that outline's kinda like drawn in crayon
because all we have to do is get from point A to point B.
The only thing that we should all agree on
in the course of the pentest is,
is that a pentest exists solely for the purposes
of testing the security and resilience of security
for an organization without damaging
any of the data, users, or systems
within that organization.
If you can do everything from get username and passwords
to testing and getting PII off of things
and all that other great stuff without doing any damage
and making sure that this organization learns
from the results found in the pentest
and strengthens their security,
that's really all we're looking for.
In order for us to be able
to make ourselves better pentesters,
we also need to practice
and become better security professionals
inside of the actual, what's the best way to put it?
Suit and tie world.
So pentesters march to the beat of their own drums,
which is great because we're unique.
But we also need to have the experience
on the defensive side of the house
because as we started the course out together,
we mentioned that you can't be a good locksmith
without having tested your locks
and done some lock picking
to verify the actual security of that lock.
If you're gonna make a bold claim
and say that it's lock pick resistant,
you better be ready to back it up.
And if you don't do any kind of testing
to improve the design of that lock,
that claim is going to be shot down rather quickly.
But again, pentesters are kind of like the snowflakes
that fall in the sky that I've heard about
because we don't have those here in Texas that often.
Each pentester is unique.
Each one of you is unique.
And we are going to continue to be unique
because if we're all the same,
that's just not unique and it's also not,
it's rather boring.
So as you go forth, just remember,
do the best you can, learn from it
and don't be afraid to make mistakes.
I hope this has been informative for you
and I'd like to thank you for viewing.