Building a Nessus Test
Building a new Nessus Test Case is straight forward. First, create a scan policy within Nessus. If you have a specific audit file that you would like to use (ex: one downloaded from the IASE website), you must first upload it into Nessus. Instructions for uploading an audit file and creating a s...
Custom Networking for Scanning in DISA milCloud
By default, the CONS3RT Elastic Test Tool VMs connect to the "CEMS network" in your HmC VDC. In order to allow the test tool VMs to scan additional networks inside your DISA milCloud VDC, a custom Red Hat 6 template may be required. To create this custom template:
Log in to your HmC VDC in vCl...
Elastic Test Tools
CONS3RT elastic test provides a framework for getting test results with minimal effort from a selection of integrated Elastic Test Tools. To use elastic test first:
Import a Test Asset (/kb/elastic-tests/import-a-test-asset)
Add the test asset to a delpoyment (/kb/deployments/creating-a-deploym...
Users have the ability to create Test Assets to run on-demand HP Fortify scans using the Fortify Elastic Test Tool. Scans can also be run against any software assets that contains or stages source code.
How to Run a Fortify Scan
Step 1: Create a Fortify Test Asset
There is a Sample Fort...
Import a Test Asset
This article describes import a Test Asset for one of the Elastic Test Tools (e.g. Nessus, Fortify, Sonar) into HmC
Import Test Assets
First, create a zip file containing the contents of your Test Asset
Next to Tests on the main menu, click Add (Note: if you do not see
Note: If you do not see ...
Nessus Test Configuration and Nessus Test Assets
Nessus Test Assets allow for on demand vulnerability scanning and auditing of all deployment runs (i.e., both newly provisioned and long standing). There are two was in which Nessus Test Assets can be used:
Part of a Deployment - By default, adding a Nessus Test Asset to a deployment will scan a...
Nessus Test Structure
All Nessus Test Cases consists of a Policy file and (optional) Audit file. A scan policy consists of configuration options related to performing a vulnerability scan. These options include, but are not limited to:
Parameters that control technical aspects of the scan such as timeouts, number of ...
Troubleshooting a Test Error
If you encounter a Test Error in a Nessus Scan with an error message including invalid credentials, simply click the Re-Test button. This is an issue with the Nessus product, and we are working on a fix to avoid this issue in the future.