# CA-09 Internal System Connections

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

Statement: a. Authorize internal connections of [Assignment: organization-defined system components or classes of components] to the system; b. Document, for each internal connection, the interface characteristics, security and privacy requirements, and the nature of the information communicated; c. Terminate internal system connections after [Assignment: organization-defined conditions]; and d. Review [Assignment: organization-defined frequency] the continued need for each internal connection.
Guidance: Internal system connections are connections between organizational systems and separate constituent system components (i.e., connections between components that are part of the same system) including components used for system development. Intra-system connections include connections with mobile devices, notebook and desktop computers, tablets, printers, copiers, facsimile machines, scanners, sensors, and servers. Instead of authorizing each internal system connection individually, organizations can authorize internal connections for a class of system components with common characteristics and/or configurations, including printers, scanners, and copiers with a specified processing, transmission, and storage capability or smart phones and tablets with a specific baseline configuration. The continued need for an internal system connection is reviewed from the perspective of whether it provides support for organizational missions or business functions.

## Enhancements (1)
- CA-09(01) Compliance Checks
Each enhancement's statement: /api/v1/controls/CA-09?fields=enhancements

## Clauses by framework (37 frameworks)
- iso_27001_2022: A.8.20. OSA's own, not in NIST's crosswalk: A.8.20
- iso_27002_2022: 8.20
- cobit_2019: MEA04
- pci_dss_v4: 1.2, 1.3, 11.3
- nist_csf_2: ID.AM-03
- soc2_tsc: CC6.1, CC7.1
- finos_ccc: CCC-C05
- bsi_grundschutz: ORP.5
- anssi: Hygiene.3, Hygiene.9, Hygiene.26
- osfi_b13: B-13.4.2
- finma_circular: IV.B.d(59), IV.B.d(60), IV.C(62), IV.D(75), IV.D(76), IV.D(77), V(104)
- gdpr: Art.32(1)(d)
- dora: Art.6(4)
- bio2: 8.20
- rbi_csf: Annex1.4
- fisc: FISC.T3, FISC.T9, FISC.T13
- lgpd_bcb: BCB.Art.11
- cbuae: CR-10
- nca_ecc: 2-5, 4-2
- qatar_nia: CS
- sama_csf: 4.3
- uae_ia: T8
- bog_cisd: CISD-XI
- bom_ctrm: 1.5, 5.4
- cbe_csf: CTO-11, OVM-3
- cbn_csf: Part2.3
- sa_js2: JS2-7.7
- bot_cyber: Ch5.2
- eba_ict: 3.3.6
- ffiec_is: II.C.6, II.C.20
- iosco_cyber: ID-2, PFMI-20
- sebi_cscrf: CERTIF
- cmmc_2: CA
- iso_27799: 13.1
- csa_ccm_v4: AA-04, DSP-05, IVS-08
- csa_aicm: A&A-04, DSP-05, I&S-08
- ccss_v9: 1.01.5, 2.02.2
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-09
- Clauses only: /api/v1/controls/CA-09?fields=mappings
- Page for people: /controls/ca-09/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.