Home labs & practical projects
Explain identity, security and compliance in one workflow
A project to do with your own tools, with guidance on what to create and capture.
What you could create
A new employee needs access to a confidential document and later leaves the company. A manager wants to understand which controls do what.
| Evidence | What to capture |
|---|---|
| Annotated employee information flow | Show the inputs, scope and decisions behind this record. Signing in successfully is not confused with permission to read every document. |
| Plain-English control glossary with examples | Include the evidence supporting your conclusion. Security detection and compliance retention have separate purposes. |
What you'll need
Document, spreadsheet or diagram tool
Draw a fictional user, identity directory, document store and security monitoring service. Define the document’s sensitivity and access owner.
Project record
Keep the working files for annotated employee information flow 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
Separate authentication, authorisation and information protection.
- 2
Develop your approach
Explain how a suspicious sign-in and an improper document share would be investigated.
- 3
Verify and explain
Describe access removal and retention decisions when employment ends.
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
Draw a fictional user, identity directory, document store and security monitoring service. Define the document’s sensitivity and access owner.
What a good result looks like
- Signing in successfully is not confused with permission to read every document.
- Security detection and compliance retention have separate purposes.
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.