Skip to content
Skillpedia
General coding35k · #6127

performing-privileged-account-access-review

Has your agent review who has special access on systems. It checks if permissions are needed and if there are no old or excessive accesses. It's useful for ensuring only the right people have access to sensitive information.

What it does

This tool checks who has special access (like administrators) and if that access is still needed. It helps ensure only the right people have elevated permissions, following security rules.

When to use it

  • ✓For mandatory security audits.
  • ✓To periodically review special accesses.
  • ✓When investigating unusual access.

Example of what to ask your AI

“Review access for system administrators and service accounts.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/main/skills/performing-privileged-account-access-review/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/main/skills/performing-privileged-account-access-review/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool lists all accounts with special access, checks if the access is justified and complies with policies. If access is no longer needed, it is removed.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-privileged-account-access-review

Or download just the file:

curl -L https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/main/skills/performing-privileged-account-access-review/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Performing Privileged Account Access Review

Overview

Privileged Account Access Review is a critical identity governance process that validates whether users with elevated permissions still require their access. This review covers domain admins, service accounts, database administrators, cloud IAM roles, and application-level privileged accounts. Regular access reviews are mandated by SOC 2, PCI DSS, HIPAA, and SOX compliance frameworks, typically required quarterly for high-privilege accounts.

When to Use

  • When conducting security assessments that involve performing privileged account access review
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • PAM solution deployed (CyberArk, BeyondTrust, Delinea, or equivalent)
  • Identity governance platform (SailPoint, Saviynt, or equivalent)
  • Complete inventory of privileged accounts across all platforms
  • Defined access review policy with SLAs and escalation procedures
  • Designated reviewers (account owners, managers, security team)

Core Concepts

Privileged Account Categories

Category Examples Risk Level Review Frequency
Domain Admins Enterprise Admin, Domain Admin, Schema Admin Critical Monthly
Service Accounts SQL service, backup agents, monitoring agents High Quarterly
Cloud IAM AWS root, Azure Global Admin, GCP Owner Critical Monthly
Database Admin DBA accounts, sa/sys accounts High Quarterly
Application Admin App admin roles, API keys with admin scope Medium Semi-annually
Emergency/Break-glass Firecall accounts, emergency access Critical After each use

Four-Pillar Review Framework

DISCOVER                    VALIDATE                    REMEDIATE                 MONITOR
    │                           │                           │                       │
    ├─ Enumerate all            ├─ Verify business          ├─ Remove excess        ├─ Continuous
    │  privileged accounts      │  justification            │  privileges           │  monitoring
    │                           │                           │                       │
    ├─ Identify orphaned        ├─ Confirm account          ├─ Disable orphaned     ├─ Anomaly
    │  accounts                 │  ownership                │  accounts             │  detection
    │                           │                           │                       │
    ├─ Map permissions to       ├─ Check compliance         ├─ Enforce password     ├─ Session
    │  business roles           │  with policies            │  rotation             │  recording
    │                           │                           │                       │
    └─ Classify by risk         └─ Review last usage        └─ Implement JIT        └─ Audit
       level                       and activity                access                  logging

Workflow

Step 1: Account Discovery and Inventory

Enumerate all privileged accounts across the environment:

Active Directory:

  • Domain Admins, Enterprise Admins, Schema Admins groups
  • Accounts with AdminCount=1 attribute
  • Service accounts with SPN (Service Principal Names)
  • Accounts with delegation rights (Unconstrained/Constrained)

Cloud Platforms:

  • AWS: IAM users/roles with AdministratorAccess, PowerUserAccess, or iam:* permissions
  • Azure: Global Administrator, Privileged Role Administrator, Security Administrator roles
  • GCP: Owner, Editor roles at organization/project level

Databases:

  • SQL Server: sysadmin, db_owner, securityadmin fixed roles
  • Oracle: DBA, SYSDBA, SYSOPER privileges
  • PostgreSQL: superuser, createrole, createdb attributes

Step 2: Establish Review Criteria

Each privileged account must be evaluated against:

  1. Business Justification: Does the user's current role require this privilege?
  2. Least Privilege: Can the task be performed with lower privileges?
  3. Account Activity: Has the account been active in the last 90 days?
  4. Compliance Status: Does the account meet password policy, MFA requirements?
  5. Separation of Duties: Does the access create SoD conflicts?
  6. Ownership: Is a responsible owner assigned and active?

Step 3: Conduct the Review

For each account, the designated reviewer must:

…

FAQ

What are 'privileged accounts'?

These are accounts with elevated permissions, like system administrators, service accounts, or database administrators, which can make significant changes to systems.

Why is it important to review these accesses?

To prevent unnecessary or unauthorized access that could be used for malicious activities, and to comply with security and regulatory requirements.

What happens if an access is no longer needed?

The access is revoked or reduced to the minimum necessary, ensuring security is maintained and only essential permissions are granted.

Details

Original description by the author

Conducts systematic reviews of privileged accounts to validate access rights, identify excessive or stale permissions, and enforce least privilege across PAM infrastructure. Use when auditing privileged access for compliance, periodic access recertification, or investigating whether privileged entitlements are still justified.

repo: mukul975/Anthropic-Cybersecurity-Skills

Popularity

GitHub stars
35k
Ranking position
#6127
License
Apache-2.0
Updated
8/31/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills