Section 11.50 (Signature Manifestations): (a) signed electronic records must contain information associated with the signing that clearly indicates all of the following: (1) the printed name of the signer; (2) the date and time when the signature was executed; (3) the meaning (such as review + approval + responsibility + or authorship) associated with the signature. (b) the items identified in §11.50(a) must be subject to the same controls as for electronic records + must be included as part of any human readable form of the electronic record (such as electronic display or printout). Section 11.70 (Signature / Record Linking): electronic signatures + handwritten signatures executed to electronic records must be linked to their respective electronic records to ensure that the signatures cannot be excised + copied + or otherwise transferred to falsify an electronic record by ordinary means. The §11.70 linking requirement is foundational - the signature must be cryptographically or otherwise bound to the specific record + cannot be reused or moved.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.