NIST SP 800-171
Control 3.12.4
Develop and Update System Security Plans
CMMC-RP Certified Team
24+ Years Experience
2,500+ Clients Served
Official Requirement
Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems.
What This Means in Plain English
You must have a System Security Plan (SSP) that documents your security environment, system boundaries, how each control is implemented, and connections to other systems. This document must be kept current.
How Petronella Implements This Control
Petronella Technology Group implements this control through:
- Comprehensive System Security Plan (SSP) documenting all 110 NIST 800-171 control implementations
- System boundary diagrams showing CUI data flow and enclave boundaries
- Annual SSP review and update cycle with version control
- ComplianceArmor generating and maintaining the SSP with implementation details for each control
- SSP updates triggered by significant system changes or environment modifications
Assessment Guidance
Assessors will review the SSP for completeness and accuracy, verify that system boundaries are clearly defined, check that all 110 controls are addressed, and confirm that the SSP reflects the current environment and is regularly updated.
Common Implementation Gaps
- No System Security Plan documented
- SSP does not cover all 110 controls
- SSP outdated and does not reflect current environment
- System boundaries not clearly defined
- Interconnections with other systems not documented
Cross-Framework Mapping
| Framework | Mapped Controls |
|---|---|
| NIST SP 800-53 | PL-2 |
Need Help Implementing 3.12.4?
Our CMMC-RP certified team can assess your current compliance posture and build a remediation plan.
Schedule a Compliance Assessment