OpenParable
Skip to content
← Back to skills

AC-2(7)_privileged-user-accounts

DevOps & Security

AC-2(7)_privileged-user-accounts is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Establish and administer privileged user accounts in accordance with [organization-defined];

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/AC_access-control/AC-2(7)_privileged-user-accounts/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ac-2-7-privileged-user-accounts, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

AC-2(7) Privileged User Accounts

Enhancement of: AC-2

High-Level Description

Family: Access Control (AC) Framework: NIST SP 800-53 Rev 5

Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. Privileged roles include key management, account management, database administration, system and network administration, and web administration. A role-based access scheme organizes permitted system access and privileges into roles. In contrast, an attribute-based access scheme specifies allowed system access and privileges based on attributes.

What to Check

  • Verify AC-2(7) Privileged User Accounts is documented in SSP
  • Validate all 4 control requirements are implemented
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for AC-2(7)
  • Verify enhancement builds upon base control AC-2

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AC-2(7) 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

ToolPurposeUsage
cloud-audit-mcpCheck IAM policies and access controlscloud_audit_iam_policies
hackbrowser-mcpTest web application access controlsbrowser_auth_test

Remediation Guide

Control Statement

Establish and administer privileged user accounts in accordance with [organization-defined]; Monitor privileged role or attribute assignments; Monitor changes to roles or attributes; and Revoke access when privileged role or attribute assignments are no longer appropriate.

Implementation Guidance

Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. Privileged roles include key management, account management, database administration, system and network administration, and web administration. A role-based access scheme organizes permitted system access and privileges into roles. In contrast, an attribute-based access scheme specifies allowed system access and privileges based on attributes.

Risk Assessment

FindingSeverityImpact
AC-2(7) Privileged User Accounts not implementedHighAccess Control
AC-2(7) partially implementedMediumIncomplete Access Control

CWE Categories

CWE IDTitle
CWE-284Improper Access Control

References

Checklist

  • Control documented in SSP
  • Implementation evidence collected
  • Operating effectiveness validated
  • Continuous monitoring in place
  • Related controls (none) reviewed