pl-8-security-and-privacy-architectures

name	PL-8_security-and-privacy-architectures
description	Develop security and privacy architectures for the system that: Describe the requirements and approach to be taken for protecting the confidentiality,
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","pl-8","pl"]
tech_stack	["any"]
cwe_ids	[]
chains_with	["CM-2","CM-6","PL-2","PL-7","PL-9","PM-5","PM-7","RA-9","SA-3","SA-5"]
prerequisites	[]
severity_boost	{"CM-2":"Chain with CM-2 for comprehensive security coverage","CM-6":"Chain with CM-6 for comprehensive security coverage","PL-2":"Chain with PL-2 for comprehensive security coverage"}

PL-8 Security and Privacy Architectures

High-Level Description

Family: Planning (PL) Framework: NIST SP 800-53 Rev 5

The security and privacy architectures at the system level are consistent with the organization-wide security and privacy architectures described in PM-7 , which are integral to and developed as part of the enterprise architecture. The architectures include an architectural description, the allocation of security and privacy functionality (including controls), security- and privacy-related information for external interfaces, information being exchanged across the interfaces, and the protection mechanisms associated with each interface. The architectures can also include other information, such as user roles and the access privileges assigned to each role; security and privacy requirements; types of information processed, stored, and transmitted by the system; supply chain risk management requirements; restoration priorities of information and system services; and other protection needs.

SP 800-160-1 provides guidance on the use of security architectures as part of the system development life cycle process. OMB M-19-03 requires the use of the systems security engineering concepts described in SP 800-160-1 for high value assets. Security and privacy architectures are reviewed and updated throughout the system development life cycle, from analysis of alternatives through review of the proposed architecture in the RFP responses to the design reviews before and during implementation (e.g., during preliminary design reviews and critical design reviews).

In today’s modern computing architectures, it is becoming less common for organizations to control all information resources. There may be key dependencies on external information services and service providers. Describing such dependencies in the security and privacy architectures is necessary for developing a comprehensive mission and business protection strategy. Establishing, developing, documenting, and maintaining under configuration control a baseline configuration for organizational systems is critical to implementing and maintaining effective architectures. The development of the architectures is coordinated with the senior agency information security officer and the senior agency official for privacy to ensure that the controls needed to support security and privacy requirements are identified and effectively implemented. In many circumstances, there may be no distinction between the security and privacy architecture for a system. In other circumstances, security objectives may be adequately satisfied, but privacy objectives may only be partially satisfied by the security requirements. In these cases, consideration of the privacy requirements needed to achieve satisfaction will result in a distinct privacy architecture. The documentation, however, may simply reflect the combined architectures.