Before
Security teams had to manually reformat each third-party scanner export to match the required HOST column structure and validate the data before importing it. They also had to check whether the correct provider existed, create one when necessary, and trigger the asset import across multiple tools.
How it works
- Capture an incoming third-party scan CSV from a webhook or email attachment and prepare the workflow data.
- Rebuild and validate the file against the required HOST schema, correcting missing columns where possible.
- Find or create the appropriate provider, import the validated file to create or update assets, and confirm whether the import succeeded.
Workflow details
- Capture: The workflow starts when a third-party scan CSV is received through a secure webhook or as an email attachment, preserving the incoming file for processing.
- Transform: An AI task rebuilds the scan data into the required HOST CSV structure, using the defined headers and mapping available values into the expected format with semicolon-separated columns.
- Validate: A second AI check cross-checks the generated file against the HOST template and adds missing columns where possible before the import is attempted.
- Import: The workflow retrieves existing providers, reuses the matching provider when available, or creates a new HOST provider when none is found. It then submits the validated CSV to create or update HOST assets and marks the run successful only when the import completes successfully.
What changed
The scan file is transformed and checked automatically as soon as it arrives, while provider lookup or creation is handled within the same workflow. The validated result is sent directly for asset creation or update, leaving analysts out of the preparation and import handoff.
Work removed
Manually restructuring CSV columns, mapping scan values to the HOST template, checking for missing fields, searching for an existing provider, creating a provider when needed, and triggering each asset import.
Expected outcome
Approximately 10–20 minutes of recurring preparation work can be removed per scan file, with consistent formatting across imports from different third-party scanners.
