What the data for this category looks like
The data for this category mainly comes from target business systems, public vulnerability databases, output results of automated scanners, and manual verification records from red team engineers. The standardized documents generated daily include four categories: test authorization letters, penetration test reports, vulnerability reproduction records, and rectification suggestions. Each type of document includes fields such as the corresponding project number, vulnerability number, risk level, and verification steps. The data update rhythm is triggered by the progress of individual penetration test projects or major version updates of target systems, with no fixed cycle.
What constraints these characteristics impose on the "workflow orchestration" link
Since data updates follow individual projects with no fixed cycle, configure the workflow to dynamically bind data sources and document templates by project dimension. Use the test authorization letter as a pre-compliance document, and add a verification node that must complete before the workflow starts to prevent compliance risks from subsequent process triggers. Associate vulnerability reproduction records and scanner results using vulnerability numbers. Configure field matching rules in the workflow to automatically aggregate data for the same vulnerability from different sources. Add a manual confirmation node for manual verification records, and reserve slots for inserting manual review links to adapt to the verification process of red team engineers. This workflow is compatible with FastGPT v4.17.0.
How to set the configurations
| Configuration Item | Recommended Approach | Basis for This Approach |
|---|---|---|
variables | Predefine project number and vulnerability database version parameters by project dimension | Adapt to the data characteristics updated per project, avoid global parameter conflicts |
| Start node trigger condition | First verify the upload status of the test authorization letter, then trigger subsequent processes | Ensure compliant authorization is completed first, avoid legal authorization dispute risks |
nodeId | Assign a unique nodeId for each document type, for example, the authorization letter node id is auth_001 | Ensure process nodes for different documents can be independently configured and monitored |
| Node timeout threshold | 600 seconds | Adapt to the conventional time range of manual verification links, avoid unexpected process interruptions |
| Single-node file upload limit | 50 MB | Adapt to the conventional size of documents such as test authorization letters and vulnerability reports |
| Vulnerability data aggregation rule | Match scanner results and reproduction records by vulnerability number, aggregate the first 8 pieces of data | Ensure multi-source data for the same vulnerability can be automatically associated, reduce manual organization costs |
| Manual review node trigger condition | Trigger when there is a difference between scan results and reproduction records | Adapt to the manual verification and risk rating needs of red team engineers |
Three common mistakes
- Symptom: The workflow does not respond after starting, and the log shows that the
variablesparameter is empty. Cause: The project-related global variables are not pre-defined during the workflow initialization phase, causing subsequent nodes that depend on the variables to fail to execute normally. - Symptom: The HTTP request node cannot transfer TXT format files, and returns status code 400. Cause: The request header and form parameters are not configured correctly, and the TXT file is not bound to the request body as a binary stream.
- Symptom: After importing someone else's workflow, the text processing module cannot be found locally. Cause: The local FastGPT version has not been updated to the version that supports this module, or the module has not been enabled in the application marketplace.
How to confirm the configuration is complete
- Upload a test authorization letter, trigger the workflow start, and check whether it automatically proceeds to subsequent nodes.
- Call the bound scanner result interface, verify whether the vulnerability number matching rule takes effect, and confirm that aggregated documents are complete.
- Manually modify the difference items between scan results and reproduction records, and check whether the manual review node triggers.
- View the process monitoring panel, confirm that the node status corresponding to
nodeIdis normal, and there are no timeout errors.
The values provided here 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.