Hi everybody and welcome to the routine assessments many module.
So this is a six part mini module that will go over what routine assessments are how they work why they're
needed any special use cases what types they are so what are routine assessments a routine assessment.
In a nutshell is a red team engagement that is done on a scheduled basis so this can be consistently
such as hourly daily weekly.
This is normally done by some sort of automation or maybe it's a daily task.
There's monthly quarterly and yearly.
Now each of these will have their own videos dedicated to just them inside of these six parts mini series.
So there's a wide variety of types of assessments such as phishing password cracking.
There's external penetration tests internal testing network segmentation testing.
So there's a lot of varieties move over this a little bit.
I know I've mentioned phishing a few times so far and haven't really given an explanation.
So phishing in a nutshell is when an attacker sends a fake or false email to an individual in attempts
to gather some sort of information whether that's them downloading and running an attachment that might
be touched to malware could be them clicking on a link and putting in their credentials whether it's
a banking site or employee log or whatever the case might be.
So that's phishing in a nutshell password cracking is around.
You have a hash that you've obtained of some way whether that be from a system from a database online
or whatever the case might be you attempt to crack it to bring it to its plaintext so we can use the
username and password combination in a future engagement to gain access to a machine ahead of time.
So why are our routine assessments needed so they're needed because they are the core function of a
red team's actions.
So a red team runs on ending on engagements or assessments.
So whether that's something you do quarterly or yearly testing the testing a specific service let's
say maybe there's a web server that you're companies using.
You run that you run a test or an assessment against directly that so that would be counted as an assessment.
So anything a red team does when it tries to emulate an attack would be considered an assessment.
So there's also a follow up tests.
So when a test has been performed a few months ago or a year ago or multiple years ago maybe we want
to revisit that same test to see what's been improved what's missing maybe something wasn't fixed.
Some most of the time this happens pretty pretty rapidly after whatever findings have been identified
were fixed.
So again like I said before specialized test you we have a web server Jenkins server some sort of deployment
pipeline and anything around anything specialized that you want to test maybe your company runs a vault
password management soft service so you might want to test that specifically and that's under a specialized
test.
Some in some cases those compliance requirements where for example maybe PCI or FET ramp or any of those
might have a requirement around having an external test be performed by a third party.
This is something that in most cases the red team will take over and get running again this is something
we'll talk about in the next in the next few videos.
But compliance requirements are a big part of this as well.
So enjoy this little mini series or kind of go over everything we just talked about in more detail specifically
around the types of engagements and at the end of this you're going to build a assessment plan or an
engagement plan for your own Red Team fictionally of course unless you actually happen to be on a red
team in that case.
Great job.
So in that case you'll build your own from scratch for the four for at least one to two years in advance
so you can kind of see what you want to recap and obviously of course there's the unknown element where
maybe you have to run a particular test for whatever reason.
Again we're not going to keep that in scope when you're building this but we'll go over this in a little
bit later.
Enjoy the rest of the mini module.