Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
mukul975/performing-privileged-account-access-reviewInformes y cumplimiento

performing-privileged-account-access-review

⁨Conducts systematic reviews of privileged accounts to validate access⁩

v1.03 instalaciones+3 en 7 días36,3 mil EstrellasApache-2.0sincronizado hace 12 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/performing-privileged-account-access-review

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
bIfV8b8J4F…4rJb3XDg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete1c2347d1…5254c4f1
1c2347d18f60…6da85254c4f18 archivos · ⁦14.4 KB⁩
EscaneoMedio3 hallazgos
  • Script ejecutable incluido con la skillscripts/agent.py
  • Script ejecutable incluido con la skillscripts/process.py
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/performing-privileged-account-access-review@54a7988

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

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

text
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:

  1. Review the account details, permissions, and last activity date
  2. Approve (certify) the access if still required with documented justification
  3. Revoke access if no longer needed or the reviewer cannot justify the privilege
  4. Flag for investigation if anomalous activity or policy violations are detected
  5. Escalate if the reviewer cannot make a determination

Decision matrix:

Condition Action
Active user, justified privilege Certify - maintain access
Active user, excessive privilege Remediate - reduce to least privilege
Inactive > 90 days Disable account, notify owner
No owner identified Disable account, escalate to security
SoD conflict detected Remediate - reassign or add compensating controls
Break-glass account Verify last use was authorized, reset credentials

Step 4: Remediation and Enforcement

After reviews are completed:

  • Revoke access for accounts that were not certified within the SLA period
  • Implement automatic revocation for accounts not reviewed within 14 days
  • Rotate credentials for all certified privileged accounts
  • Convert standing privileges to just-in-time (JIT) access where possible
  • Update PAM vault with current account inventory

Step 5: Reporting and Documentation

Generate review reports including:

  • Total accounts reviewed vs. total in scope
  • Certification rate (approved vs. revoked)
  • Average review completion time
  • Overdue reviews and escalations
  • Remediation actions taken
  • Comparison with previous review cycle

Validation Checklist

  • Complete inventory of all privileged accounts documented
  • All accounts assigned to a responsible owner/reviewer
  • Review criteria and decision matrix defined
  • Reviewers completed certification within SLA (14 days)
  • Revoked accounts disabled and credentials rotated
  • Orphaned accounts identified and disabled
  • Service accounts reviewed for least privilege
  • Break-glass accounts audited for authorized use only
  • Review report generated with metrics and trends
  • Remediation tickets created and tracked to completion
  • Evidence preserved for compliance audit

References

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaArchivo · Script ejecutable incluido con la skillscripts/agent.py
  2. MediaArchivo · Script ejecutable incluido con la skillscripts/process.py
  3. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v1.013 nov 202654a79881c2347d1Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login