# SA-16 Developer-provided Training

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

Statement: Require the developer of the system, system component, or system service to provide the following training on the correct use and operation of the implemented security and privacy functions, controls, and/or mechanisms: [Assignment: organization-defined training].
Guidance: Developer-provided training applies to external and internal (in-house) developers. Training personnel is essential to ensuring the effectiveness of the controls implemented within organizational systems. Types of training include web-based and computer-based training, classroom-style training, and hands-on training (including micro-training). Organizations can also request training materials from developers to conduct in-house training or offer self-training to organizational personnel. Organizations determine the type of training necessary and may require different types of training for different security and privacy functions, controls, and mechanisms.

## Patterns that use it (1)
- Important (1): SP-012 Secure Software Development Lifecycle

## Clauses by framework (22 frameworks)
- iso_27001_2022: A.8.28. OSA's own, not in NIST's crosswalk: A.8.28
- iso_27002_2022: 8.28
- pci_dss_v4: 6.2.1
- cis_controls_v8: CIS 16.9
- mas_trm: 6
- bio2: 8.28
- rbi_csf: Annex1.6
- fisc: FISC.O10, FISC.T6
- hkma_tme1: TME1.3.2
- cbb_tm: TM-7
- cbuae: CR-6
- qatar_nia: SD
- sama_csf: 3.2
- uae_ia: T10
- bog_cisd: CISD-SDLC
- bom_ctrm: 3.11
- cbe_csf: CTO-4
- bot_cyber: Ch2.5
- eba_ict: 3.6.2
- pci_pts: H
- hitrust_csf: 10.d
- pra_ss1_23: P3.3
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-16
- Clauses only: /api/v1/controls/SA-16?fields=mappings
- Page for people: /controls/sa-16/
- 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.