Hey everybody and welcome to the next video.
We're gonna be going over remediation options and why they should be.
Reports so why do we provide these remediation options we provide them to complete the loop so when
we when we complete the assessment loop that we're we're first doing we we get the scope we get engagement
we do the engagement we we find the findings we build the report then we build the recommendations or
the remediation options that a user or a client or a customer or the organization might have to be able
to fix the problem.
It's not always 100 percent especially if you're a contractor you're giving update service fix you change
password you know whatever the case might be.
But from an internal perspective you might have to stretch this out a little bit further to complete
that loop which we'll talk about in the next video.
Now this is also convenient for the recipient of the report.
So if a if you're a contractor and you are attacking a in enterprise and you provide them a report with
no remediation options for how you could fix the attack vector sometimes the attack vector might be
very unique and it might not be fairly obvious what the actual underlying problem is.
So it's always good to point it out and it's just over the years people have been expecting this in
the reports.
Now it's just a common thing that you add and if you didn't add it it would feel like you are leaving
you are chasing them out on money in cost and stuff.
It also showed the quality of the report the more detailed it is the more quality in the report it is.
However keep in mind there is a limit to where if you put too much options in the report sometimes it
might be confusing like you give them five different options to do the same thing.
Which one's the best.
So your best as district with one maybe two if that makes sense.
And again this should never be left out.
Always added it even if it's just as simple as hey update the service add it.
It's just just that little extra step that when somebody reads it you'd rather have them read through
it and not think anything's wrong than to read through it and think something's missing.
It's just a psychological standpoint when you look at it from that way always at the remediation.
Normally when you see a vulnerability there's a general idea of the reason of why such is the person
who built the exporter found the vulnerability has some sort of information saying hey these configuration
files together when they're at when everything's configured this way This vulnerability is present in
most cases just update the service change the password put in a firewall here restrict user change permissions.
But in some cases it might be five or six options in a config file that that make this occur.
And if that's the case then they need to get with the.
You can say that these are the options for example that caused the problem.
You can disable these options if that's not available.
Contact the the owner of the service or the the writer of the application if it's if it's that and try
to figure out if there's a way to handle it unless it's a zero day.
Chances are somebody else has looked for this resolution before and it's out there.