Home labs & practical projects
Harden a small Linux service and verify the change
A project to do with your own tools, with guidance on what to create and capture.
What you could create
A test server hosts a simple internal service with unnecessary accounts and broad network exposure. You need to improve its baseline without losing availability.
| Evidence | What to capture |
|---|---|
| Baseline change register | Show the inputs, scope and decisions behind this record. The required service remains usable. |
| Service and access validation results | Include the evidence supporting your conclusion. The evidence demonstrates control enforcement and a recovery path. |
What you'll need
Local lab
Use a disposable Linux VM, a harmless local web service and a clean snapshot. Record accounts, listening services and initial connectivity.
Project record
Keep the working files for baseline change register 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
Uses your own computer. Confirm hardware capacity, software licences and download terms before setup.
Use disposable VMs, containers or a simulator. Keep the lab separate from your everyday machine and work network.
Suggested milestones
- 1
Plan and investigate
Identify unnecessary privileges and exposed services.
- 2
Develop your approach
Apply a small set of justified baseline changes.
- 3
Verify and explain
Test the permitted service path, a blocked path and recovery from a mistaken rule.
Useful resources
Use these resources to deepen your understanding and check key details.
Review the current provider requirements and relevant subject areas.
Check relevance, platform versions and current access terms.
Find relevant providers and check features, access requirements and costs.
A useful starting point
Use a disposable Linux VM, a harmless local web service and a clean snapshot. Record accounts, listening services and initial connectivity.
What a good result looks like
- The required service remains usable.
- The evidence demonstrates control enforcement and a recovery path.
Finish the project
Save sanitised evidence, then remove the lab instances or revert to the clean snapshot. Remove temporary accounts and credentials.
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.