Everybody welcome to the next video.
So we've gone over how to scope how to identify scope and the goals briefing the stakeholders instability
considerations.
Now what we're gonna want to go through now is the document itself.
So this is a template document that you could use.
There's thousands of options you can make it any way you want in most in most cases a Red Team will
already have some sort of document in place.
So what we've got here is we've got the company name.
We've got the red team that's gonna be doing the test in this case the red team.
We've got the members one and number two which can be people's names and then we have blank assessments.
So whatever type of assessment you're wanting to do and then we've got our scope.
So this is our paragraph about what the scope is what are what we can and cannot hit as far as the scope
is concerned.
Then again we have our goals.
What is our goal.
What are our sub goals all going here.
And we have our restrictions.
Now this is where we have stability considerations.
We have no AJ.
And in some places this is where anything that you need to be aware of when doing this engagement or
this test is under this.
Followed by that is our dates of the assessment.
So this will be the start and end date.
You can also add in here the when notifications will be sent out.
So the service owners will be aware of it and then stakeholders so you can provide the contact information
and the first and last name and email of the stakeholder.
Now these are gonna be the main stakeholders because this can be a very big list or a very small list
depending on what you're testing.
So keep in mind that if for example if you have a an entire network segment you're not going to want
to hit an ad in here every stakeholder.
That's part of that has any service inside a whole network.
You're gonna want to do in that case is touch base with the network team and provide then the as the
point of contact or the stakeholder.
And then same work for the network operations team.
And then maybe a few core services in there that you're aware of that you know you're going to be specifically
testing then you're gonna want add them there.
You're not gonna want to add everybody under the sun.
Now an important piece here is the red team manager or whatever manager is overseeing the red team make
sure they have their signature there and then the red team members that are going to be actually doing
the engagement.
Now you can even add another one in here where the C so will and we'll sign this off as well for an
internal team.
And and in some cases some companies want their stakeholders to actually sign the document and make
sure that everybody agrees on everything.
However as we say in the previous CTO This is the document you're going to want to notify and send out
to the stakeholders.
Once it is completed it's been approved by your manager and any other interested parties.
So this is the document again that's going to be sent out.
I'm going to put a link to this above the.
This particular video.