Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Cm 11 2 Software Installation With?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cm-11-2-software-installation-with)
---
name: "CM-11(2)_software-installation-with-privileged-status"
description: "Allow user installation of software only with explicit privileged status."
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- cm-11-2
- cm
- enhancement
tech_stack:
- aws
- azure
- gcp
- linux
- windows
cwe_ids:
- CWE-16
chains_with:
- AC-5
- AC-6
prerequisites:
- CM-11
severity_boost:
AC-5: "Chain with AC-5 for comprehensive security coverage"
AC-6: "Chain with AC-6 for comprehensive security coverage"
---
# CM-11(2) Software Installation with Privileged Status
> **Enhancement of:** CM-11
## High-Level Description
**Family:** Configuration Management (CM)
**Framework:** NIST SP 800-53 Rev 5
Privileged status can be obtained, for example, by serving in the role of system administrator.
## What to Check
- [ ] Verify CM-11(2) Software Installation with Privileged Status is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for CM-11(2)
- [ ] Verify enhancement builds upon base control CM-11
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CM-11(2) 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
Allow user installation of software only with explicit privileged status.
### Implementation Guidance
Privileged status can be obtained, for example, by serving in the role of system administrator.
## Risk Assessment
| Finding | Severity | Impact |
| --------------------------------------------------------------------- | -------- | ----------------------------------- |
| CM-11(2) Software Installation with Privileged Status not implemented | Medium | Configuration Management |
| CM-11(2) partially implemented | Low | Incomplete Configuration Management |
## CWE Categories
| CWE ID | Title |
| ------ | ------------- |
| CWE-16 | Configuration |
## References
- [NIST SP 800-53 Rev 5 - CM-11(2)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=cm-11.2)
- [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 (AC-5, AC-6) reviewed