Home labs & practical projects

Constrain a workload without breaking its job

A project to do with your own tools, with guidance on what to create and capture.

Local lab Suggested time: 2–3 hoursYour own authorised environment

What you could create

A container runs with unnecessary privileges and unrestricted network access. The service must keep working with a smaller runtime attack surface.

Example evidence format

Project evidence map (example)

Hardened manifest and permission rationaleScope and inputs

Runtime control test matrixDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Hardened manifest and permission rationale	Show the inputs, scope and decisions behind this record. Required application behaviour survives the restrictions.
Runtime control test matrix	Include the evidence supporting your conclusion. The negative tests demonstrate enforcement, not merely accepted configuration.

What you'll need

Local lab

Use a disposable cluster with support for the controls you intend to test. Define one permitted dependency and one unrelated test endpoint.

Project record

Keep the working files for hardened manifest and permission rationale 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
Record the workload’s actual privilege, filesystem and network requirements.
2
Develop your approach
Apply suitable security context and network restrictions.
3
Verify and explain
Test the normal operation, prohibited connection and attempted forbidden filesystem write.

Evidence worth keeping

Keep clear, organised evidence of your design and any testing you carry out.

1
Hardened manifest and permission rationale
Show the inputs, scope and decisions behind this record. Required application behaviour survives the restrictions.
2
Runtime control test matrix
Include the evidence supporting your conclusion. The negative tests demonstrate enforcement, not merely accepted configuration.

Label design proposals and observed results clearly.

Explain your work

Use these prompts to reflect on your decisions and what you learned.

Which part of your hardened manifest and permission rationale needed the most judgement?
What observation or assumption changed your approach?
What would you improve, and what have you not verified?

Describe this as a personal project in your portfolio.

Useful resources

Use these resources to deepen your understanding and check key details.

Official certification objectives

Review the current provider requirements and relevant subject areas.

Explore external learning resources

Find relevant providers and check features, access requirements and costs.

A useful starting point

Use a disposable cluster with support for the controls you intend to test. Define one permitted dependency and one unrelated test endpoint.

What a good result looks like

Required application behaviour survives the restrictions.
The negative tests demonstrate enforcement, not merely accepted configuration.
Unsupported controls are called out rather than reported as successful.

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.