EVIDENCE · REFLECTION · GRADING
Prove it, reflect on it, get it verified
Pick a week, check off your evidence and safety boundaries, answer the reflection questions, and have your instructor grade against the rubric. Everything saves on this device.
Lab evidence checklist
This week asks for: Completed 5-framework control crosswalk.
Safety & authorization boundaries
Student reflection
Q1 What did you observe, and was it what you expected? If not, why?
Q2 Which security control or standard applied, and how did it change the outcome?
Q3 What would have happened in a real organization if this control were missing?
Q4 What safety or authorization boundary mattered most in this lab?
Q5 How would you explain this finding to an executive in two sentences?
Q6 What would you do differently next time, and what do you still not understand?
Instructor verification rubric
0/100
Not fully graded
| Criterion | Insufficient | Developing | Proficient | Exemplary |
|---|---|---|---|---|
| Safety & authorization 20% | ||||
| Technical execution 25% | ||||
| Evidence quality 20% | ||||
| Control mapping 15% | ||||
| Communication 20% |
Instructor validation checklist
Every lab includes these 20 elements
- 1. Lab title
- 2. Business or operational scenario
- 3. Learning objectives
- 4. Standards and controls being practiced
- 5. Network or system diagram
- 6. Required hardware and software
- 7. Virtual machines or Docker containers required
- 8. AR/VR assets required
- 9. Estimated completion time
- 10. Setup instructions
- 11. Student instructions
- 12. Expected observations
- 13. Evidence to collect
- 14. Troubleshooting guidance
- 15. Cleanup and system-reset instructions
- 16. Safety and authorization boundaries
- 17. Instructor validation checklist
- 18. Student reflection questions
- 19. Grading rubric
- 20. Workplace application