EvidenceCounter content control

The EvidenceCounter content control counts the number of instances of Evidence associated with a specific Issue. Yes, the EvidenceCounter is a real specialist! But, it can help you answer interesting questions like, "how many locations does this Issue impact?"

Because the EvidenceCounter control is specialized, you'll need to make sure that it is always wrapped in an Issue content control. Without it, the EvidenceCounter control will not populate.

This page contains:

Count All Evidence affecting each Issue

The simplest report template with an EvidenceCounter content control would look something like this:

Reports 147

This is simply an EvidenceCounter content control wrapped in an Issue control.

The output will be a count of the total count of Evidence for each Issue in your project. The EvidenceCounter control does not deduplicate the Evidence. So, if the Issue has 3 instances of Evidence, all affecting the same Node, the EvidenceCounter control would output 3 in the exported report. If you want to get deduplicated host data, check out the Affected content control.

Count All Evidence affecting each Issue, organized by Node

You can also wrap the Issue control shown above in a Node content control to display the data in a different way.

If we have an example project that contains just 1 Issue (e.g. Insufficient cross-site request forgery (CSRF) protection) with 3 instances of Evidence, we can use the EvidenceCounter content control to understand how many times each Node is affected.

Reports 148

And if we use a report template that is organized by Node like the one shown below:

Reports 193

This sample project will export into the simple report template like this:

Reports 149

Count filtered Evidence

We can filter our EvidenceCounter content control if we want to count just a subset of our instances of Evidence.

If you haven't already, now would be a good time to review the Filtering and sorting page of this guide for more on the different filtering options available.

In the example above, you can see that one of the instances of Evidence contains a #[Report]# field with the value Yes. We can filter the EvidenceCounter control as shown below to only capture the instances of Evidence that have the Report field set to Yes:

Reports 150

Next help article: Methodology content control →

Streamline InfoSec Project Delivery

Learn practical tips to reduce the overhead that drags down security assessment delivery with this 5-day course. These proven, innovative, and straightforward techniques will optimize all areas of your next engagement including:

  • Scoping
  • Scheduling
  • Project Planning
  • Delivery
  • Intra-team Collaboration
  • Reporting and much more...

Your email is kept private. We don't do the spam thing.