What this category's data looks like
Data for this category is generated across the full lifecycle of cybersecurity level protection assessment. Core daily documents include four core types: classification reports, gap analysis reports, rectification plans, and assessment reports. Data sources include assessment tool output results, on-site interview records, asset system inventories, and security device operation logs. Data updates follow individual assessment project cycles. Updates are rolled out gradually during the project as materials are organized, gaps are verified, and rectification work progresses. The volume of data for a single project varies based on system scale and assessment depth. Core fields include control item number, gap description, rectification evidence link, and assessment conclusion. There are no unified fixed units; fields and units adjust based on document type.
What constraints these characteristics impose on source citation and traceability
Data for this category is scattered across multiple sources such as assessment tools, interview records, and system inventories. Updates follow individual project cycles, so citation traceability first requires distinguishing context boundaries for different projects to avoid mixing data across projects. Fields in core documents vary significantly by type. Citations must retain exclusive original document fields such as control item numbers and rectification evidence identifiers to enable rapid matching of corresponding links during traceability. Rectification evidence relies on storage paths from original materials. Citations must be linked to the specific source location of the evidence to prevent cases where evidence cannot be traced. Improper traceability configuration may lead to the use of expired materials, creating a risk that assessment materials do not meet requirements.
How to set configurations
This configuration is based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Aligns with the single-paragraph text length of level protection reports, avoiding truncation of core control item content |
responseData | Return only associated documents | Ensures output only includes traceability content directly related to assessment items, avoiding interference from irrelevant information |
detail | Enable full traceability | Retains fields and structure from original documents to facilitate verification of original rectification evidence information |
| Maximum context length | First 3 rounds of conversation context | Aligns with project background for multi-round communication during level protection assessments, retaining early classification and gap analysis information |
| Single recall limit | Top 5 results | Controls the number of returned traceability documents, avoiding information overload that impacts review efficiency |
Three common misconfigurations
- Phenomenon: Only citation links and source descriptions are returned, with no corresponding business content. Cause: The
detailparameter is not configured correctly. Only the traceability switch is enabled, but full content return is not activated, resulting in only sources being displayed without core assessment information. - Phenomenon: The citation view function prompts that it cannot be activated when accessing a shareable link without logging in. Cause: The traceability verification rule for share permissions is not adjusted in the application configuration, or the share scope of traceability documents is not set to public, resulting in unauthenticated users being unable to access original documents.
- Phenomenon: Earlier classification report content cannot be linked in multi-round conversations. Cause: The correct context recall range is not configured. Only the current single-round input is called, and earlier project background information is not retained, resulting in traceability failing to match the corresponding document.
How to confirm correct configuration
- A single-round query for an assessment item is initiated, and the returned results are checked for the control item number and rectification evidence link from the original document to confirm the configuration is active.
- A multi-round query that includes earlier project background information is initiated, and whether content from the classification report or gap analysis report can be linked is checked to confirm the context recall configuration is correct.
- A shareable link without login requirements is generated, access is attempted without logging in, and whether the citation view function can normally open the original document is checked to confirm the share scope configuration is correct.
- The value of
quoteMaxTokenis adjusted, long-text recall is tested for appropriate handling, and the token length configuration is confirmed to meet document requirements.
The values provided are common starting points and should be measured against the user'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.