Self-reliant Trustworthiness
LOW MODERATE HIGHRequirements NIST SOURCE
Implement the security design principle of self-reliant trustworthiness in [systems or system components].
Discussion (NIST Supplemental Guidance)
The principle of self-reliant trustworthiness states that systems minimize their reliance on other systems for their own trustworthiness. A system is trustworthy by default, and any connection to an external entity is used to supplement its function. If a system were required to maintain a connection with another external entity in order to maintain its trustworthiness, then that system would be vulnerable to malicious and non-malicious threats that could result in the loss or degradation of that connection. The benefit of the principle of self-reliant trustworthiness is that the isolation of a system will make it less vulnerable to attack. A corollary to this principle relates to the ability of the system (or system component) to operate in isolation and then resynchronize with other components when it is rejoined with them.
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(16) 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 self-reliant trustworthiness are defined;
- <SA-08(16)_ODP systems or system components> implement the security design principle of self-reliant trustworthiness.
Examine
[SELECT FROM: System and services acquisition policy; procedures addressing the security design principle of self-reliant trustworthiness 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 self-reliant trustworthiness in system specification, design, development, implementation, and modification; mechanisms supporting the application of the security design principle of self-reliant trustworthiness in system specification, design, development, implementation, and modification].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SA-8(16). 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 self-reliant trustworthiness in system specification, design, development, implementation, and modification
- mechanisms supporting the application of the security design principle of self-reliant trustworthiness in system specification, design, development, implementation, and modification
Other Records
- procedures addressing the security design principle of self-reliant trustworthiness 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