Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Vulnerability Scan Notifications for JSA Appliances

 

External Scan Gateway Failure

38750119 - An invalid/unknown gateway IP address has been supplied to the external hosted scanner, the scan has been stopped.

Explanation

When an external scanner is added, a gateway IP address is required. If the address that is configured for the scanner in the deployment editor is incorrect, the scanner cannot access your external network.

User Response

Select one of the following options:

  • Review the configuration for any external scanners that are configured in the deployment editor to ensure that the gateway IP address is correct.

  • Ensure that the external scanner can communicate through the configured IP address.

  • Ensure that the firewall rules for your DMZ are not blocking communication between your appliance and the assets you want to scan.

Scan Failure Error

38750090 - A scanner has failed.

Explanation

A scheduled vulnerability scan failed to import vulnerability data. Scan failures are typically caused by configuration or performance issues that result from a large volume of data to import. Scan failures can also occur when a scan report that is downloaded by the system is in an unreadable format.

User Response

Follow these steps:

  1. Click the Admin tab.

  2. On the navigation menu, click Data Sources.

  3. Click Schedule VA Scanners.

  4. From the scanner list, hover the cursor in the Status column of any scanner to display a detailed success or failure message.

Scan Tool Failure

38750118 - A scan has been stopped unexpectedly, in some cases this may cause the scan to be stopped.

Explanation

The system cannot initialize a vulnerability scan and asset scan results cannot be imported from external scanners. If the scan tools stop unexpectedly, the system cannot communicate with an external scanner. The system tries the connection to the external scanner five times in 30-second intervals.

In rare cases, the discovery tools encounter an untested host or network configuration.

User Response

Select one of the following options:

  • Review the configuration for external scanners in the deployment editor to ensure that the gateway IP address is correct.

  • Ensure that the external scanner can communicate through the configured IP address.

  • Ensure that the firewall rules for your DMZ are not blocking communication between your appliance and the assets you want to scan.

Scanner Initialization Error

38750089 - A scanner failed to initialize.

Explanation

A scheduled vulnerability scan is unable to connect to an external scanner to begin the scan import process.

Scan initialization issues are typically caused by credential problems or connectivity issues to the remote scanner. Scanners that fail to initialize display detailed error messages in the hover text of a scheduled scan with a status of failed.

User Response

Follow these steps:

  1. Click the Admin tab.

  2. On the navigation menu, click Data Sources.

  3. Click Schedule VA Scanners icon.

  4. From the scanner list, hover the cursor in the Status column of any scanner to display a detailed success or failure message.