SecurityCenter Report Templates

CVE Monthly Status Report

by Josef Weiss
February 25, 2014

This high level report displays CVE vulnerability details for the years 2010 - 2014.

The first chapter provides a graphical overview of CVE vulnerabilities in 3 pie charts that represent both vulnerabilities and recently mitigated vulnerabilities. Presented is a graphical overview of the current CVE vulnerability status of the environment. These three charts present CVE vulnerability information by severity, count and percentage.

Nessus Scan Report

by Josef Weiss
February 4, 2014

For customers who use Nessus for vulnerability scanning and then move to SecurityCenter, vulnerability reporting may be somewhat challenging. This report mimics the look and feel of a typical Nessus scanner vulnerability report.

Like a Nessus scanner report, this report contains a Table of Contents, iterates host information, and provides a results summary and vulnerability details for all hosts scanned.

CIP-002 Identification of Critical Cyber Assets Report

by Cody Dumont
January 23, 2014

CIP-002 Identification of Critical Cyber Assets Screen Shot
For organizations that are required to be NERC compliant, SecurityCenter can lead the way to compliance. The first focus area is the “Identification of Critical Cyber Assets”. SecurityCenter uses Log Correlation Engine (LCE), Passive Vulnerability Scanner (PVS), and Nessus to identify the assets. When using the complete Tenable family of products, an organization can easily identify all critical assets and all associated assets.

Errors and Warnings Report

by Josef Weiss
January 21, 2014

This report displays details on all warnings and errors identified in the environment.

The report has two main customizable sections.

The error section contains tables that present the reviewer with all errors found. By default, it is set up for display of the top 10 errors by count, and/or the last 24 hours by time. This can be easily modified to extend timeframe or display parameters. This section presents detected errors using five different methods.