Skip to content

sickn33/agentic-awesome-skills / plugins/agentic-awesome-skills-claude/skills/access-review

access-review

Verified

Conduct periodic access reviews and certifications. Implement access governance and recertification workflows. Use when managing access compliance.

FileKindSize
SKILL.mdskill md11.4 KB
references/details.mdmarkdown3.3 KB

references/details.md

View on GitHub
# Details (moved from SKILL.md)

> Extended reference content for `access-review`, kept under `references/` so the entrypoint stays within the audit budget.

## Certification Workflow Automation

Automation design (no bundled executable workflow): use pinned read-only tooling
and workload identity, collect complete paginated inventory, then produce a private
review package. The upstream scripts named in the historical workflow are not
bundled. Creating issues/notifying managers needs an explicit recipient/repository
mandate and must not publish personal access inventories in a public issue.
Use a reviewed report body file and metadata-only aggregate counts; upload evidence
only to an approved access-controlled store with an organization-approved retention
policy. A 365-day Actions artifact retention may exceed account limits and is not
a substitute for a durable compliance evidence archive.

## Access Review Checklist

```yaml
access_review_checklist:
  preparation:
    - [ ] Define scope (systems, user populations, review period)
    - [ ] Assign review owners for each system
    - [ ] Extract current access data from all identity sources
    - [ ] Correlate identities across platforms via SSO mapping
    - [ ] Generate review packages for each manager

  execution:
    - [ ] Managers notified with review assignments and deadline
    - [ ] Privileged access reviewed first (admin, root, service accounts)
    - [ ] Each user's access certified (approve, modify, or revoke)
    - [ ] Inactive accounts flagged for disable/removal
    - [ ] Stale credentials (keys, tokens) flagged for rotation
    - [ ] Outside collaborators and contractors verified
    - [ ] Service account ownership confirmed

  remediation:
    - [ ] Revocations executed within SLA (5 business days)
    - [ ] Access modifications completed within SLA (10 business days)
    - [ ] Exceptions documented with business justification
    - [ ] Exception approvals recorded from security team
    - [ ] Changes verified in target systems

  reporting:
    - [ ] Review completion rate documented (target: 100%)
    - [ ] Non-response escalations documented
    - [ ] Remediation actions summarized
    - [ ] Exception register updated
    - [ ] Evidence archived for audit (retained according to approved legal/security policy)
    - [ ] Metrics compared to prior review cycle
```


## Best Practices

- Automate access data extraction to eliminate manual data gathering and reduce errors
- Integrate access review with HR systems to automatically flag accounts for departed employees
- Use risk-based review frequency: privileged access quarterly, standard access semi-annually
- Provide managers with clear context: show last login date, permissions, and role to inform decisions
- Set firm deadlines with escalation for non-response (non-response triggers owner escalation and a risk-approved decision, not blanket automatic revocation)
- Detect and eliminate orphaned accounts from contractors, former employees, and decommissioned services
- Review service accounts and API keys alongside human accounts to prevent credential sprawl
- Document all exceptions with business justification, approver, and expiration date
- Track review metrics over time: completion rates, revocation rates, time to remediate
- Archive all access review evidence for the approved policy period with access controls and minimization

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall