CM-6 Configuration settings
What the standard requires
a. Establish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with operational requirements using [common secure configurations]; b. Implement the configuration settings; c. Identify, document, and approve any deviations from established configuration settings for [system components] based on [operational requirements] ; and d. Monitor and control changes to the configuration settings in accordance with organizational policies and procedures.
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 Configuration Management 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.