Skip to content

alirezarezvani/claude-skills / ra-qm-team/skills/access-lifecycle

access-lifecycle

Verified

Use when preparing or running a user access review, checking that leavers lost their access, finding orphaned or ownerless service accounts, answering an auditor's access-control request for SOC 2, ISO 27001, PCI DSS, HIPAA or NIST 800-53, or checking whether a finished review campaign will hold up. Diffs the HR roster against account exports, tests the campaign for coverage, self-review, unremoved revokes and rubber-stamping, and maps every exception to the controls it breaks.

assets/access_review_signoff.md

View on GitHub
# Access review sign-off

One sheet per system per campaign. Attach the `--output json` results of
`access_review_campaign.py` and `control_evidence_mapper.py`.

| Field | Value |
|---|---|
| System / application | |
| Campaign period and close date | |
| Export used (report or query name) | |
| Export pulled by, and when | |
| Rows in export / rows in source system's own count | / |
| Lines in campaign | |
| Script verdict | COMPLETE / COMPLETE_WITH_FINDINGS / INCOMPLETE |
| Remediation window (policy) | ___ days |

## Population (AS 1105.10)

- How was the export's completeness checked? (row count tie-out, second source, control over the report)
- Accounts excluded from the campaign, and why (must be none, or each justified):

## Revokes and modifications

| Account | Decision | Decided | Removed | Re-export confirming removal (file, date) |
|---|---|---|---|---|
| | revoke / modify | | | |

## Reviewers

A signature alone is not evidence of review. Each reviewer records what they checked.

| Reviewer | Lines | Keep / revoke / modify | What I compared each line against | Date |
|---|---|---|---|---|
| | | / / | (role description, ticket, manager confirmation) | |

No reviewer may appear as the user on a line they decided.

## Exceptions open at sign-off

| Finding | Account | Owner | Due | Compensating step |
|---|---|---|---|---|
| | | | | |

## Approval

- System owner: ________ Date: ________
- Conclusion: ☐ complete ☐ complete with exceptions listed above ☐ returned (reason): ________
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall