Chapter 1 · Permission and Evidence
1. Set the Assessment Scope
Use written rules of engagement to decide whether an assessment activity is allowed.
Video transcript
You have permission. But for what exactly? Written scope names the systems, the allowed activities and the time window for an assessment. It also tells you when to stop. The owner names the practice booking app, which contains fictional customers and bookings. The agreement allows a review of test records during a specific window. When the live app comes up, the assessor checks the scope and leaves it alone. Approved assets and activities define what you can do. Stop when the work crosses that boundary and contact the owner. Confirm the exact asset with the owner. Check which activities are allowed, and when. Agree where to report a problem or stop condition. Write the scope before you begin, then use the knowledge check to practice spotting its limits.
Course outlineLesson 1 of 8
Lesson notes
Ethical hacking starts with explicit permission from someone authorized to give it. Record the exact environment, allowed actions, time window, and point of contact before you begin.
In this course, the owner has approved reviewing synthetic bookings in a fictional staging app. The live app sits outside that approval. A new asset, action, or time window needs its own approval.
Agree on stop conditions in advance. If real customer data appears, stop the activity, limit further exposure, and contact the person named in the plan.
Try it
Write four lines of scope for the practice booking app. Include the authorized environment, the permitted activity, when the review ends, and who to contact if it must stop.
1. The document approves record review in staging. What should you do before reviewing the live booking app?
2. The approved review window ends while you are still working. What comes next?
3. A staging record unexpectedly contains real customer data. What should you do first?