Good documentation turns a de4dot analysis into a report that other people can understand and check. Clear notes, honest limits, and safe handling of evidence make your findings more useful and more credible.
Record the basics first
Start with the file name, the steps you took, the tools you used, and the environment where you tested. These basics let another person repeat your work and understand the context. Keep the original file details separate from the cleaned output details.
Describe what you found, plainly
Describe the main behaviour in plain language, then add technical detail where it helps. Focus on what the program does, what data it touches, and what risks you observed. Avoid guessing about purpose when the evidence is unclear, and say so when it is.
State limits and uncertainty
Note any parts that stayed unclear, any missing libraries, and any tests you could not run safely. Honest limits do not weaken a report, they help readers judge how much weight to give each finding. Mark uncertain findings clearly, so they are not treated as proven facts.
Handle evidence safely
Keep copies of your notes and results in a safe place, and avoid sharing harmful files or sensitive data in the report itself. Share only what the reader needs, and use safe examples instead of full harmful code where possible.
For safe testing, see setting up a safe virtual machine for de4dot analysis. For output basics, see de4dot cleaned output file explained.
Frequently Asked Questions
What should a security report include
Basics, plain findings, evidence, limits, and clear next steps.
Should I include full harmful code
No, include only what is needed, and use safe examples where possible.
How do I handle uncertain findings
Mark them as uncertain and explain what evidence is missing.
Should I keep the original file
Keep it safely for reference, but do not share it without care.
Can a short report be useful
Yes, a short clear report is better than a long unclear one.


