Ingesting Findings

from csv (ui) the vrm csv import interface allows users to manually import either asset or vulnerability finding data via a csv file the system supports batching, source mapping, and result tracking asset import use this option to upload and register assets in swimlane upload the asset csv file click ingest asset csv review the result under asset rows ingested finding import finding import is used to load vulnerability scan results into vrm this is typically done when ingesting data from external scanners like qualys, tenable, etc , or for uploading test data during evaluation purpose the finding import option allows you to upload vulnerability scan data in csv format and initiate ingestion for enrichment it is typically used for ingesting raw data from tools like qualys or tenable, or for test scenarios user input fields csv file contains raw findings in comma separated format page size maximum number of findings per ingestion batch (default 1000) source logical name used in mapping (must match source in teds logic) on clicking the "+" button next to vrm csv import , a new record is created you are prompted to choose between asset or finding import based on your choice, the interface adjusts to display relevant fields such as page size, source, and file upload this is the starting point for the entire vulnerability processing flow in vrm from connector/api this method is used when data is automatically fetched and processed through scheduled flows or integration playbooks it uses the same ingestion mechanics described above when findings are ingested via connectors or scheduled playbooks, the same ingestion logic applies connectors fetch data from integrated vulnerability scanners fetched results are parsed and transformed into the ingestion page format the ingestion pipeline handles them identically to csv based imports