Home labs & practical projects

Protect a dataset through its cloud lifecycle

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

Design project Suggested time: 2–3 hoursNo hardware required for the design

What you could create

A company will collect, analyse, archive and eventually delete sensitive research data in the cloud. Different teams own each stage.

Example evidence format

Project evidence map (example)

Data lifecycle control mapScope and inputs

Risk decisions and assurance checklistDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Data lifecycle control map	Show the inputs, scope and decisions behind this record. Each lifecycle stage has a control owner and evidence requirement.
Risk decisions and assurance checklist	Include the evidence supporting your conclusion. Key loss and unauthorised key use have distinct treatments.

What you'll need

Document, spreadsheet or diagram tool

Define a fictional dataset, retention requirement, user groups and recovery objective. Draw the proposed storage and processing flow.

Project record

Keep the working files for data lifecycle control map 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
Classify data and map trust boundaries across collection, processing and archive.
2
Develop your approach
Assign access, encryption, key ownership and monitoring controls at each stage.
3
Verify and explain
Reconcile retention, backup recovery and deletion requirements, recording any conflict.

Evidence worth keeping

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

1
Data lifecycle control map
Show the inputs, scope and decisions behind this record. Each lifecycle stage has a control owner and evidence requirement.
2
Risk decisions and assurance checklist
Include the evidence supporting your conclusion. Key loss and unauthorised key use have distinct treatments.

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 data lifecycle control map 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.

Official (ISC)² CCSP Practice Tests (Sybex)

Check relevance, platform versions and current access terms.

Explore external learning resources

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

A useful starting point

Define a fictional dataset, retention requirement, user groups and recovery objective. Draw the proposed storage and processing flow.

What a good result looks like

Each lifecycle stage has a control owner and evidence requirement.
Key loss and unauthorised key use have distinct treatments.
Deletion claims explain the treatment of backups and retained copies.

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.