11 Nov 2026 · 4d ago#1
A strong write-up helps the next person reproduce the reasoning, not just copy a flag. Use this template only for public CTFs, purpose-built labs, or systems you are explicitly authorized to test. Respect event rules and embargoes.
Title and scope — event/lab, challenge name, date, difficulty, and what is in scope. Don’t publish real targets or personal data.
1. Starting observations — what the prompt, files, or lab UI actually showed. Separate facts from guesses.
2. Hypotheses — list two or three plausible explanations and what evidence would distinguish them. This is often the most educational part.
3. Method — explain the sequence of observations and decisions. Include only the commands, code, or screenshots needed to reproduce work in that authorized environment; redact tokens and identifying data.
4. The turning point — what changed your mind? What did you test that did not work, and what did that teach you?
5. Finding and impact — describe the issue in plain language, the preconditions, and the realistic impact inside the lab’s scope. Avoid overstating severity.
6. Fix or defensive lesson — show the safe configuration or design change, plus a regression test that would detect the issue next time.
7. What you would do differently — one improvement to your process, one open question, and references to primary documentation.
Before posting: remove credentials, session IDs, private keys, personal information, and any non-public target details. Check the rules for spoilers and disclosure.
Challenge: write a 5-sentence mini-report for a beginner lab: observation → hypothesis → test → result → fix. Post it and ask for feedback on clarity.
Useful references: [picoCTF](https://picoctf.org/) · [PortSwigger Web Security Academy](https://portswigger.net/web-security) · [OWASP Web Security Testing Guide](https://owasp.org/www-project-web-security-testing-guide/).
Title and scope — event/lab, challenge name, date, difficulty, and what is in scope. Don’t publish real targets or personal data.
1. Starting observations — what the prompt, files, or lab UI actually showed. Separate facts from guesses.
2. Hypotheses — list two or three plausible explanations and what evidence would distinguish them. This is often the most educational part.
3. Method — explain the sequence of observations and decisions. Include only the commands, code, or screenshots needed to reproduce work in that authorized environment; redact tokens and identifying data.
4. The turning point — what changed your mind? What did you test that did not work, and what did that teach you?
5. Finding and impact — describe the issue in plain language, the preconditions, and the realistic impact inside the lab’s scope. Avoid overstating severity.
6. Fix or defensive lesson — show the safe configuration or design change, plus a regression test that would detect the issue next time.
7. What you would do differently — one improvement to your process, one open question, and references to primary documentation.
Before posting: remove credentials, session IDs, private keys, personal information, and any non-public target details. Check the rules for spoilers and disclosure.
Challenge: write a 5-sentence mini-report for a beginner lab: observation → hypothesis → test → result → fix. Post it and ask for feedback on clarity.
Useful references: [picoCTF](https://picoctf.org/) · [PortSwigger Web Security Academy](https://portswigger.net/web-security) · [OWASP Web Security Testing Guide](https://owasp.org/www-project-web-security-testing-guide/).