Repository navigation
Client Assessment Findings DefectDojo and Retesting Workflow
Last reviewed: 2026-11-02 (documentation review; no issue tracker installed)
Prerequisites: Network audit ยท WebApp testing ยท Cloud/SCuBA assessment.
DefectDojo is a vulnerability and findings-management platform for organizing scan results, manual observations, duplicates, verification and follow-up. Its docs explain supported deployment and integrations. It is a potential backend for staged client assessments, not a substitute for authorization or a customer-ready report.
No DefectDojo installation or automatic scanner import was performed. Before accepting client information, verify application deployment support, MFA/SSO, client isolation, RBAC, retention, access logging, encrypted backups and export controls.
- Authorize: record legal entity, approved hosts/accounts, internal/external exclusions, testing methods, maintenance windows, safety contacts and signed rules of engagement.
- Create engagement: assign client/job ID, assessor, encrypted evidence folder, agreed report recipients and an isolated tracking context.
- Ingest: preserve original test provenance: OWASP method, SCuBA baseline, Nuclei template, Wazuh result or manual observation, with tool version, target and UTC timestamp.
- Normalize: record affected asset, sanitized reproducible steps, expected control, observed behavior, business impact, prerequisites and any supportable CVE/CWE/ATT&CK links.
- Deduplicate: combine evidence from tests describing the same root cause without losing independent source provenance; never inflate counts by treating each scanner alert as unique.
- Assign severity: incorporate exploitability, verified exposure and business context. A template's severity tag is not confirmation of a vulnerability.
- Remediate: define owner, recommendation, change/rollback plan, acceptance criteria and due date, approved by the customer.
- Retest: repeat the bounded procedure, preserving before/after evidence. Separate fixed, mitigated, accepted, still open and inconclusive states.
- Close: deliver an executive summary and sanitized technical report, enforce agreed evidence retention, and schedule the next review.
| Field | Required record |
|---|---|
| Customer/engagement | Stable case ID, approved scope reference |
| Asset | System, URL and environment |
| Evidence | Encrypted URI, hash, collection time and provenance |
| Control | Versioned ASVS/WSTG, SCuBA, CIS or internal ID |
| Status | Validation confidence, impact and remediation priority |
| Ownership | Remediation contact, approved exception, review date |
| Retest | New evidence, tester and result |
| Data handling | Recipients, retention and legal hold |
Avoid automatically uploading raw scans, employee identities, network maps or incident evidence to a hosted service without an approved data processing agreement. For later automation use idempotent import keys based on engagement, asset and check ID; never equate a successful import with a verified flaw. Test retention and restoration before use.
- DefectDojo and official documentation (BSD-3-Clause source repository; verify current per-file terms).
- Purple Team validation ยท DFIR triage ยท API catalog.
Playbooks index ยท Main README ยท Legal notice
๐ Source: PlayBooks/assessment-findings-lifecycle.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Playbooks
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics