close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Vulnerability Assessment Scanner Overview
- Vulnerability Assessment Scanner Overview
- Installing the Java Cryptography Extension on JSA
play_arrow Troubleshooting Scanners
- Troubleshooting Scanners
play_arrow AXIS Scanner
- AXIS Scanner
- Adding an AXIS Vulnerability Scan
play_arrow Beyond Security Automatic Vulnerability Detection System Scanner Overview
- Beyond Security Automatic Vulnerability Detection System Scanner Overview
- Adding a Beyond Security AVDS Vulnerability Scanner
play_arrow Digital Defense Inc AVS Scanner Overview
- Digital Defense Inc AVS Scanner Overview
- Install the Frontline Vulnerability Manager SSL Certificate
- Creating an API Key in Frontline Vulnerability Manager
- Adding a Digital Defense AVS Scanner
play_arrow eEye Scanner Overview
- eEye Scanner Overview
- Adding an eEye REM SNMP Scan
- Adding an eEye REM JDBC Scan
play_arrow IBM AppScan Enterprise Scanner Overview
- IBM AppScan Enterprise Scanner Overview
- Creating a Customer User Type for IBM AppScan Enterprise
- Enabling Integration with IBM AppScan Enterprise
- Creating an Application Deployment Map in IBM AppScan Enterprise
- Publishing Completed Reports in IBM AppScan Enterprise
- Adding an IBM AppScan Enterprise Vulnerability Scanner
play_arrow IBM Guardium Scanner Overview
- IBM Guardium Scanner Overview
- Adding an IBM Guardium Vulnerability Scanner
- Configuring Guardium to Produce Report in AXIS Format
play_arrow IBM SiteProtector Scanner Overview
- IBM SiteProtector Scanner Overview
- Adding an IBM SiteProtector Vulnerability Scanner
play_arrow Juniper Profiler NSM Scanner Overview
- Juniper Profiler NSM Scanner Overview
- Adding a Juniper NSM Profiler Scanner
play_arrow McAfee Vulnerability Manager Scanner Overview
- McAfee Vulnerability Manager Scanner Overview
play_arrow Microsoft SCCM Scanner Overview
- Microsoft SCCM Scanner Overview
- Enable WMI for Microsoft SCCM Scanners
- Adding a Microsoft SCCM Scanner
play_arrow nCircle IP360 Scanner Overview
- nCircle IP360 Scanner Overview
- Exporting nCircle IP360 Scan Results to an SSH Server
- Adding a nCircle IP360 Scanner
play_arrow Nessus Scanner Overview
- Nessus Scanner Overview
play_arrow netVigilance SecureScout Scanner Overview
- netVigilance SecureScout Scanner Overview
- Adding a NetVigilance SecureScout Scan
play_arrow NMap Scanner Overview
- NMap Scanner Overview
- Adding a NMap Remote Result Import
- Adding a NMap Remote Live Scan
play_arrow Outpost24 Vulnerability Scanner Overview
- Outpost24 Vulnerability Scanner Overview
- Creating an Outpost24 API Authentication Token for JSA
play_arrow Qualys Scanner Overview
- Qualys Scanner Overview
- Installing the Qualys Certificate
- Adding a Qualys Detection Scanner
- Adding a Qualys Scheduled Live Scan
- Adding a Qualys Scheduled Import Asset Report
- Adding a Qualys Scheduled Import Scan Report
play_arrow Rapid7 NeXpose Scanners Overview
- Rapid7 NeXpose Scanners Overview
- Adding a Rapid7 NeXpose Scanner Local File Import
- Adding a Rapid7 NeXpose Scanner API Site Import
- Adding a Rapid7 Nexpose Scanner Remote File Import
play_arrow SAINT Security Suite Overview
- SAINT Security Suite Scanner
- Obtaining the SAINT API Port Number
- Obtaining the SAINT API Token
- Adding a JSA Host to the Allowed API Clients List
- Copy the Server Certificate
- Adding a SAINT Security Suite Vulnerability Scanner in JSA
play_arrow Tenable.io Scanner Overview
- Tenable.io Scanner Overview
- Obtaining the Tenable.io API Access key and Secret key
- Adding a Tenable.io Scanner to JSA
play_arrow Tenable SecurityCenter Scanner Overview
- Tenable SecurityCenter Scanner Overview
- Adding a Tenable SecurityCenter Scan
play_arrow Scheduling a Vulnerability Scan
- Scheduling a Vulnerability Scan
play_arrow Viewing the Status Of a Vulnerability Scan
- Viewing the Status Of a Vulnerability Scan
play_arrow Supported Vulnerability Scanners
- Supported Vulnerability Scanners

list Table of Contents

English

keyboard_arrow_right

Adding a NMap Remote Live Scan

date_range 27-Mar-21

arrow_backward

arrow_forward

JSA monitors the status of the live scan in progress and waits for the NMap server to complete the scan. After the scan completes, the vulnerability results are downloaded over SSH.

Several types of NMap port scans require NMap to run as a root user. Therefore, JSA must have access as root or you must clear the OS Detection check box. To run NMap scans with OS Detection enabled, you must provide root access credentials to JSA when you add the scanner. Alternately, you can have your administrator configure the NMap binary with setuid root. See your NMap administrator for more information.

