Home labs & practical projects

Turn an operational weakness into a measurable risk

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

Design project Suggested time: 90–120 minutesNo hardware required for the design

What you could create

A critical service has missed several recovery tests. The risk register currently says only “backup risk” and offers no basis for management action.

Example evidence format

Improvement roadmap (example)

Completed risk assessmentScope and inputs

Treatment decision and indicator specificationDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Completed risk assessment	Show the inputs, scope and decisions behind this record. The risk statement explains a business consequence.
Treatment decision and indicator specification	Include the evidence supporting your conclusion. The chosen indicator can change a decision and has a measurable threshold.

What you'll need

Document, spreadsheet or diagram tool

Define the service’s business impact, recovery objective, backup history and control owner. Include uncertain evidence rather than assuming the controls work.

Project record

Keep the working files for completed risk assessment 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

No paid platform is needed for the written version. Use a document, spreadsheet or diagram tool you already have.

The organisation and records are fictional. Write down assumptions; do not substitute confidential employer information.

Suggested milestones

1
Plan and investigate
Write a cause-event-impact risk statement.
2
Develop your approach
Assess current controls and compare treatment options with residual risk.
3
Verify and explain
Define risk indicators, thresholds and an escalation owner.

Evidence worth keeping

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

1
Completed risk assessment
Show the inputs, scope and decisions behind this record. The risk statement explains a business consequence.
2
Treatment decision and indicator specification
Include the evidence supporting your conclusion. The chosen indicator can change a decision and has a measurable threshold.

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 completed risk assessment 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

Define the service’s business impact, recovery objective, backup history and control owner. Include uncertain evidence rather than assuming the controls work.

What a good result looks like

The risk statement explains a business consequence.
The chosen indicator can change a decision and has a measurable threshold.

Finish the project

Keep the decision record and note unanswered questions. A written design is not evidence that a technical control has been tested.

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.