# SA-11 Developer Testing and Evaluation

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

Statement: Require the developer of the system, system component, or system service, at all post-design stages of the system development life cycle, to: a. Develop and implement a plan for ongoing security and privacy control assessments; b. Perform [Selection (one or more): unit; integration; system; regression] testing/evaluation [Assignment: organization-defined frequency] at [Assignment: organization-defined depth and coverage]; c. Produce evidence of the execution of the assessment plan and the results of the testing and evaluation; d. Implement a verifiable flaw remediation process; and e. Correct flaws identified during testing and evaluation.
Guidance: Developmental testing and evaluation confirms that the required controls are implemented correctly, operating as intended, enforcing the desired security and privacy policies, and meeting established security and privacy requirements. Security properties of systems and the privacy of individuals may be affected by the interconnection of system components or changes to those components. The interconnections or changes—including upgrading or replacing applications, operating systems, and firmware—may adversely affect previously implemented controls. Ongoing assessment during development allows for additional types of testing and evaluation that developers can conduct to reduce or eliminate potential flaws. Testing custom software applications may require approaches such as manual code review, security architecture review, and penetration testing, as well as and static analysis, dynamic analysis, binary analysis, or a hybrid of the three analysis approaches. Developers can use the analysis approaches, along with security instrumentation and fuzzing, in a variety of tools and in source code reviews. The security and privacy assessment plans include the specific activities that developers plan to carry out, including the types of analyses, testing, evaluation, and reviews of software and firmware components; the degree of rigor to be applied; the frequency of the ongoing testing and evaluation; and the types of artifacts produced during those processes. The depth of testing and evaluation refers to the rigor and level of detail associated with the assessment process. The coverage of testing and evaluation refers to the scope (i.e., number and type) of the artifacts included in the assessment process. Contracts specify the acceptance criteria for security and privacy assessment plans, flaw remediation processes, and the evidence that the plans and processes have been diligently applied. Methods for reviewing and protecting assessment plans, evidence, and documentation are commensurate with the security category or classification level of the system. Contracts may specify protection requirements for documentation.

## Enhancements (9)
- SA-11(01) Static Code Analysis
- SA-11(02) Threat Modeling and Vulnerability Analyses
- SA-11(03) Independent Verification of Assessment Plans and Evidence
- SA-11(04) Manual Code Reviews
- SA-11(05) Penetration Testing
- SA-11(06) Attack Surface Reviews
- SA-11(07) Verify Scope of Testing and Evaluation
- SA-11(08) Dynamic Code Analysis
- SA-11(09) Interactive Application Security Testing
Each enhancement's statement: /api/v1/controls/SA-11?fields=enhancements

## Patterns that use it (16)
- Critical (7): SP-012 Secure Software Development Lifecycle; SP-028 Secure DevOps Pipeline Pattern; SP-045 AI Governance and Responsible AI; SP-049 AI in Security Operations (draft); SP-051 Tokenised Asset Security Architecture (draft); SP-053 Zero-Knowledge Proof Architecture (draft); SP-054 CBDC and Digital Currency Infrastructure (draft)
- Important (8): SP-011 Cloud Computing Pattern; SP-027 Secure LLM Usage; SP-030 API Security; SP-035 Offensive Security Testing; SP-047 Secure Agentic AI Frameworks; SP-048 Offensive AI and Deepfake Defence (draft); SP-050 Mobile Security Architecture (draft); SP-052 Decentralised Identity & Verifiable Credentials (draft)
- Standard (1): SP-038 Vulnerability Management and Patching

