access-lifecycle – skill Lập trình cho agent AI
Dùng khi chuẩn bị hoặc thực hiện đợt rà soát quyền truy cập người dùng, kiểm tra người đã nghỉ việc có còn mất quyền truy cập không, tìm tài khoản dịch vụ mồ côi hoặc không có chủ sở hữu, trả lời yêu cầu kiểm toán về kiểm soát truy cập theo SOC 2, ISO 27001, PCI DSS, HIPAA hoặc NIST 800-53, hoặc kiểm tra đợt rà soát đã hoàn tất có đủ vững không. So khớp danh sách nhân sự từ HR
Cài skill access-lifecycle bằng một lệnh
Chọn công cụ bạn đang dùng, copy lệnh và dán vào terminal. Skill sẽ nằm trong thư mục skills của công cụ đó và sẵn sàng dùng ở phiên làm việc tiếp theo.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/access-lifecycle-a0886.tgz | tar xz -C ~/.claude/skills
Gọi trong Claude Code: /access-lifecycle – rồi mô tả công việc bạn muốn làm.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/access-lifecycle-a0886.tgz | tar xz -C ~/.codex/skills
Gọi trong Codex: $access-lifecycle – rồi mô tả công việc bạn muốn làm.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/access-lifecycle-a0886.tgz | tar xz -C ~/.hermes/skills
Gọi trong Hermes Agent: /access-lifecycle – rồi mô tả công việc bạn muốn làm.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/access-lifecycle-a0886.tgz | tar xz -C ~/.deepcode/skills
Gọi trong DeepSeek: /access-lifecycle – rồi mô tả công việc bạn muốn làm.
Nội dung SKILL.md
Nội dung SKILL.md gốc bằng tiếng Anh.
Access Lifecycle
> Portability: 3 stdlib scripts, no network, no IdP or HR connection. Export CSV, run, keep the output as evidence.
> Not audit advice. Periods and thresholds are your policy; the scripts make you state them.
Access reviews fail audits in four ordinary ways: the review ran on an incomplete
export, someone approved their own access, a revoke was decided and never
carried out, and leavers kept working accounts nobody looked at. Each script
catches one class of these before the auditor does.
Workflow
# 1 - Diff: who has access that the HR roster says they should not?
python scripts/access_diff.py --roster hr_roster.csv --accounts accounts.csv \
--inactive-days 90 --privileged-review-days 90 --as-of 2026-10-31
# 2 - Campaign: did the review cover everything, and did the revokes happen?
python scripts/access_review_campaign.py --decisions campaign.csv --population accounts.csv \
--remediation-days 10 --close-date 2026-10-20
# 3 - Map: which controls do the exceptions break, and what evidence do you keep?
python scripts/control_evidence_mapper.py --diff diff.json --campaign campaign.json --framework soc2,iso27001Step 1 joins each account to the roster on employee ID, then email. A
terminated person with an enabled account is a blocker; one who logged in after
their exit date is a worse one. Accounts that match nobody are orphans; service
accounts need a named owner. Inactivity and privileged-review age use your periods.
Step 2 checks the campaign against the export it was built from. An enabled
account missing from the campaign means the review did not cover the population,
whatever the sign-off sheet says. It also catches undecided lines, self-review,
revokes not removed inside your window, late decisions, and a reviewer who kept
every line of a large batch at machine speed.
Step 3 turns findings into a per-control table: FAIL, EXCEPTIONS,
NO_EXCEPTIONS, PARTLY_TESTED, NOT_TESTED or NOT_COVERED, each with what an
auditor tests and the evidence to keep. There is no PASS.
The gates block on (exit 4)
1. A leaver with an enabled account, or any login after the exit date.
2. A privileged orphan account, or a privileged service account with no owner.
3. An enabled account the campaign never reviewed.
4. An undecided line, a self-review, or a decision with no reviewer named.
5. A revoke or modify with no removal recorded past your remediation window.
Hard rules
- Periods are policy.
--inactive-daysand--remediation-dayshave no default. PCI DSS 8.2.6 says 90 days; your policy may differ. - Prove removals by re-export. A closed ticket is not evidence the access is gone.
- The export is evidence too. Keep the query, the pull time and the row count (PCAOB AS 1105.10).
- A rubber-stamp flag is a signal, not proof. Ask the reviewer what they checked; do not call it fraud.
- No PASS from a script. Operating effectiveness is the auditor's conclusion.
Scripts
| Script | Role | Exit codes |
|---|---|---|
| scripts/access_diff.py | Roster vs account export: leavers, orphans, ownerless service accounts, movers, privileged review age, inactivity | 0 clean · 2 findings · 3 bad input · 4 blocked |
| scripts/access_review_campaign.py | Population coverage, undecided, self-review, unremoved revokes, late decisions, rubber-stamp signal | 0 · 2 · 3 · 4 incomplete |
| scripts/control_evidence_mapper.py | Findings → per-control status for ISO 27001, SOC 2, NIST 800-53, PCI DSS, HIPAA, SOX IPE | 0 · 2 exceptions · 3 · 4 fail |
All support --help, --sample and --output json.
References and assets
- [
references/joiner_mover_leaver_standards.md](references/joiner_mover_leaver_standards.md) — what each framework requires for provisioning, change and removal (7 sources) - [
references/access_review_campaigns.md](references/access_review_campaigns.md) — population, reviewers, cadence, remediation, what auditors reject (6 sources) - [
references/control_crosswalk.md](references/control_crosswalk.md) — finding codes to controls across six frameworks, with the caveats (7 sources) - [
assets/hr_roster.example.csv](assets/hr_roster.example.csv), [assets/accounts.example.csv](assets/accounts.example.csv), [assets/campaign.example.csv](assets/campaign.example.csv) — input formats - [
assets/access_review_signoff.md](assets/access_review_signoff.md) — campaign sign-off with the evidence fields a reviewer fills in
Skill liên quan
- adversarial-reviewer – Review code đối kháng nhằm phá vỡ thói quen tự review. Dùng khi muốn một đánh giá thực…
- access-review – Thực hiện rà soát quyền truy cập và chứng nhận định kỳ. Triển khai quy trình quản trị…
- api-design-principles – Nắm vững nguyên tắc thiết kế REST và GraphQL để xây dựng API trực quan, mở rộng tốt và…
- cli-creator – Xây dựng CLI có thể kết hợp cho Codex từ tài liệu API, đặc tả OpenAPI, ví dụ curl có…
- create-plan – Tạo một kế hoạch ngắn gọn. Dùng khi người dùng yêu cầu rõ ràng một kế hoạch cho tác vụ…
- code-review-and-quality – Thực hiện đánh giá mã nguồn đa chiều. Dùng trước khi merge bất kỳ thay đổi nào. Dùng khi…
- active-directory-attacks – Đánh giá các đường tấn công Active Directory bằng cách rà soát cấu hình trong phạm vi…
- address-github-comments – Dùng khi cần xử lý các bình luận review hoặc issue trên Pull Request GitHub đang mở bằng…