CoordOps GUI Scanners: Nmap, Wfuzz, SQLMap, OpenVAS, and Nuclei

CoordOps gives Nmap, Wfuzz, SQLMap, OpenVAS/GVM, and Nuclei dedicated workspaces built around a consistent principle: operators should be able to see the real command before it runs. Each interface provides a live command preview, streams tool output as it is produced, and keeps the scanning workflow connected to the active engagement.

These are interfaces to the real upstream tools, not simplified replacements with hidden behavior. Values selected in the interface are translated into the tool’s native arguments, allowing operators to review the generated command, understand what will execute, and use additional native options when the structured controls do not cover a specialized requirement.

The workspaces also provide a consistent execution lifecycle. Operators can configure the scan, refresh its command preview, start the operation, follow output as it arrives, stop supported operations, and review the final status. Output files and reports are directed into the active session where appropriate instead of being scattered across unrelated working directories.

The Nmap interface covers common scan configuration such as targets, ports, service and version detection, operating-system detection, host discovery, SYN scanning, default scripts, and fast scans. Advanced controls expose additional scan types, timing and performance settings, NSE script arguments, and evasion or spoofing options.

Nmap XML results are retained with the session and parsed back into CoordOps. Discovered hosts, ports, services, operating-system details, and other supported observations can therefore become part of the engagement record rather than remaining only in the scanner output.

The Wfuzz interface supports wordlists, payload and iterator syntax, response-code filtering, request headers, cookies, POST data, proxy settings, connection limits, delays, redirects, and basic, NTLM, or digest authentication. Operators can still supply additional Wfuzz options for workflows that fall outside the structured fields.

Wfuzz also includes an OpenAPI batch workflow. CoordOps can read a Swagger or OpenAPI document, identify its available operations, construct the corresponding fuzzing targets, and run them sequentially. Each generated command retains its own output handling, making a multi-endpoint assessment easier to review than one continuous, undifferentiated terminal transcript.

The SQLMap interface accepts one target source at a time: a target URL, a raw HTTP request file, or a bulk target file. Targets are validated against the current session scope before execution, helping prevent an imported request or bulk list from silently expanding the assessment beyond its authorized boundaries.

Operators can configure detection level, risk, non-interactive batch mode, user-agent behavior, Tor routing, operating-system shell testing, tamper scripts, and other advanced SQLMap options. Sensitive headers and cookies are excluded from the visible command preview, audit text, and execution output. When they are required for execution, CoordOps passes them through a protected temporary configuration file instead of exposing them on the displayed command line.

The OpenVAS/GVM integration provides a focused bridge to an existing GVM deployment. Operators supply the scan target and the credentials used to authenticate to the GVM management service. These credentials are for the management connection and should not be confused with credentials for performing an authenticated scan against the target itself.

CoordOps runs its bundled GVM integration script and stores generated reports in the session’s Reports directory. The interface is intentionally a lightweight scanning integration rather than a replacement for the complete GVM administration console, NVT configuration, scanner management, or compliance-reporting workflow.

The Nuclei interface supports individual targets or target files, custom template directories, severity and tag filters, concurrency and rate controls, headless scanning, debug output, and template updates. CoordOps can install Nuclei when the executable is unavailable and provides a direct template-update workflow for keeping the local scanning catalog current.

Nuclei output is parsed into structured findings. When a result can be matched to a host in the active session, CoordOps associates the finding with that host so it appears alongside discoveries from the rest of the toolchain instead of remaining isolated in a JSON or console output file.

The depth of integration intentionally varies by scanner. Nmap and Nuclei results can directly enrich the host and finding models, Wfuzz preserves endpoint-specific batch output, SQLMap maintains controlled execution artifacts, and OpenVAS/GVM produces reports through the external management service. CoordOps does not pretend that fundamentally different scanners produce identical data.

Operators remain responsible for the upstream tools, their versions, templates, licenses, daemon configuration, and the authorization to scan a target. CoordOps supplies the session context, scope checks, visible command construction, execution management, output handling, and result ingestion needed to use those tools as part of a coordinated assessment.

The result is a shared operating experience without hiding what each scanner actually does. Each tool retains its native capabilities and command structure, while CoordOps provides the visibility, organization, and engagement context needed to move from scan configuration to reviewable evidence.