Log [organization-defined] for nonlocal maintenance and diagnostic sessions;
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill MA-4(1)_logging-and-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of MA 4(1) Logging And Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-ma-4-1-logging-and-review)More formats (shields.io, HTML) on the badges page.
---
name: "MA-4(1)_logging-and-review"
description: "Log [organization-defined] for nonlocal maintenance and diagnostic sessions;"
category: "configuration"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- ma-4-1
- ma
- enhancement
tech_stack:
- linux
- windows
cwe_ids: []
chains_with:
- AU-6
- AU-12
prerequisites:
- MA-4
severity_boost:
AU-6: "Chain with AU-6 for comprehensive security coverage"
AU-12: "Chain with AU-12 for comprehensive security coverage"
---
# MA-4(1) Logging and Review
> **Enhancement of:** MA-4
## High-Level Description
**Family:** Maintenance (MA)
**Framework:** NIST SP 800-53 Rev 5
Audit logging for nonlocal maintenance is enforced by [AU-2](#au-2) . Audit events are defined in [AU-2a](#au-2_smt.a).
## What to Check
- [ ] Verify MA-4(1) Logging and Review is documented in SSP
- [ ] Validate all 2 control requirements are implemented
- [ ] Confirm control is operating effectively
- [ ] Review evidence of continuous monitoring for MA-4(1)
- [ ] Verify enhancement builds upon base control MA-4
## How to Test
### Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for MA-4(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
Log [organization-defined] for nonlocal maintenance and diagnostic sessions; and
Review the audit records of the maintenance and diagnostic sessions to detect anomalous behavior.
### Implementation Guidance
Audit logging for nonlocal maintenance is enforced by [AU-2](#au-2) . Audit events are defined in [AU-2a](#au-2_smt.a).
## Risk Assessment
| Finding | Severity | Impact |
| ------------------------------------------ | -------- | ---------------------- |
| MA-4(1) Logging and Review not implemented | Medium | Maintenance |
| MA-4(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-4(1)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=ma-4.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 (AU-6, AU-12) 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!