Developer Security and Privacy Architecture and Design
System and Services Acquisition
NIST Control Text
Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that:
- a.Is consistent with the organization’s security and privacy architecture that is an integral part the organization’s enterprise architecture;
- b.Accurately and completely describes the required security and privacy functionality, and the allocation of controls among physical and logical components; and
- c.Expresses how individual security and privacy functions, mechanisms, and services work together to provide required security and privacy capabilities and a unified approach to protection.
NIST Discussion
Developer security and privacy architecture and design are directed at external developers, although they could also be applied to internal (in-house) development. In contrast, PL-8 is directed at internal developers to ensure that organizations develop a security and privacy architecture that is integrated with the enterprise architecture. The distinction between SA-17 and PL-8 is especially important when organizations outsource the development of systems, system components, or system services and when there is a requirement to demonstrate consistency with the enterprise architecture and security and privacy architecture of the organization. [ISO 15408-2], [ISO 15408-3], and [SP 800-160-1] provide information on security architecture and design, including formal policy models, security-relevant components, formal and informal correspondence, conceptually simple design, and structuring for least privilege and testing.
SL5 Supplemental Guidance
Apply SP 800-161 Rev. 1 Update 1 guidance [3]. Architecture decisions should address security and resilience considerations, including component selection strategies that enable availability through multiple supplier options.