Acceptable Security
LOW MODERATE HIGHRequirements NIST SOURCE
Implement the security design principle of acceptable security in [systems or system components].
Discussion (NIST Supplemental Guidance)
The principle of acceptable security requires that the level of privacy and performance that the system provides is consistent with the users’ expectations. The perception of personal privacy may affect user behavior, morale, and effectiveness. Based on the organizational privacy policy and the system design, users should be able to restrict their actions to protect their privacy. When systems fail to provide intuitive interfaces or meet privacy and performance expectations, users may either choose to completely avoid the system or use it in ways that may be inefficient or even insecure.
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(28) 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 acceptable security are defined;
- <SA-08(28)_ODP systems or system components> implement the security design principle of acceptable security.
Examine
[SELECT FROM: System and services acquisition policy; system and services acquisition procedures; procedures addressing the security design principle of acceptable security 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; personally identifiable information processing policy; privacy notifications provided to users; system security plan; privacy plan; privacy impact assessment; privacy risk assessment documentation; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with information security and privacy responsibilities; organizational personnel with system specification, design, development, implementation, and modification responsibilities; system developers].
Test
[SELECT FROM: Organizational processes for applying the security design principle of acceptable security in system specification, design, development, implementation, and modification; mechanisms supporting the application of the security design principle of acceptable security in system specification, design, development, implementation, and modification; mechanisms that enforce security policies].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SA-8(28). 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
- personally identifiable information processing policy
- system security plan
- privacy plan
Configuration
- system design documentation
- system security and privacy architecture
Testing
- Organizational processes for applying the security design principle of acceptable security in system specification, design, development, implementation, and modification
- mechanisms supporting the application of the security design principle of acceptable security in system specification, design, development, implementation, and modification
- mechanisms that enforce security policies
Other Records
- system and services acquisition procedures
- procedures addressing the security design principle of acceptable security used in the specification, design, development, implementation, and modification of the system
- security and privacy requirements and specifications for the system
- privacy notifications provided to users
- privacy impact assessment
- privacy risk assessment documentation
- other relevant documents or records