See the following sections for the optional Network Scanner - Nmap plugin configuration settings.

excludeHosts

Comma-delimited list of hosts to exclude from scanning. Uses the same format as the hosts field. Useful for excluding routers, firewalls, or critical infrastructure from scans.

For example:

10.1.127.1,192.168.1.254

timeout

Total scan timeout in seconds. For large networks, increase this value to prevent premature scan termination.

  • Default: 300 seconds (5 minutes).
  • Range: 1-86400 seconds (1 second to 24 hours). 
  • Example: 60

timingTemplate

The name of the Nmap timing template controlling scan speed and network impact. See the following table for the supported options.

Template name

Template identifier

Scan speed

paranoid

T0

Slowest, most stealthy, suitable for IDS evasion

sneaky

T1

Very slow and stealthy

polite 

T2

Slow and considerate to target systems

normal 

T3

Balanced speed and stealth (default)

aggressive 

T4

Fast but more detectable

insane 

T5 

Fastest but very noisy, and may miss results

Example: polite

maxHostGroup

The maximum number of hosts to scan in parallel. 

  • For small networks, use 5-10;
  • For large networks, use 50-100.

Larger values increase scan speed but delay streaming feedback and consume more resources.

  • Default: 10 hosts.
  • Range: 0-1000. 
  • Example: 20

skipHostDiscovery

true to treat all hosts as online and skip ping probes using:

Nmap -Pn flag

Use this value when firewalls block ICMP ping requests. May increase scan time as Nmap will attempt to scan all specified hosts.

  • Default: false
  • Example: true

skipDNSResolution: 

true to skip reverse DNS lookups using:

Nmap -n flag

Enabling this speeds up scans and reduces network traffic; however, hostnames won't be resolved in the output.

  • Default: false
  • Example: true

randomizeHosts

true to randomize the order of host scanning using:

Nmap --randomize-hosts flag

This value helps distribute scan load and avoid detection patterns.

  • Default: false 
  • Example: true

state.lastRunDateTime

The timestamp of the last scan execution. This value is updated automatically after each scan and is for informational and tracking purposes only.

Example: 

2025-10-02T12:00:00Z