Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Adding a NMap Remote Live Scan

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.

  1. Click the Admin tab.
  2. Click the VA Scanners icon.
  3. Click Add.
  4. In the Scanner Name field, type a name to identify your NMap scanner.
  5. From the Managed Host list, select the managed host from your JSA deployment that manages the scanner import.
  6. From the Type list, select NMap Scanner.
  7. From the Scan Type list, select Remote Live Scan.
  8. In the Server Hostname field, type the IP address or hostname of the NMap server.
  9. Choose one of the following authentication options:

    Option

    Description

    Server Username

    To authenticate with a user name and password:

    1. In the Server Username field, type the username required to access the remote system hosting the NMap client using SSH.

    2. 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:

    1. Select the Enable Key Authentication check box.

    2. 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.
  10. 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.

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  15. 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.

  16. 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.

  17. Click Save.
  18. On the Admin tab, click Deploy Changes.

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

Related Documentation