Protego field desk

Chapter 1 · Permission and Evidence

2. Capture Useful Evidence

Record what happened and keep only the evidence needed to explain it.

Video transcript

A screenshot helps. A clear record helps more. Evidence lets an owner understand what you observed. A useful record pairs the expected behavior with the observed behavior. A synthetic booking shows the wrong role label. Capture the label and test context. Crop unrelated fields and redact private information while keeping what supports the observation. Place the redacted note in the agreed location, where authorized reviewers can read it. The screenshot can establish which label was displayed. You need separate evidence to draw a conclusion about permissions. Record the time, environment and role. Document what should have happened and what did. Keep a minimal record and follow the agreed retention plan. Give the reviewer enough to follow your reasoning. Use the knowledge check to choose what to keep.

Course outlineLesson 2 of 8
Ethical Hacking for Beginners: course overview

Lesson notes

Capture the environment, time, test role, expected behavior, and observed behavior. Record those details together so a reviewer can tell which result came from which check.

A screenshot showing the wrong role label establishes what appeared on screen. Treat the underlying permissions as unverified until you have evidence about what the server allowed.

Crop unrelated data, redact sensitive fields, and share what remains through the agreed private channel. Follow the agreed retention schedule for working copies.

Try it

Draft an evidence note for a synthetic viewer who sees an editor label. Record the two labels and leave the actual edit permission marked as unverified.

NIST SP 800-115
Knowledge Check

1. Which record gives an owner enough information to interpret the observation?

2. The only evidence is an editor label shown to a viewer. What can you report?

3. Who should receive the evidence?