itgov-identity-lifecycle-access-review-and-segregation-of-duties
Use when access accumulates faster than it is removed: the identity lifecycle from joiner through mover to leaver and why the mover case causes most privilege creep, access review and certification including how to run one that is not rubber-stamped, and segregation of duties covering the conflict matrix and compensating controls.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 5
- Forks
- 3
01 前言 Front Matter
- name
- itgov-identity-lifecycle-access-review-and-segregation-of-duties
- description
- Use when access accumulates faster than it is removed: the identity lifecycle from joiner through mover to leaver and why the mover case causes most privilege creep, access review and certification including how to run one that is not rubber-stamped, and segregation of duties covering the conflict matrix and compensating controls.
03 SKILL.md 正文
IT Infrastructure and Governance: The Identity Lifecycle, Access Review, and Segregation of Duties
Part 3 of 5 of the IT Infrastructure and Governance reference (plugin
it-infrastructure-governance), covering §9–§11. Sibling skills:itgov-infrastructure-layers-compute-storage-and-networking(§0–§4),itgov-directory-authentication-authorization-and-privileged-access(§5–§8),itgov-endpoints-continuity-itsm-and-vendor-risk(§12–§19),itgov-reference(§20–§26). Section numbers are shared across the set; a reference written as §N →skillpoints into that sibling skill.Currency: RBAC theory, directory concepts, backup strategy and ITIL process are stable. Two areas moved. See §21 →
itgov-referencefor the phishing-resistant authentication mandate timeline and non-human identity governance.
⚠️ Scope. The enterprise on-prem and hybrid layer. Complements a Linux server administration reference (host-level operations), a cloud reference (cloud-native patterns), and a security reference (threat modelling and defensive controls). ⚠️ The through-line here is access: who and what can do what, how you know, and how you prove it.
⚠️ GOTCHA boxes mark the things that cause audit findings and breaches.
The three ideas that organize this:
- ⚠️ Identity is the perimeter. The network boundary stopped being the control point years ago. Every meaningful access decision now happens at authentication and authorization time (§5 →
itgov-directory-authentication-authorization-and-privileged-access, §6 →itgov-directory-authentication-authorization-and-privileged-access).- ⚠️ Access accumulates and never sheds by itself. People change roles and keep old permissions; service accounts outlive their systems. Privilege creep is the default state of any system without deliberate revocation (§9, §10).
- ⚠️ Governance is the ability to answer "who has access to what, why, and who approved it" — with evidence. If you cannot answer it, you do not have governance, you have configuration (§10, §17 →
itgov-endpoints-continuity-itsm-and-vendor-risk).
§9. Identity Lifecycle (Joiner-Mover-Leaver)
JOINER ⚠️ provisioning driven from an authoritative source (HR system), not tickets
MOVER ⚠️ THE HARD ONE — see below
LEAVER ⚠️ deprovision everything, promptly, including non-SSO apps
⚠️ GOTCHA — the "mover" case is where privilege creep comes from, and almost every organization handles it badly. ⚠️ When someone changes role, new access is granted promptly because they need it to work — and old access is rarely removed, because removing it has no urgency and some risk of breaking something. Over a career, a long-tenured employee accumulates the union of every role they've held. ⚠️ The fix is that role change must trigger revocation review, not just grant — and ⚠️ defaulting to revoke-and-re-request is more effective than review-and-remove, because the default is what determines the outcome.
⚠️ Leaver risk is concentrated in what SSO doesn't cover: the account disabled in the directory is the easy part. ⚠️ Locally-provisioned SaaS, shared credentials, personal API keys, VPN certificates, physical access, and anything the person set up themselves are what actually persist. Immediate disable beats delete (preserves data and audit trail), transfer ownership of data and service accounts, and rotate any shared secret they knew. ⚠️ Contractors and third parties need an expiry date at creation — ⚠️ time-bounded by default, because nobody will remember to remove them.
§10. Access Review and Certification
⚠️ Periodic recertification: managers or resource owners attest that access is still needed. ⚠️ It is the standard control and it is widely performed badly.
⚠️ GOTCHA — rubber-stamping makes the control worthless while producing perfect evidence that it was performed. ⚠️ A manager presented with 400 entitlements named
APP_PRD_RW_GRP_04will approve all of them, and the audit artefact will look immaculate. ⚠️ What actually improves it: review by resource owner rather than line manager where the owner understands what the access does; plain-language entitlement descriptions; risk-based scoping — certify high-risk entitlements often and low-risk ones rarely, rather than everything annually; highlighting anomalies and outliers rather than presenting flat lists; ⚠️ and micro-certifications triggered by events (role change, unusual usage) rather than a calendar.
⚠️ Metrics worth tracking: orphaned accounts (no owner), dormant accounts (no sign-in in N days), entitlements never used (⚠️ research suggests identities commonly use a very small fraction of what they're granted, which is the argument for usage-informed rightsizing), exception count and age, time-to-deprovision.
§11. Segregation of Duties
⚠️ No single person should control an entire sensitive transaction end to end.
Classic pairs: create a vendor and approve payment to it; write code and deploy it to
production unreviewed; request access and approve it; administer a system and audit its
logs.
⚠️ SoD is a combinatorial problem, not a per-permission one — each permission is
fine; the combination is the violation, ⚠️ which is why it must be evaluated as a rule
set across effective access, and why it interacts badly with nested groups (§7 → itgov-directory-authentication-authorization-and-privileged-access).
⚠️ Compensating controls where SoD is impossible — and in small teams it frequently
is. Detective controls, mandatory review, and logging with independent oversight are
the honest answer for a five-person IT department, rather than pretending the separation
exists.
04 同仓库更多 Skills
white-paper-writing
Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks "how should I structure this" for a long-form document.
prose-technical-mechanics
Use when editing or writing prose at a technical/mechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.
prose-mechanics
Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate/Jamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix "AI-sounding" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.
narrative-structure
Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or "how should I structure this story/pitch/presentation" request.
legal-brief-writing
Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic/neurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.
journal-publishability-criteria
Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs/paper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.