Note:

Although there is an NMap binary on each JSA host, it is reserved for internal JSA use only. Configuring an NMap vulnerability scanner to use a JSA console or JSA managed host as the remote NMap scanner is not supported and can cause instabilities.

Click the Admin tab.
Click the VA Scanners icon.
Click Add.
In the Scanner Name field, type a name to identify your NMap scanner.
From the Managed Host list, select the managed host from your JSA deployment that manages the scanner import.
From the Type list, select NMap Scanner.
From the Scan Type list, select Remote Live Scan.
In the Server Hostname field, type the IP address or hostname of the NMap server.

Choose one of the following authentication options:

Option	Description
Server Username	To authenticate with a user name and password: In the Server Username field, type the username required to access the remote system hosting the NMap client using SSH. In the Login Password field, type the password associated with the user name. If the OS Detection check box is selected, the username must have root privileges.
Enable Key Authorization	To authenticate with a key-based authentication file: Select the Enable Key Authentication check box. In the Private Key File field, type the directory path to the key file. The default is directory for the key file is/opt/qradar/conf/vis.ssh.key. If a key file does not exist, you must create the vis.ssh.key file. Note: The `vis.ssh.key` file must have `vis qradar` ownership. For example: # ls -al /opt/qradar/conf/vis.ssh.key -rw------- 1 vis qradar 1679 Aug 7 06:24 /opt/qradar/conf/vis.ssh.key If the scanner is configured to use a password, the SSH scanner server to that connects to JSA must support password authentication. If it does not, SSH authentication for the scanner fails. Ensure the following line is displayed in your /etc/ssh/sshd_config file: `PasswordAuthentication yes`. If your scanner server does not use OpenSSH, see the vendor documentation for the scanner configuration information.

Option

Description

Server Username

To authenticate with a user name and password:

In the Server Username field, type the username required to access the remote system hosting the NMap client using SSH.
In the Login Password field, type the password associated with the user name.

If the OS Detection check box is selected, the username must have root privileges.

Enable Key Authorization

To authenticate with a key-based authentication file:

Select the Enable Key Authentication check box.
In the Private Key File field, type the directory path to the key file.

The default is directory for the key file is/opt/qradar/conf/vis.ssh.key. If a key file does not exist, you must create the vis.ssh.key file.

Note:

The vis.ssh.key file must have vis qradar ownership.

For example:

# ls -al /opt/qradar/conf/vis.ssh.key
-rw------- 1 vis qradar 1679 Aug 7
06:24 /opt/qradar/conf/vis.ssh.key

If the scanner is configured to use a password, the SSH scanner server to that connects to JSA must support password authentication.

If it does not, SSH authentication for the scanner fails. Ensure the following line is displayed in your /etc/ssh/sshd_config file: PasswordAuthentication yes.

If your scanner server does not use OpenSSH, see the vendor documentation for the scanner configuration information.

In the NMap Executable field, type the full directory path and filename of the NMap binary file.
The default directory path to the binary file is /usr/bin/NMap.
Select an option for the Disable Ping check box.
In some networks, the ICMP protocol is partially or completely disabled. In situations where ICMP is not enabled, you can select this check box to disable ICMP pings to enhance the accuracy of the scan. By default, the check box is clear.
Select an option for the OS Detection check box:
- Select this check box to enable operating system detection in NMap. You must provide the scanner with root privileges to use this option.
- Clear this check box to receive NMap results without operating system detection.
From the Max RTT Timeout list, select a timeout value.
The timeout value determines if a scan should be stopped or reissued due to latency between the scanner and the scan target. The default value is 300 milliseconds (ms). If you specify a timeout period of 50 milliseconds, then we suggest that the devices that are scanned be in the local network. Devices in remote networks can use a timeout value of 1 second.
Select an option from the Timing Template list. The options include:
- Paranoid - This option produces a slow, non-intrusive assessment.
- Sneaky - This option produces a slow, non-intrusive assessment, but waits 15 seconds between scans.
- Polite - This option is slower than normal and intended to ease the load on the network.
- Normal - This option is the standard scan behavior.
- Aggressive - This option is faster than a normal scan and more resource intensive.
- Insane - This option is not as accurate as slower scans and only suitable for very fast networks.
In the CIDR Mask field, type the size of the subnet scanned.
The value specified for the mask represents the largest portion of the subnet the scanner can scan at one time. The mask segments the scan to optimize the scan performance.
To configure a CIDR range for your scanner:
1. In the text field, type the CIDR range you want this scanner to consider or click Browse to select a CIDR range from the network list.
2. Click Add.
Click Save.
On the Admin tab, click Deploy Changes.

You are now ready to create a scan schedule. See Scheduling a Vulnerability Scan

arrow_backward PREVIOUS Adding a NMap Remote Result Import

NEXT arrow_forward Outpost24 Vulnerability Scanner Overview

Juniper Secure Analytics Managing Vulnerability Assessment Guide

Adding a NMap Remote Live Scan

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Juniper Secure Analytics Managing Vulnerability Assessment Guide

Adding a NMap Remote Live Scan

Related Documentation

Stay in touch