Imported from node011/Bounty-Reaper (
.bountyreper/skill/NIST/SP800-53_rev5/SC_system-and-communications-protection/SC-28(1)_cryptographic-protection/SKILL.md). Install upstream withnpx skills add node011/Bounty-Reaper --skill SC-28(1)_cryptographic-protection. Copyright stays with the author.
SC-28(1) Cryptographic Protection
Enhancement of: SC-28
High-Level Description
Family: System and Communications Protection (SC) Framework: NIST SP 800-53 Rev 5
The selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of organizational information. The strength of mechanism is commensurate with the security category or classification of the information. Organizations have the flexibility to encrypt information on system components or media or encrypt data structures, including files, records, or fields.
What to Check
- Verify SC-28(1) Cryptographic Protection is documented in SSP
- Confirm control is operating effectively
- Review evidence of continuous monitoring for SC-28(1)
- Verify enhancement builds upon base control SC-28
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for SC-28(1) 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 |
|---|---|---|
| cloud-audit-mcp | Check encryption and network controls | cloud_audit_encryption |
| nmap | Network scanning | nmap -sV --script ssl-enum-ciphers |
Remediation Guide
Control Statement
Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on [organization-defined]: [organization-defined].
Implementation Guidance
The selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of organizational information. The strength of mechanism is commensurate with the security category or classification of the information. Organizations have the flexibility to encrypt information on system components or media or encrypt data structures, including files, records, or fields.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| SC-28(1) Cryptographic Protection not implemented | High | System and Communications Protection |
| SC-28(1) partially implemented | Medium | Incomplete System and Communications Protection |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-311 | Missing Encryption of Sensitive Data |
References
- NIST SP 800-53 Rev 5 - SC-28(1)
- NIST SP 800-53A Rev 5 (Assessment Procedures)
- NIST SP 800-53 Rev 5 Full Catalog
Checklist
- Control documented in SSP
- Implementation evidence collected
- Operating effectiveness validated
- Continuous monitoring in place
- Related controls (AC-19, SC-12, SC-13) reviewed