Ensure compliance with [organization-defined].
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill CM-7(3)_registration-compliance --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of CM 7(3) Registration Compliance?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cm-7-3-registration-compliance)More formats (shields.io, HTML) on the badges page.
---
name: "CM-7(3)_registration-compliance"
description: "Ensure compliance with [organization-defined]."
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- cm-7-3
- cm
- enhancement
tech_stack:
- aws
- azure
- gcp
- linux
- windows
cwe_ids:
- CWE-16
chains_with: []
prerequisites:
- CM-7
severity_boost: {}
---
# CM-7(3) Registration Compliance
> **Enhancement of:** CM-7
## High-Level Description
**Family:** Configuration Management (CM)
**Framework:** NIST SP 800-53 Rev 5
Organizations use the registration process to manage, track, and provide oversight for systems and implemented functions, ports, protocols, and services.
## What to Check
- [ ] Verify CM-7(3) Registration Compliance is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for CM-7(3)
- [ ] Verify enhancement builds upon base control CM-7
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CM-7(3) 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 configuration baselines | `cloud_audit_config` |
| AWS CLI | Review Config rules | `aws configservice describe-config-rules` |
## Remediation Guide
### Control Statement
Ensure compliance with [organization-defined].
### Implementation Guidance
Organizations use the registration process to manage, track, and provide oversight for systems and implemented functions, ports, protocols, and services.
## Risk Assessment
| Finding | Severity | Impact |
| ----------------------------------------------- | -------- | ----------------------------------- |
| CM-7(3) Registration Compliance not implemented | Medium | Configuration Management |
| CM-7(3) partially implemented | Low | Incomplete Configuration Management |
## CWE Categories
| CWE ID | Title |
| ------ | ------------- |
| CWE-16 | Configuration |
## References
- [NIST SP 800-53 Rev 5 - CM-7(3)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=cm-7.3)
- [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!