Assessment Objective
Determine if:
- SA-11(02)(a)
- SA-11(02)(a)[01] the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that uses [Assignment: information];
- SA-11(02)(a)[02] the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that uses [Assignment: information];
- SA-11(02)(a)[03] the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that uses [Assignment: information];
- SA-11(02)(a)[04] the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that uses [Assignment: information];
- SA-11(02)(b)
- SA-11(02)(b)[01] the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that employs [Assignment: tools and methods];
- SA-11(02)(b)[02] the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that employs [Assignment: tools and methods];
- SA-11(02)(b)[03] the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that employs [Assignment: tools and methods];
- SA-11(02)(b)[04] the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that employs [Assignment: tools and methods];
- SA-11(02)(c)
- SA-11(02)(c)[01] the developer of the system, system component, or system service is required to perform threat modeling at [Assignment: breadth and depth] during development of the system, component, or service;
- SA-11(02)(c)[02] the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that conducts modeling and analyses at [Assignment: breadth and depth];
- SA-11(02)(d)
- SA-11(02)(d)[01] the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that produces evidence that meets [Assignment: acceptance criteria];
- SA-11(02)(d)[02] the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [Assignment: acceptance criteria];
- SA-11(02)(d)[03] the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that produces evidence that meets [Assignment: acceptance criteria];
- SA-11(02)(d)[04] the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets [Assignment: acceptance criteria].
Assessment Methods
Examine
- System and services acquisition policy
- procedures addressing system developer security testing
- solicitation documentation
- acquisition documentation
- service level agreements
- acquisition contracts for the system, system component, or system service
- system developer security test plans
- records of developer security testing results for the system, system component, or system service
- vulnerability scanning results
- system risk assessment reports
- threat and vulnerability analysis reports
- system security plan
- supply chain risk management plan
- other relevant documents or records
Interview
- Organizational personnel with system and service acquisition responsibilities
- organizational personnel with information security responsibilities
- organizational personnel with developer security testing responsibilities
- system developers
- organizational personnel with supply chain risk management responsibilities
Test
- Organizational processes for monitoring developer security testing and evaluation
- mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation
Ticket collegati
| Tipo di collegamento | Ticket |
|---|---|
| blocks | SA-11(02) Threat Modeling and Vulnerability Analyses |
- NIST -
EN: Publications of the National Institute of Standards and Technology (NIST), U.S. Department of Commerce, https://www.nist.gov/, from their electronic versions (OSCAL; SP 800-63-4 from its HTML version, https://pages.nist.gov/800-63-4/). Works of NIST employees are not subject to copyright protection in the United States (17 U.S.C. § 105); the OSCAL content is dedicated to the public domain worldwide (CC0 1.0); outside the United States NIST grants the right to reprint its technical series publications in all formats (NIST copyright statement). Republished courtesy of the National Institute of Standards and Technology; each document names its citation. Divided into sections and converted into the GRCA format, the wording unchanged. Only the versions published by NIST are authoritative.
DE: Veröffentlichungen des National Institute of Standards and Technology (NIST), U.S. Department of Commerce, https://www.nist.gov/, aus ihren elektronischen Fassungen (OSCAL; SP 800-63-4 aus ihrer HTML-Fassung, https://pages.nist.gov/800-63-4/). Werke von NIST-Beschäftigten sind in den USA urheberrechtlich nicht geschützt (17 U.S.C. § 105); die OSCAL-Inhalte sind weltweit gemeinfrei gestellt (CC0 1.0); außerhalb der USA räumt das NIST das Recht ein, seine Technical-Series-Publikationen in allen Formaten neu zu veröffentlichen (Copyright-Hinweis des NIST). „Republished courtesy of the National Institute of Standards and Technology“; jedes Dokument nennt seine Zitierangabe. In Abschnitte aufgeteilt und in das GRCA-Format umgewandelt, der Wortlaut unverändert. Maßgeblich sind allein die vom NIST veröffentlichten Fassungen.