Vulnerability Assessment¶
Assessment is where broad reconnaissance gets narrowed into reproducible security hypotheses.
Working model¶
- Use automation for coverage, not as final proof.
- Use manual validation for context, exploitability, and impact.
- Keep test cases small enough that you can explain exactly what changed between requests.
Assessment loop¶
- Prioritize the inventory by exposure, trust boundary, and probable impact.
- Build hypotheses from versions, banners, framework behavior, and business logic.
- Validate one hypothesis at a time.
- Record the request, response, and conclusion immediately.
- Escalate to exploitation only after you can explain the issue clearly.
Evidence standards¶
- Exact target and path
- Authentication state and privilege level
- Minimal reproduction steps
- Observed result
- Why the result matters
Common failure modes¶
- Treating scanner output as a finding
- Testing too many variables at once
- Losing raw evidence while chasing impact
- Overstating severity before proving exploitability