Monitor the use of maintenance tools that execute with increased privilege.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill MA-3(5)_execution-with-privilege --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of MA 3(5) Execution With Privilege?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-ma-3-5-execution-with-privilege)More formats (shields.io, HTML) on the badges page.
---
name: "MA-3(5)_execution-with-privilege"
description: "Monitor the use of maintenance tools that execute with increased privilege."
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- ma-3-5
- ma
- enhancement
tech_stack:
- linux
- windows
cwe_ids: []
chains_with:
- AC-3
- AC-6
prerequisites:
- MA-3
severity_boost:
AC-3: "Chain with AC-3 for comprehensive security coverage"
AC-6: "Chain with AC-6 for comprehensive security coverage"
---
# MA-3(5) Execution with Privilege
> **Enhancement of:** MA-3
## High-Level Description
**Family:** Maintenance (MA)
**Framework:** NIST SP 800-53 Rev 5
Maintenance tools that execute with increased system privilege can result in unauthorized access to organizational information and assets that would otherwise be inaccessible.
## What to Check
- [ ] Verify MA-3(5) Execution with Privilege is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for MA-3(5)
- [ ] Verify enhancement builds upon base control MA-3
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for MA-3(5) 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
Monitor the use of maintenance tools that execute with increased privilege.
### Implementation Guidance
Maintenance tools that execute with increased system privilege can result in unauthorized access to organizational information and assets that would otherwise be inaccessible.
## Risk Assessment
| Finding | Severity | Impact |
| ------------------------------------------------ | -------- | ---------------------- |
| MA-3(5) Execution with Privilege not implemented | Medium | Maintenance |
| MA-3(5) partially implemented | Low | Incomplete Maintenance |
## CWE Categories
| CWE ID | Title |
| ------ | --------------------- |
| N/A | No direct CWE mapping |
## References
- [NIST SP 800-53 Rev 5 - MA-3(5)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=ma-3.5)
- [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-3, AC-6) 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!