Home labs & practical projects
Review a legacy information-protection policy set
A project to do with your own tools, with guidance on what to create and capture.
What you could create
An existing information-protection programme has overlapping labels and retention rules. Staff cannot predict what happens when a document is shared or deleted.
| Evidence | What to capture |
|---|---|
| Policy overlap review | Show the inputs, scope and decisions behind this record. Sensitivity and retention are evaluated separately. |
| Information lifecycle acceptance tests | Include the evidence supporting your conclusion. The test plan records assumptions about the currently licensed features. |
What you'll need
Document, spreadsheet or diagram tool
Invent three labels, two retention rules and four sample documents. Treat the credential as a historical record and check current product documentation for implementation choices.
Project record
Keep the working files for policy overlap review 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
Map label intent, user actions and retention outcomes.
- 2
Develop your approach
Identify conflicts and propose clearer policy ownership.
- 3
Verify and explain
Write acceptance tests for internal sharing, external sharing and deletion requests.
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
Invent three labels, two retention rules and four sample documents. Treat the credential as a historical record and check current product documentation for implementation choices.
What a good result looks like
- Sensitivity and retention are evaluated separately.
- The test plan records assumptions about the currently licensed features.
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.