# CA-03 Information Exchange

NIST SP 800-53 control. Family: CA Security Assessment and Authorization. Function: preventative. Baselines: low, moderate, high. Mapping licence: CC BY-SA 4.0.

Statement: a. Approve and manage the exchange of information between the system and other systems using [Selection (one or more): interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service level agreements; user agreements; nondisclosure agreements; [Assignment: organization-defined 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 [Assignment: organization-defined frequency].
Guidance: System information exchange requirements apply to information exchanges between two or more systems. System information exchanges include connections via leased lines or virtual private networks, connections to internet service providers, database sharing or exchanges of database transaction information, connections and exchanges with cloud services, exchanges via web-based services, or exchanges of files via file transfer protocols, network protocols (e.g., IPv4, IPv6), email, or other organization-to-organization communications. Organizations consider the risk related to new or increased threats that may be introduced when systems exchange information with other systems that may have different security and privacy requirements and controls. This includes systems within the same organization and systems that are external to the organization. A joint authorization of the systems exchanging information, as described in CA-06(01) or CA-06(02), may help to communicate and reduce risk. Authorizing officials determine the risk associated with system information exchange and the controls needed for appropriate risk mitigation. The types of agreements selected are based on factors such as the impact level of the information being exchanged, the relationship between the organizations exchanging information (e.g., government to government, government to business, business to business, government or business to service provider, government or business to individual), or the level of access to the organizational system by users of the other system. If systems that exchange information have the same authorizing official, organizations need not develop agreements. Instead, the interface characteristics between the systems (e.g., how the information is being exchanged. how the information is protected) are described in the respective security and privacy plans. If the systems that exchange information have different authorizing officials within the same organization, the organizations can develop agreements or provide the same information that would be provided in the appropriate agreement type from CA-03a in the respective security and privacy plans for the systems. Organizations may incorporate agreement information into formal contracts, especially for information exchanges established between federal agencies and nonfederal organizations (including service providers, contractors, system developers, and system integrators). Risk considerations include systems that share the same networks.

## Enhancements (2)
- CA-03(06) Transfer Authorizations. Baselines: high
- CA-03(07) Transitive Information Exchanges
Withdrawn by NIST: CA-03(01) (now in SC-07(25)); CA-03(02) (now in SC-07(26)); CA-03(03) (now in SC-07(27)); CA-03(04) (now in SC-07(28)); CA-03(05) (now in SC-07(05)).
Each enhancement's statement: /api/v1/controls/CA-03?fields=enhancements

## Patterns that use it (5)
- Important (4): SP-011 Cloud Computing Pattern; SP-016 DMZ Module; SP-019 Secure Ad-Hoc File Exchange Pattern; SP-021 Realtime Collaboration Pattern
- Standard (1): SP-018 Information Security Management System

## Clauses by framework (42 frameworks)
- iso_27001_2022: A.5.14, A.8.21
- cobit_2019: APO09
- nist_csf_2: ID.AM-03, PR.DS-01, PR.DS-02, PR.DS-10
- iso_42001_2023: A.10.2
- pra_op_resilience: SS2/21-9.1
- anssi: Hygiene.9, Hygiene.26, SecNumCloud.14.1
- osfi_b13: B-13.2.2, B-13.3.2
- finma_circular: IV.C(62), IV.F(100), V(101)
- gdpr: Art.28(3)(a), Art.32(1)(a)
- dora: Art.9(4)(a)
- rbi_csf: Annex1.4, Annex1.11
- fisc: FISC.O6, FISC.T3, FISC.T9, FISC.T13
- lgpd_bcb: BCB.Art.11
- cra: CRA.I.2i, CRA.Info.8f
- swift_cscf: SWIFT.1.1, SWIFT.1.5, SWIFT.2.8
- cbuae: CR-14
- nca_ecc: 2-5, 4-1, 4-2
- qatar_nia: CS
- uae_ia: T8
- bog_cisd: CISD-COMP, CISD-XI, CISD-XIII
- bom_ctrm: 3.9
- cbe_csf: CTO-11, GOV-3
- bcbs_239: Principle 14
- bot_cyber: Ch5.2
- cpmi_pfmi: PFMI.P22
- ecb_croe: CROE.2.2.3, CROE.2.3.5
- ffiec_is: II.C.6, II.C.9, II.C.20
- hipaa_sr: §164.308(b)(1), §164.308(b)(3), §164.314(a)(1), §164.314(a)(2)
- iosco_cyber: GOV-5, ID-2, PFMI-20, PROT-2
- nydfs_500: 500.11
- sebi_cscrf: PR.CS
- cmmc_2: CA
- common_criteria: CC Part 2 — FRU/FTA/FTP
- isae_3402: Clause 7, Clause 8
- hitrust_csf: 05.b
- iso_27799: 13.1, 13.2, H.2
- lloyds_ms: MS8.9, MS13.1
- naic_ds: 4D
- nhs_dspt: NDG-10.2, NDG-10.3
- solvency_ii: EIOPA-ICT-4.6
- mica: Art.66(1), Art.66(3)
- basel_sco60: SCO60.54, SCO60.84
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/CA-03
- Clauses only: /api/v1/controls/CA-03?fields=mappings
- Page for people: /controls/ca-03/