Code Audit Finding

Code Audit Finding Overlay

This skill adapts the code-audit-main knowledge base for DeepAudit's Finding agent.

Use this skill to strengthen source-code auditing for:

• authorization and access-control flaws
• IDOR and tenant-isolation issues
• business-logic and state-machine flaws
• file operations and path handling
• input-validation gaps
• attack-chain driven source-to-sink review

This skill keeps DeepAudit's current role split intact:

• recon provides project navigation and scope
• finding produces source-audit conclusions
• verification performs follow-up validation

Required Startup Protocol

1. Read this SKILL.md first with read_file(skill_file_path).
2. Read at most one or two core references before you return to project code:
   • references/core/anti_hallucination.md
   • references/core/false_positive_filter.md
3. After bootstrap, immediately audit the active candidate code path with read_many_files or Action Batch.
4. Read additional checklist/framework/security references only when the current code path needs them.
5. Do not claim a checklist, framework rule, control requirement, or case pattern unless you have actually read the corresponding file.
6. Do not loop on skill materials. Skill references are just-in-time guidance, not a preload queue.

Minimal Bootstrap Order

After reading this SKILL.md, you may read these core files first if the current code path still needs more review structure:

• references/core/anti_hallucination.md
• references/core/false_positive_filter.md

Only read the files below when the current candidate needs them:

• references/checklists/coverage_matrix.md
• references/core/comprehensive_audit_methodology.md
• references/core/data_flow_methodology.md
• references/core/taint_analysis.md

Conditional Reference Reading

After the minimal bootstrap, route by project signals:

• Languages:
  • references/checklists/<language>.md
  • references/languages/<language>.md
• Frameworks:
  • references/frameworks/<framework>.md
• Security domains:
  • references/security/authentication_authorization.md
  • references/security/business_logic.md
  • references/security/file_operations.md
  • references/security/input_validation.md
  • references/security/api_security.md
  • references/security/race_conditions.md
  • plus other matching files under references/security/
• Control verification:
  • references/adapters/<language>.yaml

Finding-Specific Constraints

• Audit must stay evidence-driven.
• Cases and historical vulns can guide search direction, but they never count as evidence.
• If you have not read the relevant reference file, do not say that topic is fully audited.
• If you want to claim a missing control at high confidence, read the matching adapter first.
• Use the references to guide code reading, not to replace code reading.
• Prefer returning to project code after each reference read instead of opening many skill files back-to-back.

Preserved Methodology Reference

The following sections are preserved because they carry important audit methodology, coverage, and anti-bias constraints from the original code-audit knowledge base.

DeepAudit runtime still uses the minimal bootstrap order above for efficient execution, but these sections remain authoritative reference material for how the audit should be reasoned about and validated.

Execution Controller（执行控制器 — 必经路径）

⚠️ 以下步骤是审计执行的必经路径，不是参考建议。 每步有必须产出的输出，后续步骤依赖前序输出。不产出 = 用户可见缺失。

Step 1: 模式判定

根据用户指令确定审计模式：

反降级规则: 用户指定的模式不可自行降级。项目规模大不是降级理由，而是启用 Multi-Agent 的理由。降级需用户明确确认。

必须输出:

[MODE] {quick|standard|deep}

Step 2: 文档加载

按模式加载必要文档（用 Read 工具实际读取，不是"知道有这个文件"）：

deep 模式下 agent.md 是必读文档 — Step 4 的执行计划模板包含只有 agent.md 中才有的字段（维度权重、Agent 切分模板、门控条件、执行状态机）。

必须输出:

[LOADED] {实际 Read 的文档列表，含行数}

Step 3: 侦察（Reconnaissance）

对目标项目执行攻击面测绘。

必须输出:

[RECON]
项目规模: {X files, Y directories}
技术栈: {language, framework, version}
项目类型: {CMS | 金融 | SaaS | 数据平台 | 身份认证 | IoT | 通用Web}
入口点: {Controller/Router/Handler 数量}
关键模块: {列表}

Step 4: 执行计划 → STOP

基于 Step 1-3 的输出生成执行计划。输出后暂停，等待用户确认才能继续。

quick/standard 模板:

[PLAN]
模式: {mode}
技术栈: {from Step 3}
扫描维度: {计划覆盖的 D1-D10 维度}
已加载文档: {from Step 2}

deep 模板（全部字段必填 — 标注了信息来源文档）:

