access-lifecycle — Claude Code plugin: audit departed staff access
The access-lifecycle plugin for Claude Code audits user access before compliance checks, detecting retained access for departed staff and mapping gaps to SOC 2, ISO 27001, or HIPAA controls.
MIT ★ 30,251 updated 2026-10-23
/plugin marketplace add alirezarezvani/claude-skills
/plugin install access-lifecycle@claude-code-skillsWhat access-lifecycle does
The plugin audits identity governance records using exported CSV files. Deterministic standard library Python scripts handle the reconciliation: matching personnel rosters against active account lists, validating access review campaigns, and mapping evidence directly to compliance controls. The diff script catches accounts belonging to departed personnel, actions taken after exit dates, and service accounts lacking assigned owners.
The campaign script checks whether reviewers approved their own entitlements or failed to revoke flagged permissions within the remediation window. The mapper assigns explicit test statuses to individual controls across SOC 2, ISO 27001, NIST 800-53, PCI DSS, HIPAA, and SOX IPE. The package includes the cs-access-reviewer subagent along with review sign-off templates.
Direct IdP connections are not needed. Running the checks requires only standard Python and local CSV exports.
What it helps with
- catch active accounts belonging to departed workers in CSV exports
- spot unassigned service accounts and orphaned administrative privileges
- flag self-approved access reviews and delayed revocation tickets
- map review exceptions to SOC 2, ISO 27001, and HIPAA compliance controls
Example prompts for the agent
- Run
/cs-access-diffonhr_roster.csvandaccounts.csvwith a 90-day inactivity filter. - Execute
/cs-access-reviewacrosshr_roster.csv,accounts.csv, andcampaign.csvtargeting SOC 2. - Ask the
cs-access-revieweragent to inspectcampaign.csvfor self-approval issues.
How to install access-lifecycle
Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install access-lifecycle@claude-code-skillsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about access-lifecycle
How do I install access-lifecycle in Claude Code?
First add the marketplace source by executing /plugin marketplace add alirezarezvani/claude-skills. Then install the package by running /plugin install access-lifecycle@claude-code-skills.
What does the access-lifecycle plugin do?
It compares personnel records against account lists and campaign logs to audit access controls. The underlying Python scripts detect dormant accounts, departed workers, and review procedural gaps.
Does this plugin require an active connection to an IdP or HR tool?
Direct network connections to external identity providers are unnecessary. The scripts rely entirely on Python standard library modules and read data from local CSV files.
Source text
access-lifecycle · MIT
# access-lifecycle > Access reviews fail audits in ordinary ways: an incomplete export, someone > approving their own access, a revoke nobody carried out, a leaver still enabled. Three deterministic scripts diff the HR roster against account exports, check a review campaign against the population it was built from, and map every exception to the SOC 2, ISO 27001, NIST 800-53, PCI DSS, HIPAA or SOX control it breaks. No IdP or HR connection, no network: export CSV and run. **Not audit advice.** Inactivity periods and remediation windows are your policy. ## Install ```bash /plugin marketplace add alirezarezvani/claude-skills /plugin install access-lifecycle@claude-code-skills ``` ## Use ```bash /cs-access-review hr_roster.csv accounts.csv campaign.csv --framework soc2,iso27001 # full pass /cs-access-diff hr_roster.csv accounts.csv --inactive-days 90 # just the diff ``` Or run the scripts directly. Each has `--help`, `--sample` and `--output json`: ```bash cd skills/access-lifecycle python scripts/access_diff.py --sample python scripts/access_review_campaign.py --sample python scripts/control_evidence_mapper.py --sample --framework soc2,iso27001,pci ``` ## The three scripts | Script | Question | Exit codes | |---|---|---| | `access_diff.py` | Who has access they should not? Leavers enabled or **used after exit**, orphans, ownerless service accounts, movers, privileged review age, inactivity | 0 · 2 findings · 3 · **4 blocked** | | `access_review_campaign.py` | Did the review cover the population, and did the revokes happen? **Population gaps**, undecided, **self-review**, unremoved revokes, late decisions, rubber-stamp signal | 0 · 2 · 3 · **4 incomplete** | | `control_evidence_mapper.py` | Which controls fail, and what evidence do we keep? FAIL / EXCEPTIONS / NO_EXCEPTIONS / PARTLY_TESTED / NOT_TESTED / NOT_COVERED — never PASS | 0 · 2 · 3 · **4 fail** | ## What it cites AICPA Trust Services Criteria CC6.1–CC6.3; NIST SP 800-53 Rev 5 AC-2, AC-2(3) and AC-5 with FedRAMP parameter values; PCI DSS v4.0.1 7.2.4, 7.2.5.1, 8.2.5 and 8.2.6; HIPAA 45 CFR 164.308(a)(3)(ii)(C); PCAOB AS 1105.10 and Staff Audit Practice Alert 11; ISO/IEC 27001:2022 Annex A titles. Every claim in `skills/access-lifecycle/references/` carries a confidence marker, and the finding-to-control mapping is labelled as our judgment. ## Distinct from - `soc2-compliance` — SOC 2 readiness and control design across all criteria. - `information-security-manager-iso27001` — ISMS design and Statement of Applicability. - `isms-audit-expert` — internal audit programme and nonconformity handling. ## License MIT. See the repository [LICENSE](../../LICENSE).
© Alireza Rezvani · MIT · alirezarezvani/claude-skills