Implement the security design principle of acceptable security in [organization-defined].
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill SA-8(28)_acceptable-security --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of SA 8(28) Acceptable Security?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-sa-8-28-acceptable-security)More formats (shields.io, HTML) on the badges page.
---
name: "SA-8(28)_acceptable-security"
description: "Implement the security design principle of acceptable security in [organization-defined]."
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- sa-8-28
- sa
- enhancement
tech_stack:
- any
cwe_ids:
- CWE-16
chains_with: []
prerequisites:
- SA-8
severity_boost: {}
---
# SA-8(28) Acceptable Security
> **Enhancement of:** SA-8
## High-Level Description
**Family:** System and Services Acquisition (SA)
**Framework:** NIST SP 800-53 Rev 5
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.
## What to Check
- [ ] Verify SA-8(28) Acceptable Security is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for SA-8(28)
- [ ] Verify enhancement builds upon base control SA-8
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for SA-8(28) implementation details. Verify the organization has documented how this control is satisfied.
### Step 2: Validate Implementation
```
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly
# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
```
### Step 3: Test Operating Effectiveness
Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.
## Tools
| Tool | Purpose | Usage |
| ------------- | --------------------------------- | ----- |
| Manual Review | Documentation and interview-based | N/A |
## Remediation Guide
### Control Statement
Implement the security design principle of acceptable security in [organization-defined].
### Implementation 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.
## Risk Assessment
| Finding | Severity | Impact |
| -------------------------------------------- | -------- | ------------------------------------------ |
| SA-8(28) Acceptable Security not implemented | Medium | System and Services Acquisition |
| SA-8(28) partially implemented | Low | Incomplete System and Services Acquisition |
## CWE Categories
| CWE ID | Title |
| ------ | ------------- |
| CWE-16 | Configuration |
## References
- [NIST SP 800-53 Rev 5 - SA-8(28)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=sa-8.28)
- [NIST SP 800-53A Rev 5 (Assessment Procedures)](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final)
- [NIST SP 800-53 Rev 5 Full Catalog](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)
## Checklist
- [ ] Control documented in SSP
- [ ] Implementation evidence collected
- [ ] Operating effectiveness validated
- [ ] Continuous monitoring in place
- [ ] Related controls (none) reviewed
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!