CA-3 Information exchange
What the standard requires
a. Approve and manage the exchange of information between the system and other systems using [interconnection security agreements | information exchange security agreements | memoranda of understanding or agreement | service level agreements | user agreements | non-disclosure agreements | [type of agreement] ]; b. Document, as part of each exchange agreement, the interface characteristics, security and privacy requirements, controls, and responsibilities for each system, and the impact level of the information communicated; and c. Review and update the agreements [frequency].
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 Assessment & Authorization 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.