Nmap (Network Mapper) step configuration
Scan application instances with Nmap.
You can scan your application instances and ingest results from Nmap.
Important notes for running Nmap scans in STO
You can utilize custom STO scan images and pipelines to run scans as a non-root user. For more details, refer Configure your pipeline to use STO images from private registry.
STO supports three different approaches for loading self-signed certificates. For more information, refer Run STO scans with custom SSL certificates.
Nmap step settings for STO
The recommended workflow is to add an Nmap step to a Security or Build stage and then configure it as described below.
Scan
Scan Mode
Scan Configuration
Accepted values(s):
Default Run a scan with the following CLI flags to support most common use cases:
-sS -sU -T4 -A -v -PE -PP -PS80,443 -PA3389 -PU40125 -PY -g 53 –script "default"No Default CLI Flags Run a scan with no CLI flags. This is useful when you want to set up a highly customized scan with your own flags in the Additional CLI flags field.
Target
Type
Target and variant detection
Name
Variant
Instance
Domain
Protocol
Port
Path
Ingestion
Ingestion File
Log Level
Additional CLI flags
Use this field to run the Nmap scanner with specific command-line arguments. For example, the following flag includes IPv6 tests: -6.
Fail on Severity
Settings
Additional Configuration
Advanced settings
Last updated
Was this helpful?