Before
Security teams likely had to search each selected port individually, review the products returned for that port, and look up available versions for every product. They then had to copy the findings into a spreadsheet and manually note when a version was unavailable, repeating the process on a recurring schedule.
How it works
- On schedule, query the defined network for products associated with each configured port.
- For every discovered product, retrieve its detected versions and check whether version information is available.
- Append the port, product, and version details to the designated spreadsheet, using "n/a" when no version is returned.
Workflow details
- Scheduled discovery: The workflow starts on a predefined schedule and scans the configured network, country, city, and port filters. The current configuration includes nine commonly exposed ports, while the port list can be adjusted by the user.
- Port and product enumeration: For each selected port, the workflow retrieves the leading products identified on that port. It then processes each product individually to discover the versions associated with it on the specified network.
- Version validation: The workflow checks whether version data is available for each product finding. When versions are present, they are retained; when no version is reported, the finding is recorded with a clear "n/a" value rather than being omitted.
- Structured reporting: Each port, product, and version finding is appended as a row to a designated spreadsheet, creating an organized report that can be reviewed or maintained over successive scheduled runs.
- Operational result: The process replaces repeated manual searches and transcription across the selected ports with a consistent, scheduled inventory of products and versions running on externally visible network services.
What changed
Network discovery now runs on a predetermined schedule and automatically iterates through the configured ports, products, and versions. Findings are validated for missing version data and written directly to the designated spreadsheet, so the recurring work changes from manual collection and transcription to reviewing the generated report.
Work removed
Running separate searches for each configured port, reviewing returned products one by one, checking for available versions, copying findings into spreadsheet rows, and manually recording missing version information.
Expected outcome
For the shown nine-port configuration, each scheduled run can replace up to nine initial port searches plus the related product and version lookups, producing a repeatable network exposure inventory without manual row-by-row data entry.
