What data for this category includes
Vulnerability scanning service data primarily comes from vulnerability scanners, asset inventories, CVE databases, and patch bulletins. Daily produced documents include scan plans, vulnerability lists, remediation tickets, and rescan reports. Core fields include asset scope, CVE ID, vulnerability severity, remediation status, and rescan time. Data update frequency is weekly or monthly. Sync rhythms differ across asset and vulnerability databases. Fields in documents must strictly align with requirements of scanning tools and security operations workflows to ensure data consistency and traceability.
Constraints on forms and interactions workflows
Data sources are scattered, and multiple security document formats must be matched. Forms must receive asset inventory data imported from external asset systems, and receive vulnerability filtering criteria output by external filtering logic. The weekly or monthly data update rhythm requires scan triggering logic to run via an external scheduled scheduling system. This avoids frequent scans impacting business peak hours. The strong correlation between core fields requires external business systems to group and display form-collected content per security operations workflows. For example, configure scan scope before setting vulnerability filtering rules. High-severity vulnerability exposure risks require mandatory field and data validity checks in subsequent nodes. This prevents security risks caused by missing critical configuration.
Configuration Guidelines
The following configurations are based on the formInput and userSelect node logic in FastGPT v4.17.0. All remaining business functions must be implemented via external systems.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
Form input node formInput | Test example: Select 3 fields from vulnerability scanning service as mandatory inputs; actual fields are determined per task | This node collects user input; missing mandatory items require checking interaction status to avoid subsequent nodes failing to receive complete input |
User selection node userSelect | Test example: Set 2 business options, verify corresponding branches one by one | This node handles user selection; query and filtering of vulnerability scanning service-related records must be implemented by subsequent interfaces or external systems |
| Post-submission field passing | Test example: Prepare 10 vulnerability scanning service input samples, covering full completion, missing mandatory items, and canceled operations | Compare input and node output to confirm whether subsequent nodes receive corresponding fields; result thresholds are determined per actual task |
| External implementation item: Asset scope selection | Must be implemented separately by external systems; after external asset systems import asset scope data, form nodes collect this data | Data comes from asset inventory documents, must match actual scan asset scope to ensure scans cover target assets |
| External implementation item: Scheduled scan triggering | Must be implemented separately by external systems; scheduled triggering logic is implemented by an external scheduled scheduling system, and form nodes pass triggering configuration parameters to the external scheduled scheduling system | Data update frequency is weekly, need to avoid business peak hours to ensure scans do not impact normal business |
| External implementation item: Rescan result verification threshold | Must be implemented separately by external systems; verification logic is implemented by subsequent data comparison nodes, matching thresholds are calibrated via actual testing (test example: difference rate ≤5%) | Need to eliminate false alarms caused by temporary environment fluctuations, verify consistency between rescan data and initial scan data |
Three Common Configuration Errors
- Symptom: Vulnerability scanning form displays "No valid vulnerability library associated" after submission. Verification steps: Confirm subsequent retrieval nodes use a valid CVE library source, confirm the form correctly passes vulnerability library association parameters
- Symptom: Scheduled scan task does not run at the scheduled time. Verification steps: Check trigger time settings in the external scheduled scheduling system, confirm the form correctly passes triggering configuration parameters
- Symptom: Rescan result vulnerability count does not match initial scan results. Verification steps: Check external asset scope filtering logic configuration, confirm classification rules in subsequent data comparison nodes are correct
How to Verify Correct Configuration
- Submit a test small asset inventory via the external asset import interface. Confirm the selected asset scope is normally received and displayed after form submission.
- Call the external scanning service interface to trigger a single scan task. Confirm the task starts normally and generates an initial scan plan document.
- View the external vulnerability retrieval node. Confirm the correct CVE library source is associated, and preset test vulnerability information can be retrieved.
- Check configuration items in the external scheduled scheduling system. Confirm trigger times are set per business requirements and do not conflict with peak business hours.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.