This document covers vulnerability disclosure and security-related practices for the DocSentinel project — an AI-powered SSDLC platform. It aligns with PRD §7.2 Security Requirements and Controls.
本文档涵盖 DocSentinel 项目(AI 驱动的 SSDLC 平台)的漏洞披露与安全实践,遵循 PRD §7.2 安全需求与控制。
| Version | Supported |
|---|---|
| 4.0.x | ✅ |
| 3.1.x | ✅ |
| 3.0.x | ✅ |
| 2.0.x | |
| < 2.0 | ❌ |
If you discover a security vulnerability, please report it responsibly:
- Do not open a public GitHub issue for security-sensitive findings.
- Email the maintainers (e.g. the contact in the PRD:
[email protected]) with:- A description of the vulnerability and steps to reproduce.
- Impact and suggested fix if possible.
- We will acknowledge receipt and aim to respond within a reasonable timeframe. We may ask for more details and will keep you updated on remediation and disclosure.
如果您发现了安全漏洞,请负责任地进行报告:
- 请勿针对敏感安全问题提交公开的 GitHub Issue。
- 请发送邮件给维护者(联系方式见 PRD:
[email protected]),包含:- 漏洞描述与复现步骤。
- 影响范围与建议修复方案(如有)。
- 我们将在合理时间内确认收到并回复。可能会向您询问更多细节,并同步后续的修复与披露进度。
-
Secrets: Do not commit
.envor any file containingSECRET_KEY, API keys, or passwords. Use.env.exampleas a template only. -
Input Validation: File type and size limits are enforced (see
UPLOAD_MAX_FILE_SIZE_MB,UPLOAD_MAX_FILES). Only allowed extensions are parsed (seeapp/parser/service.py). -
Prompt Injection Guardrails: Input sanitization via regex pattern detection and length limits is enforced before content reaches the LLM (see
app/core/guardrails.py). Malicious inputs are rejected with HTTP 400. -
TLS: In production, use HTTPS and TLS 1.2+ for all endpoints and external calls (PRD §7.2 DATA-01).
-
Auth: API currently does not enforce authentication in the MVP; add AAD/API Key as per PRD §7.2 IAM before exposing externally.
-
LangGraph State: Assessment state and checkpoints may contain sensitive document content. Ensure
LANGGRAPH_CHECKPOINT_DIRis on encrypted storage in production. -
SAST/DAST Integration: When ingesting scan results from external tools, validate report integrity and source authenticity.
-
机密信息:请勿提交
.env或任何包含SECRET_KEY、API Key、密码的文件。.env.example仅作为模板使用。 -
输入验证:强制执行文件类型与大小限制(见
UPLOAD_MAX_FILE_SIZE_MB、UPLOAD_MAX_FILES)。仅解析允许的扩展名(见app/parser/service.py)。 -
提示注入防护:通过正则模式检测和长度限制对输入进行清洗,在内容到达 LLM 之前执行(见
app/core/guardrails.py)。恶意输入将被 HTTP 400 拒绝。 -
TLS:生产环境中,所有端点与外部调用必须使用 HTTPS 和 TLS 1.2+(PRD §7.2 DATA-01)。
-
认证:MVP 阶段 API 暂未强制认证;在对外暴露前,请根据 PRD §7.2 IAM 添加 AAD/API Key 认证。
-
LangGraph 状态:评估状态和检查点可能包含敏感文档内容。生产环境中请确保
LANGGRAPH_CHECKPOINT_DIR位于加密存储上。 -
SAST/DAST 集成:从外部工具接入扫描结果时,请验证报告完整性和来源真实性。
-
SPEC.md Section 7.2 — Security Requirements and Controls (identity, data, application, operations, supply chain).
-
ARCHITECTURE.md — System architecture with LangGraph design and security architecture section.
-
docs/05-deployment-runbook.md — Deployment, configuration, and network requirements.
-
SPEC.md 第 7.2 节 — 安全需求与控制(身份、数据、应用、运维、供应链)。
-
ARCHITECTURE.md — 系统架构,含 LangGraph 设计与安全架构章节。
-
docs/05-deployment-runbook.md — 部署、配置与网络需求。