一键导入
confidence-methodology
Methodology for scoring confidence in secret validation findings.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Methodology for scoring confidence in secret validation findings.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Effective usage of GitHub API tools for fetching secret scanning alerts and locations.
Guidelines for setting up isolated testing environments for secret validation scripts.
Techniques for analyzing code context around secret locations to understand usage and intent.
Strategies for cloning repositories with full history into the workspace for analysis.
Use the validate-secrets tool for deterministic secret validation when a matching validator is available.
Verification guide specific to HTTP Basic Authentication credentials.
| name | confidence-methodology |
| agent | analysis |
| description | Methodology for scoring confidence in secret validation findings. |
| phase | 4-scoring-and-reporting |
| required | true |
This skill provides the established methodology for scoring confidence in your secret validation findings.
The overall confidence score is calculated from seven factors, each scored 0-10:
| Factor | Description | Weight |
|---|---|---|
| Recency | How recent is the information (commits, sources) | Equal |
| Directness | Direct evidence vs. inferred/indirect | Equal |
| Completeness | Full context vs. partial understanding | Equal |
| Source Reliability | Official docs vs. unofficial sources | Equal |
| Verification Confidence | Confidence in your test methodology | Equal |
| Test Results | Actual results from validation tests | Equal |
| Findings Review | First-principles review of conclusions | Equal |
How recent is the evidence you're evaluating?
| Score | Criteria |
|---|---|
| 9-10 | Data from last 7 days |
| 7-8 | Data from last 30 days |
| 5-6 | Data from last 90 days |
| 3-4 | Data from last year |
| 1-2 | Data older than 1 year |
| 0 | Cannot determine age |
Is your evidence direct or inferred?
| Score | Criteria |
|---|---|
| 9-10 | Direct observation (e.g., auth test succeeded) |
| 7-8 | Strong direct evidence (e.g., code shows active use) |
| 5-6 | Indirect but clear evidence |
| 3-4 | Mostly inferred from context |
| 1-2 | Speculation based on patterns |
| 0 | No direct evidence available |
How complete is your understanding of the context?
| Score | Criteria |
|---|---|
| 9-10 | Full context: all files, all branches, all history |
| 7-8 | Most context gathered, minor gaps |
| 5-6 | Key context present, some areas unexplored |
| 3-4 | Partial context, significant gaps |
| 1-2 | Minimal context, mostly unknown |
| 0 | No context available |
How reliable are your information sources?
| Score | Criteria |
|---|---|
| 9-10 | Official documentation, verified APIs |
| 7-8 | Reputable sources, official examples |
| 5-6 | Community sources, Stack Overflow answers |
| 3-4 | Unofficial sources, blog posts |
| 1-2 | Unverified sources |
| 0 | No external sources consulted |
How confident are you in your verification approach?
| Score | Criteria |
|---|---|
| 9-10 | Standard verification method, well-documented |
| 7-8 | Solid approach with minor uncertainties |
| 5-6 | Reasonable approach, some assumptions |
| 3-4 | Approach has significant limitations |
| 1-2 | Verification method questionable |
| 0 | Could not verify at all |
What did your actual tests show?
| Score | Criteria |
|---|---|
| 9-10 | Clear positive/negative result from tests |
| 7-8 | Strong test results with minor ambiguity |
| 5-6 | Tests ran but results ambiguous |
| 3-4 | Limited testing possible |
| 1-2 | Tests failed/inconclusive |
| 0 | Could not run tests |
Did first-principles review confirm your findings?
| Score | Criteria |
|---|---|
| 9-10 | Review confirms all findings, no contradictions |
| 7-8 | Review mostly confirms, minor concerns addressed |
| 5-6 | Review shows some gaps, conclusions still hold |
| 3-4 | Review reveals significant issues |
| 1-2 | Review contradicts initial findings |
| 0 | No review conducted |
Overall Score = (Recency + Directness + Completeness + Source Reliability
+ Verification Confidence + Test Results + Findings Review) / 7
| Average Score | Confidence Level |
|---|---|
| 8.0 - 10.0 | High |
| 5.0 - 7.9 | Medium |
| 0.0 - 4.9 | Low |
Include this table in Section 7 of your report:
## 7. Confidence Scoring (0–10 each)
| Factor | Score | Rationale |
| ----------------------- | ----- | ------------------------------------------------ |
| Recency | 8 | Alert detected within last 7 days |
| Directness | 9 | Credential directly present in source code |
| Completeness | 7 | Full context gathered, minor gaps in history |
| Source Reliability | 8 | Official GitHub API and documentation used |
| Verification Confidence | 5 | Cannot test internal endpoint |
| Test Results | 6 | Format valid; endpoint unreachable |
| Findings Review | 7 | Review confirms exposure, password strength low |
**Average:** **7.1/10** → **Medium**
For each score, document:
Combine confidence score with risk level for final verdict:
| Confidence | Risk Evidence | Recommended Verdict |
|---|---|---|
| High | Strong risk indicators | TRUE_POSITIVE |
| High | No risk indicators | FALSE_POSITIVE |
| Medium | Strong risk indicators | TRUE_POSITIVE |
| Medium | No risk indicators | INCONCLUSIVE |
| Low | Any | INCONCLUSIVE |
Before finalizing your confidence score: