Summary
Support exporting scan results in Nmap-compatible XML and grepable output formats for interoperability with existing security toolchains.
Motivation
- Many security tools (Metasploit, Nessus, OpenVAS) import Nmap XML format
- Grepable output (-oG) is widely used in scripting and automation pipelines
- Standards-based output makes the toolkit a drop-in complement to existing workflows
- Enables integration with vulnerability scanners and SIEM platforms
Proposed Approach
-
Nmap XML output (-oX equivalent):
- Follow Nmap DTD schema for scan results
- Include host, port, service, and state information
- Add scan metadata (start time, arguments, scanner version)
- Validate output against Nmap's DTD
-
Grepable output (-oG equivalent):
- One host per line with tab-separated fields
- Compatible with standard grep/awk processing
- Include open/closed/filtered port states
-
JSON output (native):
- Structured JSON for programmatic consumption
- Nested host > port > service hierarchy
-
CLI integration:
-o xml, -o grep, -o json flags
-oA to output all formats simultaneously
- Output to file or stdout
Acceptance Criteria
Summary
Support exporting scan results in Nmap-compatible XML and grepable output formats for interoperability with existing security toolchains.
Motivation
Proposed Approach
Nmap XML output (-oX equivalent):
Grepable output (-oG equivalent):
JSON output (native):
CLI integration:
-o xml,-o grep,-o jsonflags-oAto output all formats simultaneouslyAcceptance Criteria