Hey everybody.
Welcome to the next video.
We're gonna be talking about the audience of the report.
So we've gone over the format and some of the places that in sections that are in the report now we're
going to look at the audience and where we should tell in the report to now in a standard situation
you're going to have two types of audiences the technical audience and the non-technical audience.
Now keep in mind that sometimes these two can bridge between each other such as You you're what might
be considered in the non-technical of the executives but a C so or a chief information security officer
is technically considered an executive and they might be very technical in nature as well.
So sometimes they blend.
So it's not a hard line in between the two.
Just keep that in mind when you go through writing the report.
So the first thing I want to quickly will actually go back just for a second here.
So the audience is not just how you write the report but it's where the report is presented.
So keep in mind that there's there's two different aspects to this.
There's the inside the report and then external to the report.
So on the technical side there's normally again.
Take this with a grain of salt.
It's normally engineers owners of services and individuals that will actually fix the issues that were
found.
Again this can bleed into different tech non-technical roles but just as a generic standpoint is when
you look at a technical report of some ways we'll look at that.
It's probably going to be an engineer of some kind that would understand the context around all of the
details that were going on rather than the issue of at a high level then we have non-technical which
can be executives managers program managers and these tend to read the executive summary.
But again I take it with a grain of salt there are program managers managers and executives that are
technical in nature.
There are some that are not.
So there's it's just entirely depends on who the report is going to be provided to.
Once it's been complete and a lot of times you'll know what individual she is going to be able to be
getting the report at the very end that's might not be the technical person and you can judge based
on that how you want to approach the conversation.
Now there's one thing I wanted to quickly talk about before the end of the video is speaking to non-technical
people having a skill set as a red team or even as a contractor being able to explain a technical problem
to non-technical people is a very very good skill set to have.
It is a very valuable skill to have and it's not something that you can build up by doing research online
and googling things you need to actually go and present things to people use metaphors similarities
between other common processes in the company or common things in general.
So taking that back for a second.
What I want you to do is think of a concept like let's say SSA tunneling not reverse tunneling just
the standard tunneling.
How would you explain that to somebody without using any technical lingo.
So take a second.
Figure that out.
It might take you a little bit if you're not used to doing this but think of metaphors and things that
kind of act the same way in the real world that anybody can relate to and then try to explain it based
on that.
It takes a little bit of time to build up that skill set to get it off the top of your head.
And so it's a very valuable skill set to have because when you go in talking to a group of people whether
it's the technical group the non-technical or the mix of both you need to be able to explain things
based on the audience in the room and that's where the important bit is here.
This is more of a social skill than a technical skill at this point.
You need to be able to convert technical to non-technical based on the audience that you're currently
in.
And if you're in a room with technical people you need to be able to explain the technical problem at
enough depth for them to be able to understand to resolve the issue.