Source Document
MAS TRM Guidelines
MAS.TRM.2021.Sec5.7.5.p18.OBL1
5 IT Project Management and Security-by-Design > 5.7 System Testing and Acceptance > 5.7.5
Obligation Summary
Issues identified from testing, including system defects or software bugs, should be properly tracked and addressed.
Issues identified from testing, including system defects or software bugs, should be properly tracked and addressed.
MAS TRM Guidelines, Section 5.7.5, p. 18 (2021) · Technology Risk Management Guidelines · p. 18
5.7.4 The FI should perform regression testing for changes (e.g. enhancement, rectification, etc.) to an existing IT system to validate that it continues to function properly after the changes have been implemented.
5.7.5 Issues identified from testing, including system defects or software bugs, should be properly tracked and addressed. Major issues that could have an adverse impact on the FI’s operations or delivery of service to customers should be reported to the project steering committee and addressed prior to deployment to the production environment.
5.7.6 The FI should ensure the results of all testing that was conducted are documented in the test report, and signed off by the relevant stakeholders.
What This Requires.
ProfytAI Regulatory Intelligence
Type: requirementIssues identified during testing, including system defects and software bugs, should be properly tracked and addressed.
Relationship
First of two expectations from paragraph 5.7.5; the companion obligation (OBL2) adds escalation and pre-deployment resolution for major issues.
Why This Exists
Untracked defects resurface in production; disciplined tracking ensures every known issue is either fixed or knowingly dispositioned.
Implementation Considerations
Typically involves a defect management tool and workflow with severity classification, ownership and closure evidence.
Interpretation Note · 'Including' makes defects and bugs examples of test issues rather than the whole scope, and both tracking and addressing are expected. As guidance, 'should' is a MAS expectation.
This explanation is generated regulatory intelligence, traceable to the citation above.
The byte-exact verbatim text remains the authority you cite.
The captured source page, with this duty highlighted and stamped with its obligation ID, section, and page.
