SI-3(10) Malicious code protection | malicious code analysis
What the standard requires
(a) Employ the following tools and techniques to analyze the characteristics and behavior of malicious code: [tools and techniques] ; and (b) Incorporate the results from malicious code analysis into organizational incident response and flaw remediation processes.
Quoted verbatim from NIST SP 800-53 Rev 5 (OSCAL catalog), which is in the public domain.
Cross-framework mappings
No cross-framework mapping is seeded for this control. That is stated rather than filled in: a mapping nobody authored is worse than a gap you can see.
Integrations that carry evidence for this family
These connectors produce data relevant to FedRAMP Moderate’s System & Information Integrity family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.