Secure Distributed Composition
LOW MODERATE HIGHRequirements NIST SOURCE
Implement the security design principle of secure distributed composition in [systems or system components].
Discussion (NIST Supplemental Guidance)
The principle of secure distributed composition states that the composition of distributed components that enforce the same system security policy result in a system that enforces that policy at least as well as the individual components do. Many of the design principles for secure systems deal with how components can or should interact. The need to create or enable a capability from the composition of distributed components can magnify the relevancy of these principles. In particular, the translation of security policy from a stand-alone to a distributed system or a system-of-systems can have unexpected or emergent results. Communication protocols and distributed data consistency mechanisms help to ensure consistent policy enforcement across a distributed system. To ensure a system-wide level of assurance of correct policy enforcement, the security architecture of a distributed composite system is thoroughly analyzed.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for SA-8(17) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- systems or system components that implement the security design principle of secure distributed composition are defined;
- <SA-08(17)_ODP systems or system components> implement the security design principle of secure distributed composition.
Examine
[SELECT FROM: System and services acquisition policy; procedures addressing the security design principle of secure distributed composition used in the specification, design, development, implementation, and modification of the system; system design documentation; security and privacy requirements and specifications for the system; system security and privacy architecture; system security plan; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with the responsibility for determining system security and privacy requirements; organizational personnel with system specification, design, development, implementation, and modification responsibilities; system developers; organizational personnel with information security responsibilities].
Test
[SELECT FROM: Organizational processes for applying the security design principle of secure distributed composition in system specification, design, development, implementation, and modification; mechanisms supporting the application of the security design principle of secure distributed composition in system specification, design, development, implementation, and modification].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SA-8(17). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- System and services acquisition policy
- system security plan
Configuration
- system design documentation
- system security and privacy architecture
Testing
- Organizational processes for applying the security design principle of secure distributed composition in system specification, design, development, implementation, and modification
- mechanisms supporting the application of the security design principle of secure distributed composition in system specification, design, development, implementation, and modification
Other Records
- procedures addressing the security design principle of secure distributed composition used in the specification, design, development, implementation, and modification of the system
- security and privacy requirements and specifications for the system
- other relevant documents or records