Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill MA-3(1)_inspect-tools --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of MA 3(1) Inspect Tools?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-ma-3-1-inspect-tools)More formats (shields.io, HTML) on the badges page.
---
name: "MA-3(1)_inspect-tools"
description: "Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications."
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- ma-3-1
- ma
- enhancement
tech_stack:
- linux
- windows
cwe_ids: []
chains_with:
- SI-7
prerequisites:
- MA-3
severity_boost:
SI-7: "Chain with SI-7 for comprehensive security coverage"
---
# MA-3(1) Inspect Tools
> **Enhancement of:** MA-3
## High-Level Description
**Family:** Maintenance (MA)
**Framework:** NIST SP 800-53 Rev 5
Maintenance tools can be directly brought into a facility by maintenance personnel or downloaded from a vendor’s website. If, upon inspection of the maintenance tools, organizations determine that the tools have been modified in an improper manner or the tools contain malicious code, the incident is handled consistent with organizational policies and procedures for incident handling.
## What to Check
- [ ] Verify MA-3(1) Inspect Tools is documented in SSP
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for MA-3(1)
- [ ] 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(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 |
| ------------- | --------------------------------- | ----- |
| Manual Review | Documentation and interview-based | N/A |
## Remediation Guide
### Control Statement
Inspect the maintenance tools used by maintenance personnel for improper or unauthorized modifications.
### Implementation Guidance
Maintenance tools can be directly brought into a facility by maintenance personnel or downloaded from a vendor’s website. If, upon inspection of the maintenance tools, organizations determine that the tools have been modified in an improper manner or the tools contain malicious code, the incident is handled consistent with organizational policies and procedures for incident handling.
## Risk Assessment
| Finding | Severity | Impact |
| ------------------------------------- | -------- | ---------------------- |
| MA-3(1) Inspect Tools not implemented | Medium | Maintenance |
| MA-3(1) 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(1)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=ma-3.1)
- [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 (SI-7) 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!