Home labs & practical projects

Plan and conduct a mock management-system audit

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

An audit team needs to evaluate a fictional organisation’s access-review process against its documented management-system commitments.

Example evidence format

Improvement roadmap (example)

Mock audit plan and working papersScope and inputs

Finding statement and closure criteriaDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Mock audit plan and working papers	Show the inputs, scope and decisions behind this record. The finding cites a specific criterion and objective evidence.
Finding statement and closure criteria	Include the evidence supporting your conclusion. The auditor does not prescribe an unsupported technical solution as the only remedy.

What you'll need

Document, spreadsheet or diagram tool

Write a short policy, three review records and a management objective. Use the organisation’s commitments and authorised standard access as audit criteria.

Project record

Keep the working files for mock audit plan and working papers 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
Prepare an audit plan and interview questions tied to the criteria.
2
Develop your approach
Evaluate the sample records and corroborate an apparent exception.
3
Verify and explain
Write a neutral finding and explain the evidence needed to close it.

Evidence worth keeping

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

1
Mock audit plan and working papers
Show the inputs, scope and decisions behind this record. The finding cites a specific criterion and objective evidence.
2
Finding statement and closure criteria
Include the evidence supporting your conclusion. The auditor does not prescribe an unsupported technical solution as the only remedy.

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 mock audit plan and working papers 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

Write a short policy, three review records and a management objective. Use the organisation’s commitments and authorised standard access as audit criteria.

What a good result looks like

The finding cites a specific criterion and objective evidence.
The auditor does not prescribe an unsupported technical solution as the only remedy.

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.