[PLAN]
模式: deep
项目规模: {from Step 3}
技术栈: {from Step 3}
维度权重: {from agent.md 状态机 → 项目类型维度权重，如 CMS: D5(++), D1(+), D3(+), D6(+) }
Agent 方案: {from agent.md Agent 模板 → 每个 Agent 负责的维度和 max_turns}
Agent 数量: {from agent.md 规模建议 → 小型(<10K) 2-3, 中型(10K-100K) 3-5, 大型(>100K) 5-9}
D9 覆盖策略: {若项目有后台管理/多角色/多租户 → D9 必查，D3 Agent 须同时覆盖 D9a(IDOR+权限一致性+Mass Assignment)}
轮次规划: R1 广度扫描 → R1 评估 → R2 增量补漏(按需)
门控条件: PHASE_1_RECON → ROUND_N_RUNNING → ROUND_N_EVALUATION → REPORT
预估总 turns: {Agent数 × max_turns}
已加载文档: {from Step 2}

⚠️ STOP — 输出执行计划后暂停。等待用户确认后才能开始审计。

Step 5: 执行

用户确认后，按执行计划和已加载文档执行：

• quick: 高危模式匹配扫描，直接输出
• standard: 按 Phase 1→5 顺序执行
• deep: 严格按 agent.md 执行状态机
  • 启动 Multi-Agent 并行（按 Step 4 确认的 Agent 方案）
  • 遵守每个 State 的门控条件
  • 轮次评估使用 agent.md 三问法则

Step 6: 报告门控

生成报告前验证：

不满足前置条件 → 不得生成最终报告。

Anti-Hallucination Rules (MUST FOLLOW)

⚠️ Every finding MUST be based on actual code read via tools

✗ Do NOT guess file paths based on "typical project structure"
✗ Do NOT fabricate code snippets from memory
✗ Do NOT report vulnerabilities in files you haven't read

✓ MUST use Read/Glob to verify file exists before reporting
✓ MUST quote actual code from Read tool output
✓ MUST match project's actual tech stack

Core principle: Better to miss a vulnerability than report a false positive.

Anti-Confirmation-Bias Rules (MUST FOLLOW)

⚠️ Audit MUST be methodology-driven, NOT case-driven

✗ Do NOT say "基于之前的审计经验，我将重点关注..."
✗ Do NOT prioritize certain vuln types based on "known CVEs"
✗ Do NOT skip checklist items because they seem "less likely"

✓ MUST enumerate ALL sensitive operations, then verify EACH one
✓ MUST complete the full checklist for EACH vulnerability type
✓ MUST treat all potential vulnerabilities with equal rigor

Core principle: Discover ALL potential vulnerabilities, not just familiar patterns.

Two-Layer Checklist (两层检查清单)

Layer 1: coverage_matrix.md — Phase 2A后加载，验证10个安全维度覆盖率 Layer 2: 语言语义提示 — 仅对未覆盖维度按需加载对应段落

核心原则: Checklist 不驱动审计，而是验证覆盖。LLM 先自由审计(Phase 2A)，再用矩阵查漏(Phase 2B)。

Module Reference

Core Modules (Load First)

Language Modules (Load by Tech Stack)

Security Domain Modules (Load as Needed)

Tool Priority Strategy

Priority 1: External Professional Tools (if available)
├─ semgrep scan --config auto          # Multi-language SAST
├─ bandit -r ./src                      # Python security
├─ gosec ./...                          # Go security
└─ gitleaks detect                      # Secret scanning

Priority 2: Built-in Analysis (always available)
├─ LSP semantic analysis                # goToDefinition, findReferences, incomingCalls
├─ Read + Grep pattern matching         # Core analysis
└─ Module knowledge base                # 55+ vuln patterns

Priority 3: Verification
├─ PoC templates from references/core/poc_generation.md
└─ Confidence scoring from references/core/verification_methodology.md

Detailed Documentation

For complete audit methodology, vulnerability patterns, and detection rules, see:

• Full Workflow: agent.md - Complete audit process and detection commands
• Vulnerability Details: references/ - Language/framework-specific patterns
• Tool Integration: references/core/external_tools_guide.md
• Report Templates: references/core/taint_analysis.md

Version

• Current: 1.0
• Updated: 2026-02-13

v1.0 (Initial Public Release)

• 9语言143项强制检测清单 (references/checklists/)
• 双轨并行审计框架: Sink-driven + Control-driven + Config-driven
• Docker部署验证框架 (references/core/docker_verification.md)
• WooYun 88,636案例库集成
• 安全控制矩阵框架

Progressive Disclosure for WooYun and Cases

Use four levels of disclosure:

1. Default:
   • do not preload WooYun case bodies
2. Index first:
   • read references/wooyun/INDEX.md
3. Evidence-gated expansion:
   • only after you already have project-specific code evidence may you read one or two related case files
4. Strict evidence boundary:
   • WooYun and real-world cases only expand search directions, bypass ideas, and missed-check hints
   • they do not justify a finding on their own

Relevant case sources:

• references/wooyun/
• references/cases/real_world_vulns.md

Intentionally Excluded From Required Runtime Flow

agent.md is preserved in this skill root for reference, but its deep multi-agent orchestration is not part of Finding's required runtime reading path.

The original upstream SKILL.md is preserved at:

• references/core/original_skill_reference.md