WEBVTT

00:00:01.340 --> 00:00:05.460
Accuracy. Details in the report must be accurate.

00:00:06.540 --> 00:00:09.370
They should be technically correct and evidenced

00:00:09.380 --> 00:00:14.490
appropriately. Someone performing QA will be looking for signs

00:00:14.490 --> 00:00:17.050
that each finding wasn't a false positive.

00:00:18.140 --> 00:00:21.960
If during testing assumptions were made and never proven,

00:00:22.210 --> 00:00:25.140
then it's possible to report findings that don't actually

00:00:25.140 --> 00:00:28.710
exist. That could waste a lot of time in remediation.

00:00:28.710 --> 00:00:32.850
Guidance on risk is important here too.

00:00:33.340 --> 00:00:37.550
If a vulnerability like cross‑site scripting exists, then it's definitely a

00:00:37.550 --> 00:00:41.430
finding. If there are mitigations that limit its usefulness,

00:00:41.840 --> 00:00:46.460
then risk and severity scores should reflect that, not just the worst case.

00:00:47.740 --> 00:00:49.920
If you can use it to steal session cookies,

00:00:50.130 --> 00:00:53.070
then there should be evidence, like a screenshot. Typos.

00:00:53.070 --> 00:00:57.070
Spell checkers don't always pick these up,

00:00:57.110 --> 00:00:58.750
but using one is a good start.

00:00:59.840 --> 00:01:03.520
Hyperlinks can be challenging because often the URL isn't visible.

00:01:03.520 --> 00:01:09.370
You have to hover over it or click it to check. Maybe the web page

00:01:09.370 --> 00:01:12.060
was removed or there's a typo in the URL.

00:01:13.140 --> 00:01:17.960
If Kim mentions the SMB protocol, she'll mention the version if it's appropriate.

00:01:18.940 --> 00:01:20.980
If it's the EternalBlue vulnerability,

00:01:21.140 --> 00:01:27.860
then she states SMB version 1 because it only happens in version 1. Clarity.

00:01:28.540 --> 00:01:33.250
The report should use language that conveys messages in an unambiguous way.

00:01:34.040 --> 00:01:37.620
It should be very clear to the audience what their vulnerabilities are,

00:01:37.720 --> 00:01:40.560
how to fix them, and the risks they present.

00:01:41.940 --> 00:01:44.900
It's easy to write a report with the assumption that readers

00:01:44.900 --> 00:01:49.040
have a similar level of knowledge to you. Vincent at Carved

00:01:49.040 --> 00:01:51.160
Rock is a security engineer,

00:01:51.540 --> 00:01:56.250
so likely to be well versed in most but not all vulnerabilities in a report.

00:01:57.240 --> 00:01:59.660
Many readers won't be that knowledgeable.

00:02:00.940 --> 00:02:04.750
How do we help clarity? Did we use an abbreviation?

00:02:05.640 --> 00:02:08.729
Every time Kim does, it gets stated as the expanded

00:02:08.729 --> 00:02:10.460
version the first time it's used.

00:02:11.340 --> 00:02:15.260
So if she writes denial of service, it gets the DoS in brackets.

00:02:16.140 --> 00:02:20.020
Just the abbreviation DoS is then used any other time it's needed.

00:02:20.020 --> 00:02:24.550
Domain‑specific wording is important to get right.

00:02:25.340 --> 00:02:27.400
If Kim mentions password cracking,

00:02:27.540 --> 00:02:31.760
she'll add an explanation and maybe even a hyperlink for more information.

00:02:32.940 --> 00:02:36.890
There are lots of words like this in security, rainbow tables,

00:02:36.900 --> 00:02:39.060
dictionary attacks, buffer overflows.

00:02:39.640 --> 00:02:40.860
Try to keep this in mind.

00:02:41.940 --> 00:02:45.440
Kim gives step‑by‑step walkthroughs for findings because it

00:02:45.440 --> 00:02:47.660
can really help a reader to understand them.

00:02:48.740 --> 00:02:52.960
Often, images helped too, although, if they show use of the command line,

00:02:52.970 --> 00:02:56.630
Kim will add the command text to the document so it can be

00:02:56.630 --> 00:02:58.850
copy and pasted to reproduce findings.

00:03:00.140 --> 00:03:05.650
Writing a report in a consistent manner helps too. If two pen testers work on a

00:03:05.650 --> 00:03:09.150
report and write up findings in completely different ways,

00:03:09.470 --> 00:03:11.660
then this makes it complicated for the reader.

00:03:12.840 --> 00:03:15.840
This gets easier when everyone writing a report is using

00:03:15.840 --> 00:03:18.660
similar templates and has the same requirements.

00:03:19.840 --> 00:03:24.550
Generally, readers want a report to be concise to get to the point quickly.

00:03:25.640 --> 00:03:29.190
They'd rather not spend hours reading a report, nor do they want

00:03:29.200 --> 00:03:31.760
page after page of text with no interruption.

00:03:32.640 --> 00:03:33.150
However,

00:03:33.840 --> 00:03:37.680
if we're trying to explain everything accurately and clearly with the

00:03:37.680 --> 00:03:40.650
assumption that readers have only a basic understanding,

00:03:41.040 --> 00:03:42.750
then that can mean a lot of words.

00:03:43.940 --> 00:03:45.260
We need a balance here.

00:03:46.140 --> 00:03:49.950
We want to give enough information, but don't want to put someone off because

00:03:49.950 --> 00:03:54.190
there's too much text. Looking at Kim's executive summary,

00:03:54.350 --> 00:03:55.860
that's half a page long.

00:03:56.340 --> 00:04:00.750
It is a summary after all and shouldn't contain huge amounts of detail.

00:04:01.640 --> 00:04:04.660
It also uses bullet points that help keep it short.

00:04:05.640 --> 00:04:09.000
Kim chooses her wording carefully here and makes

00:04:09.000 --> 00:04:10.460
sure she doesn't repeat anything.

00:04:11.340 --> 00:04:15.290
Getting information across with minimal wording is a skill

00:04:15.290 --> 00:04:20.269
in itself and takes practice. In the findings, Kim gives

00:04:20.269 --> 00:04:22.760
information clearly and concisely,

00:04:23.140 --> 00:04:26.680
but uses hyperlinks to give depth to help readers who don't

00:04:26.680 --> 00:04:28.360
have as much knowledge on the subject.

00:04:29.540 --> 00:04:32.660
This really helps to reduce the overall size of the report.
