CHG-06 · Testing, release and acceptance
Catalogue · Build & Change
Changes are tested against requirements, including security and resilience, and formally accepted before release.
Typical activities
- Maintain a testing programme covering functional, performance, security and recovery testing
- Use independent testers or reviewers for critical systems
- Record acceptance by the business owner before go-live
- Track and remediate findings from tests
Evidence an assessor would expect
- Test plans and results
- Acceptance sign-offs
- Findings remediation log
Capability scale
- 0 · Absent
- The practice is not performed, or happens so rarely that it produces no recognisable outcome.
- 1 · Initial
- The practice is performed informally and its results depend on the people involved.
- 2 · Repeatable
- The practice is planned, assigned and tracked, with basic records kept.
- 3 · Defined
- The practice follows a documented, organisation-wide approach with clear roles and measurable outputs.
- 4 · Measured
- The practice is managed with quantitative targets and its performance is monitored and reported.
- 5 · Optimising
- The practice is continuously improved using performance data, external comparison and automation.
Regulatory requirements
Cross-references
- COBIT® 2019 BAI07
- ISO/IEC 27001:2022 A.8.29
Identifiers only, for orientation. Consult the original publications for their content.