> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/gai-shu-yu-ji-chu/vulnerability-management.md).

# 漏洞管理

于 **2026 年 10 月 16 日**核查。

## 已知 CVE

在核查日，对 [CVE.org](https://www.cve.org/)、[NVD](https://nvd.nist.gov/) 和 [Tenable Research Advisories](https://www.tenable.com/security/research) 的公开搜索未发现以 DocBits 命名的安全通告。这并不能证明应用或依赖项没有漏洞。这些来源无法替代对已部署版本及当前漏洞登记表的评估。要明确回答是否存在尚未解决的 CVE，需要 FELLOWPRO 提供该评估。

## 评估与修复

[认证](/chinese/gai-shu-yu-ji-chu/architecture/certifications.md)页面链接的报告提供以下证据：

* 2026 年签发的 SOC 2 Type II 报告涵盖 **2024 年 10 月 1 日至 2025 年 9 月 30 日**。报告描述定期内部扫描、**至少每年一次的第三方网络漏洞评估及渗透测试**，以及对发现问题的跟踪直至关闭。
* ISO 27001 监督审核报告记录了对 **2025 年 10 月 30 日** VA/PT 报告的审查，所评估问题已关闭。这并未确定其后所有测试的日期或结果。
* GDPR 审计描述定期产品漏洞评估及及时修复严重漏洞。
* SOC 报告描述生产部署前对操作系统及网络补丁进行稳定性与可用性测试、定期更新及应对严重事件，但未确定每个严重级别的具体修复天数。

如需最新测试范围、报告、未关闭问题及合同修复目标，请联系 **<compliance@fellowpro.com>**。历史审计结果不能替代当前漏洞扫描。

## 更新与报告

[发布生命周期策略](/chinese/gai-shu-yu-ji-chu/docbits-release-lifecycle-strategy.md)提供参考计划：主要及次要版本约每 3–4 个月，VESTA 热修复约每月或更长；NOVA 稳定性修复取决于具体版本。这些是计划估计，不是安全修复期限。发布流程包括 QA 和沙箱验收测试。

已查材料未确立公开漏洞赏金计划、奖励条件或获准测试范围。在声明提供此类计划前，应与 FELLOWPRO 确认。安全报告及渗透测试摘要请求可发送至 **<compliance@fellowpro.com>**；该联系地址本身不代表获准测试生产系统。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/chinese/gai-shu-yu-ji-chu/vulnerability-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.