How to Create Reports with Netsparker Custom Reporting API

Netsparker Desktop allows you to create and define your own web security scan report templates. These may be used to generate custom reports that suit your business needs, and for integration with other software applications. The custom reporting tool employs the Razor templating engine that runs C# code to generate reports.

Creating a Custom Web Security Scan Report

Netsparker’s scripting language is C#. Below is a sample code for a web security report that generates an XML file which includes the following:

  • A list of all the vulnerabilities detected during the scan,
  • The vulnerable Parameter and type (GET/POST),
  • Vulnerability Details,
  • Confirmation Status,
  • Extra exploitation data,
  • Web security scan time,
  • Vulnerability severity.

You can add more details into the reports, customize them, or filter your reports with custom criteria.

Code Example for Custom Netsparker Desktop Report

@using System
@using System.IO
@using System.Linq
@using MSL.Common.Text;
@using MSL.Core.Configuration
@using MSL.Core.Data.Resources
@using MSL.Core.Entities.Vulnerability
@using MSL.Core.Process.Exploitation
@using MSL.Core.Process.Reporting;
@inherits HelperBaseTemplate<ReportTemplateData>
<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet href="vulnerabilities-list.xsl" type="text/xsl" ?>

<netsparker generated="@DateTime.Now.ToString()">
		var reportOutput = new FileInfo(Model.ReportFilePath);
			File.Copy(string.Format(@"{0}/vulnerabilities-list.xsl", ResourceCategories.ReportTemplate.ResolveCustomDirectoryPath()), string.Format(@"{0}/vulnerabilities-list.xsl", reportOutput.Directory.FullName), true);
		catch (Exception)

		// Sort vulnerabilities based on their severity, Type, confirmation and certainty
		var sortedVulns = from IVulnerabilityView v in Model.Vulnerabilities
			orderby v.Severity descending, v.Order ascending, v.Type ascending, v.IsConfirmed descending, v.Certainty descending, v.AbsolutePath
			where v.Visibility != VulnerabilityVisibility.Hidden && !v.IsIgnored
			select v;

		foreach (var vuln in sortedVulns)
			if (vuln.Visibility != VulnerabilityVisibility.Hidden)
				<vulnerability confirmed="@vuln.IsConfirmed.ToString()">

					@if (!string.IsNullOrEmpty(vuln.AttackParameterName))
						@foreach (var field in vuln.CustomFields)
							<info name="@field.Key">@ReportingUtility.XmlEscapeCharacterData(field.Value.HasMultipleValues ? string.Join(", ", field.Value.Values) : field.Value.Value)</info>

						var renderer = new ProofXmlDataRenderer();

					@if (vuln.Classification != null)

					@if (vuln.VersionVulnerabilities.Any())
							@foreach (var implied in vuln.VersionVulnerabilities)
									<references>@(implied.References == null ? string.Empty : implied.References.Trim())</references>

Saving the Custom Report Template

During startup the Netsparker Desktop scanner scans the "Report Templates" directory for C# template files (*.cshtml). This directory is in the Resources sub-directory of the Netsparker data directory (default location is the current Windows user’s Documents/My Documents directory, so the full path of that directory would be Documents/Netsparker/Resources/Report Templates). Every identified file here will be visible in the "Reporting" menu as a custom report.

Figure 54: The Customized Reporting Menu

Therefore every new custom report template that you create should be saved in this directory.

Defining the File Type (Extension) of the Custom Web Security Report

The name of the C# code file will be visible under the Reporting menu. When selected, the generated report will use the extension from the custom report file name. The file extension should be chosen based on the content type of the report. For the sample report above, it should be xml.

For example:

  • "Vulnerabilities List (XML).xml.cshtml" - File extension will be "xml"
  • "Vulnerabilities List as Web Page.html.cshtml" - File extension will be "html"

Testing the Custom Reports

You do not need to restart Netsparker Desktop every time you change the source code of your custom report. Once Netsparker adds the custom report to the report drop down menu all you need to do is run it again. If it fails to compile it'll let you know with an error message.

Security of Custom Reports

The Reporting engine runs with current user's privileges. So don't run the report unless you trust the author of the report.

Documentation for Custom Reports in Netsparker Desktop

You can access a MSDN-style API documentation from the Help drop down menu in Netsparker Desktop.


Dead accurate, fast & easy-to-use Web Application Security Scanner