SI-6 Security and privacy function verification
What the standard requires
a. Verify the correct operation of [organization-defined security and privacy functions]; b. Perform the verification of the functions specified in SI-6a [[system transitional states] | upon command by user with appropriate privilege | [frequency] ]; c. Alert [personnel or roles] to failed security and privacy verification tests; and d. [shut the system down | restart the system | [alternative action(s)] ] when anomalies are discovered.
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.