CM-20 Change Management
Data Conversion / Migration
Migrated data is complete and accurate.
- Domain
- Change Management
- Control type
- Preventive/Detective
- Automated / manual
- Manual
- Frequency
- Per project
- Framework reference
- COBIT BAI07.05
What good looks like
Migration planned, reconciled and validated for completeness/accuracy with sign-off.
Risk if it fails
Data loss/corruption during migration.
How Tess tests it
3 tests — each concludes only on cited evidence.
Migration plan with reconciliation approach
Design- Procedure
- Inspect the plan.
- Expected
- Defined.
- Sample
- 1 (design inspection)
- Evidence
- Migration plan, reconciliation results, sign-off.
Migration reconciled (counts/values)
Operating- Procedure
- Sample a migration.
- Expected
- Complete and accurate.
- Sample
- Judgmental, by population (e.g. 10–25)
- Evidence
- Migration plan, reconciliation results, sign-off.
Migration signed off
Operating- Procedure
- Inspect sign-off.
- Expected
- Approved.
- Sample
- Judgmental, by population (e.g. 10–25)
- Evidence
- Migration plan, reconciliation results, sign-off.
Evidence Tess looks for
Migration plan, reconciliation results, sign-off.
More in Change Management
Want Tess to test CM-20 against your evidence?
Book a demo