Home labs & practical projects

Audit a change-control sample

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 internal auditor must assess whether production changes follow the organisation’s stated approval and validation process.

Example evidence format

Improvement roadmap (example)

Audit test worksheetScope and inputs

Evidence-backed finding and management questionsDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Audit test worksheet	Show the inputs, scope and decisions behind this record. The conclusion stays within the sample and evidence limitations.
Evidence-backed finding and management questions	Include the evidence supporting your conclusion. An absent document is distinguished from proof that an action never happened.

What you'll need

Document, spreadsheet or diagram tool

Create eight fictional change tickets with approvals, testing and release timestamps. Include an emergency change and two incomplete records.

Project record

Keep the working files for audit test worksheet 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
Define the audit objective, criteria and sampling rationale.
2
Develop your approach
Test the sample for control design and operating effectiveness.
3
Verify and explain
Write a finding with condition, criteria, cause, consequence and a proportionate recommendation.

Evidence worth keeping

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

1
Audit test worksheet
Show the inputs, scope and decisions behind this record. The conclusion stays within the sample and evidence limitations.
2
Evidence-backed finding and management questions
Include the evidence supporting your conclusion. An absent document is distinguished from proof that an action never happened.

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 audit test worksheet 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

Create eight fictional change tickets with approvals, testing and release timestamps. Include an emergency change and two incomplete records.

What a good result looks like

The conclusion stays within the sample and evidence limitations.
An absent document is distinguished from proof that an action never happened.

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.