[RDI 9] Focus on outcome, not process, of memory safety

#### 5.2.5.1 Requirement

1. **REQ-SSD-05 (MI-IMSL)-1** The product shall be implemented in a memory-safe language, and

2. **REQ-SSD-05 (MI-IMSL)-2** any use of unsafe memory features shall be documented to explain how that feature does not present a cybersecurity risk.

1. **REQ-SSD-05 (MI-IMSL)-1** The product shall employ implementation practices, tooling, or language features that mitigate memory corruption vulnerabilities, and

2. **REQ-SSD-05 (MI-IMSL)-2** any use of unsafe memory features in the product's own code or in dependencies shall be documented, justified as necessary, and accompanied by the specific mitigations applied to reduce residual risk.

#### 5.2.5.2 Applicability

PASS if **all** of the following are fulfilled:

* Source code is in a memory-safe language, and

* the documentation of all uses of unsafe memory features convincingly demonstrates that each one does not present a cybersecurity risk.

* The product employs implementation practices, tooling, or language features that mitigate memory corruption vulnerabilities, and

* documentation of all uses of unsafe memory features in the product’s own code or in dependencies identifies each instance, justifies its necessity, and demonstrates that the applied mitigations reduce the residual cybersecurity risk to an acceptable level.

Otherwise FAIL