Testing Workflow & Reporting
Writing a security finding
| Section | Include |
|---|---|
| Title | Clear vulnerability name |
| Impact | What an attacker could achieve |
| Evidence | Minimal reproducible proof |
| Root cause | Why the weakness exists |
| Remediation | Specific engineering fix |
| Retest | Whether the fix worked |
A strong report helps engineers fix the issue. Avoid sensational wording; explain the security boundary, affected component and practical remediation.
Lesson complete?Use the next lesson to continue the learning path.