π§ͺ Use this template to document a repeatable lab environment. Replace the bracketed prompts and remove this note before publishing.
| Lab details | |
|---|---|
| Author | Name |
| Last verified | YYYY-MM-DD |
| Difficulty | Beginner / Intermediate / Advanced |
| Estimated time | Duration |
| Environment | Hypervisor, cloud, operating systems, or platform |
π― Objectives
By the end of this lab, the reader will be able to:
- Learning objective
- Learning objective
- Learning objective
β οΈ Safety and authorization
Describe isolation requirements, authorization boundaries, destructive actions, malware precautions, or data-handling rules.
πΊοΈ Architecture
flowchart LR
A[Management workstation] --> B[Lab network]
B --> C[System 1]
B --> D[System 2]
π₯οΈ Environment inventory
| System | Role | Operating system | Address | Resources |
|---|---|---|---|---|
| Name | Purpose | OS/version | IP or DNS | CPU/RAM/storage |
β Prerequisites
- Required software or images
- Required access or accounts
- Snapshots, backups, or isolation controls
ποΈ Build procedure
1. Prepare the environment
Steps, configuration, and commands.
2. Deploy the systems
Steps, configuration, and commands.
3. Configure the lab
Steps, configuration, and commands.
π§ͺ Validation
Verify the environment before using it:
- Connectivity test
- Service or configuration check
- Expected output
βΆοΈ Lab exercise
- Exercise step
- Exercise step
- Exercise step
π§Ή Reset and teardown
Explain how to revert snapshots, remove temporary data, rotate credentials, or safely dismantle the lab.
π‘ Findings and lessons learned
- Observation
- Unexpected behavior
- Improvement for the next build