## Clauses by framework (67 frameworks)
- iso_27001_2022: A.8.25, A.8.28, A.8.29, A.8.30, A.8.31, A.8.33. OSA's own, not in NIST's crosswalk: A.8.25, A.8.28, A.8.31, A.8.33
- iso_27002_2022: 8.25, 8.26, 8.28, 8.29, 8.30, 8.31, 8.33
- cobit_2019: APO11, BAI03, BAI07
- pci_dss_v4: 6.2, 6.2.3, 6.4
- nist_csf_2: ID.IM-01, ID.IM-02, ID.IM-03, ID.RA-09, PR.PS-06
- cis_controls_v8: CIS 16, CIS 16.2, CIS 16.3, CIS 16.8, CIS 16.12, CIS 16.13
- soc2_tsc: CC4.1-POF1
- iso_42001_2023: A.6.2.4
- nis2: Art. 21(2)(e)
- mas_trm: 6
- bsi_grundschutz: APP.3.1, OPS.1.1.6
- anssi: Hygiene.31, Hygiene.33, SecNumCloud.15.5
- osfi_b13: B-13.3.2, B-13.3.5
- finma_circular: IV.A(36), IV.A(37), IV.D(75), IV.D(76)
- gdpr: Art.25(1), Art.32(1)(d)
- dora: Art.9(4)(e), Art.25(1), Art.25(2)
- bio2: 8.25, 8.26, 8.28, 8.29, 8.30, 8.31, 8.33
- rbi_csf: Annex1.6, Annex1.18
- fisc: FISC.O10, FISC.T6
- lgpd_bcb: BCB.Art.10
- hkma_tme1: TME1.3.2, TME1.3.3
- mlps_2: 8.1.9.4, 8.1.9.5
- dnb_good_practice: DNB.10.3, DNB.10.4, DNB.22.1
- cra: CRA.I.1, CRA.I.2a, CRA.II.2, CRA.II.3
- swift_cscf: SWIFT.2.10
- cbb_tm: TM-7
- cbuae: CR-6
- nca_ecc: 1-6, 2-3, 2-10, 2-11, 2-14
- qatar_nia: SD
- sama_csf: 3.2
- uae_ia: T7, T10
- bog_cisd: CISD-IX, CISD-SDLC
- bom_ctrm: 3.11
- cbe_csf: CTO-4
- cbn_csf: Part5.2
- sa_js2: JS2-7.7, JS2-SA
- bcbs_239: Principle 3, Principle 7
- bot_cyber: Ch2.5
- cpmi_pfmi: CG.TE, PFMI.P17
- eba_ict: 3.4.6, 3.6.2
- ecb_croe: CROE.2.3.4, CROE.2.6.1
- ffiec_is: II.C.15(b), II.C.17, IV.A, IV.A.2
- iosco_cyber: PROT-6, SA-3, TEST-1, TEST-3
- nydfs_500: 500.5, 500.8
- sebi_cscrf: PR.AS, PR.IP
- tsa_psd: SD-2 Sec G
- ieee_1686: 5.10
- pci_pts: F
- fips_140: FIPS 140-3 §7.5, FIPS 140-3 §7.11, FIPS 140-3 §7.12
- common_criteria: CC Part 2 — FPT, CC Part 3 — SAR, CEM
- isae_3402: Clause 4
- fca_sysc_13: SYSC 13.7.1, SYSC 13.7.4
- fda_21_cfr_11: §11.10(a), §11.10(f)
- fda_cyber: 524B-4, CRA-1, PU-1, ST-1, ST-2, ST-3, ST-4, TM-1
- hitrust_csf: 09.b, 10.b, 10.d
- iso_27799: 14.2, 14.3
- lloyds_ms: BP2.1, MS8.4, MS8.11
- naic_ds: 4-config
- pra_ss1_23: P3.3, P4.2, P4.3
- solvency_ii: EIOPA-ICT-4.11
- owasp_masvs_v2: MASVS-CODE-3, MASVS-CODE-4, MASVS-PLATFORM-2, MASVS-RESILIENCE-1
- csa_ccm_v4: AIS-02, AIS-03, AIS-04, AIS-05, AIS-07, CCC-02, TVM-05
- csa_aicm: AIS-02, AIS-03, AIS-04, AIS-05, AIS-07, AIS-09, AIS-10, AIS-13, AIS-15, CCC-02, MDS-03, MDS-08, TVM-05, TVM-12
- ccss_v9: 1.02.7
- basel_sco60: SCO60.14, SCO60.21, SCO60.51, SCO60.52
- bssc: GSP-08, GSP-15, NOS-02, TIS-02, TIS-04
- dpdpa: Rules.13(3)
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/SA-11
- Clauses only: /api/v1/controls/SA-11?fields=mappings
- Page for people: /controls/sa-11/
- 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.