Home labs & practical projects
Deliver a client debrief for a training assessment
A project to do with your own tools, with guidance on what to create and capture.
What you could create
A fictional client needs to understand the business significance of a permitted internal-network training assessment and which changes to prioritise.
| Evidence | What to capture |
|---|---|
| Executive assessment summary | Show the inputs, scope and decisions behind this record. The debrief distinguishes demonstrated impact from potential impact. |
| Remediation roadmap and debrief outline | Include the evidence supporting your conclusion. The recommended sequence considers business dependencies and retesting. |
What you'll need
Authorised security lab
Use an authorised training environment and its allowed assessment scope. Create a fictional business dependency map for the lab systems.
Project record
Keep the working files for executive assessment summary and record assumptions as you go.
Current reference material
Use the linked provider resources to verify the features, access terms and version relevant to your project.
Access & cost
Use a deliberately vulnerable local image or a licensed training range. Check the provider’s access terms and current price.
Only test systems you own or are explicitly authorised to assess. Keep targets isolated and use synthetic accounts and data.
Suggested milestones
- 1
Plan and investigate
Document the observed exposure path using the range’s permitted exercise.
- 2
Develop your approach
Translate technical findings into business impact and a prioritised remediation sequence.
- 3
Verify and explain
Prepare a five-minute verbal debrief with answers to likely client questions.
Useful resources
Use these resources to deepen your understanding and check key details.
A useful starting point
Use an authorised training environment and its allowed assessment scope. Create a fictional business dependency map for the lab systems.
What a good result looks like
- The debrief distinguishes demonstrated impact from potential impact.
- The recommended sequence considers business dependencies and retesting.
Finish the project
Revert target snapshots, remove test accounts and artefacts, and store a sanitised report. Do not publish credentials or working attack material.
Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.