Authorized hacking lab and written scope

1. Before testing, document who owns the system, the permitted targets, the time window and the stop conditions.

2. Prefer your own local application, an intentionally vulnerable practice machine or a published training lab. A publicly reachable device is not automatically in scope.

3. Record software versions, expected behavior and observed behavior in a small notebook.

4. Stop and seek permission when a test touches other people's data, networks or accounts.

5. Exercise: write an authorization and rollback checklist for a local test project.

Scope: Education and testing on owned or explicitly authorized systems only.