# SA-21 Developer Screening

NIST SP 800-53 control. Family: SA System and Services Acquisition. Function: preventative. Baselines: high. Mapping licence: CC BY-SA 4.0.

Statement: Require that the developer of [Assignment: organization-defined system, system component, or system service]: a. Has appropriate access authorizations as determined by assigned [Assignment: organization-defined official government duties]; and b. Satisfies the following additional personnel screening criteria: [Assignment: organization-defined additional personnel screening criteria].
Guidance: Developer screening is directed at external developers. Internal developer screening is addressed by PS-03. Because the system, system component, or system service may be used in critical activities essential to the national or economic security interests of the United States, organizations have a strong interest in ensuring that developers are trustworthy. The degree of trust required of developers may need to be consistent with that of the individuals who access the systems, system components, or system services once deployed. Authorization and personnel screening criteria include clearances, background checks, citizenship, and nationality. Developer trustworthiness may also include a review and analysis of company ownership and relationships that the company has with entities that may potentially affect the quality and reliability of the systems, components, or services being developed. Satisfying the required access authorizations and personnel screening criteria includes providing a list of all individuals who are authorized to perform development activities on the selected system, system component, or system service so that organizations can validate that the developer has satisfied the authorization and screening requirements.

## Enhancements (none current)
Withdrawn by NIST: SA-21(01) (now in SA-21).

## Clauses by framework (35 frameworks)
- iso_27001_2022: A.6.1
- iso_27002_2022: 8.30
- cobit_2019: BAI03
- nis2: Art. 21(2)(d)
- apra_cps_234: Para 29-33
- mas_trm: 6, 16
- pra_op_resilience: SS2/21-5.1
- anssi: Hygiene.42, SecNumCloud.15.1, SecNumCloud.16.1
- osfi_b13: B-13.4.1
- finma_circular: IV.F(100), V(101), V(103), VII.A(113)
- dora: Art.28(5)
- bio2: 8.30
- rbi_csf: Annex1.6
- fisc: FISC.O6, FISC.O10
- hkma_tme1: TME1.3.2, TME1.12.1
- cbb_tm: TM-7, TM-15
- cbuae: CR-6, CR-12
- qatar_nia: SD
- sama_csf: 3.2, 4.1, 4.2
- uae_ia: T10
- bog_cisd: CISD-SDLC
- bom_ctrm: 3.9, 3.11
- cbe_csf: CTO-4, OVM-1
- cbn_csf: Part2.4
- sa_js2: JS2-8.7
- bot_cyber: Ch2.5, Ch5.1
- eba_ict: 3.6.2
- iosco_cyber: PROT-7
- sebi_cscrf: GV.SC, PR.AS
- pci_pts: H
- cbest: CBEST.8
- tiber_eu: TIBER.PROV
- fca_sysc_13: SYSC 13.9.2
- lloyds_ms: MS8.8
- solvency_ii: Art.49(1)
OSA's mapping for iso_27001_2022 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/SA-21
- Clauses only: /api/v1/controls/SA-21?fields=mappings
- Page for people: /controls/sa-21/
- 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.