Overview
Placeholder overview: describe the problem, the environment, the authorized scope, and what made the project interesting. Keep sensitive client or target details anonymized.
Scope & Constraints
Use this area to describe what was allowed, what was excluded, assumptions, safe testing rules, and any privacy or disclosure boundaries.
In Scope
Placeholder: systems, features, labs, targets, or workflows included in the project.
Out of Scope
Placeholder: client identifiers, destructive actions, unsafe exploit details, or production-sensitive data.
Process
Replace these phases with your actual workflow. Keep it readable: what you did, why it mattered, and what changed after each phase.
Placeholder: discovery, scope confirmation, threat model, environment setup, and rules of engagement.
Placeholder: implementation, testing, exploitation path validation, automation, or prototype buildout.
Placeholder: reporting, remediation support, detection mapping, lessons learned, and next iteration.
Media
Add safe visuals here: redacted screenshots, architecture diagrams, terminal captures, demo GIFs, or report excerpts.
Keep images redacted and safe to publish.
Lessons Learned
Placeholder notes: what changed, what was difficult, what you would improve, and what readers should take away from the project.
What Worked
Placeholder: effective design choices, useful tools, strong assumptions, or successful techniques.
What To Improve
Placeholder: cleanup tasks, future features, documentation gaps, or testing improvements.