Back to catalog
Static reviewDevelopment

Skill dossier

building-identity-governance-lifecycle-process

Source declaration

Design identity governance and lifecycle (IGA) programs on platforms like SailPoint, Saviynt, or Entra ID Governance, covering joiner-mover-leaver (JML) automation, role mining, access requests, periodic recertification, and orphaned-account remediation sourced from an HR feed. Use when automating cross-system JML provisioning, remediating former-employee access, or building lifecycle processes for SOX, HIPAA, or GDPR compliance.

The author's original description, preserved in English. It describes intent, not verified performance.

Design identity governance and lifecycle (IGA) programs on platforms like SailPoint, Saviynt, or Entra ID Governance, covering joiner-mover-leaver (JML) automation, role mining, access requests, periodic recertification, and orphaned-account remediation sourced from an HR feed. Use when automating cross-system JML provisioning, remediating former-employee access, or building lifecycle processes for SOX, HIPAA, or GDPR compliance.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Design identity governance and lifecycle (IGA) programs on platforms like SailPoint, Saviynt, or Entra ID Governance, covering joiner-mover-leaver (JML) automation, role mining, access requests, periodic recertification, and orphaned-account remediation sourced from an HR feed. Use when automating cross-system JML provisioning, remediating former-employee access, or building lifecycle processes for SOX, HIPAA, or GDPR compliance. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Building Identity Governance Lifecycle Process [Source statement; provisional, not tested. Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L60]
  • Workflow [Source statement; provisional, not tested. Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L82]
  • Step 1: Define Identity Lifecycle States and Transitions [Source statement; provisional, not tested. Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L84]
  • Step 2: Implement Authoritative Source Integration [Source statement; provisional, not tested. Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L191]
  • Step 3: Implement Role Mining and Birthright Access [Source statement; provisional, not tested. Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L303]
  • Step 4: Build Access Request and Approval Workflow [Source statement; provisional, not tested. Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L414]
  • Step 5: Implement Orphaned Account Detection and Remediation [Source statement; provisional, not tested. Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L541]
  • Scenario: Building JML Process for 10,000-Employee Organization [Source statement; provisional, not tested. Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L654]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L1-L58]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
48.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/building-identity-governance-lifecycle-process/LICENSEOther11 KB
skills/building-identity-governance-lifecycle-process/references/api-reference.mdReference2.1 KB
skills/building-identity-governance-lifecycle-process/scripts/agent.pyScript6.8 KB
skills/building-identity-governance-lifecycle-process/SKILL.mdInstruction28.4 KB

SKILL.md frontmatter

{
  "name": "building-identity-governance-lifecycle-process",
  "description": "Design identity governance and lifecycle (IGA) programs on platforms like SailPoint, Saviynt, or Entra ID Governance, covering joiner-mover-leaver (JML) automation, role mining, access requests, periodic recertification, and orphaned-account remediation sourced from an HR feed. Use when automating cross-system JML provisioning, remediating former-employee access, or building lifecycle processes for SOX, HIPAA, or GDPR compliance.",
  "domain": "cybersecurity",
  "subdomain": "identity-access-management",
  "tags": [
    "identity-governance",
    "lifecycle-management",
    "JML",
    "access-provisioning",
    "RBAC",
    "IGA"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_ai_rmf": [
    "GOVERN-1.1",
    "GOVERN-1.7",
    "MAP-1.1"
  ],
  "nist_csf": [
    "PR.AA-01",
    "PR.AA-02",
    "PR.AA-05",
    "PR.AA-06"
  ],
  "mitre_attack": [
    "T1098",
    "T1136",
    "T1078",
    "T1531",
    "T1087"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "positioning",
      "defense-impairment",
      "initial-access"
    ],
    "techniques": [
      {
        "id": "F1005",
        "name": "Account Manipulation",
        "tactic": "positioning",
        "source": "f3"
      },
      {
        "id": "F1005.002",
        "name": "Account Manipulation: Add Authorized User",
        "tactic": "positioning",
        "source": "f3"
      },
      {
        "id": "F1033",
        "name": "Insider Access Abuse",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1042",
        "name": "Reactivate Account",
        "tactic": "positioning",
        "source": "f3"
      },
      {
        "id": "F1006",
        "name": "Account Takeover",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Building Identity Governance Lifecycle Process

    Source-described action candidate under “Building Identity Governance Lifecycle Process”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  4. 04
    Action

    Step 1: Define Identity Lifecycle States and Transitions

    Source-described action candidate under “Step 1: Define Identity Lifecycle States and Transitions”; not verified execution.

  5. 05
    Input

    Step 2: Implement Authoritative Source Integration

    Source-described input candidate under “Step 2: Implement Authoritative Source Integration”; not verified execution.

  6. 06
    Action

    Step 3: Implement Role Mining and Birthright Access

    Source-described action candidate under “Step 3: Implement Role Mining and Birthright Access”; not verified execution.

Inspect all extracted workflow candidates (25 candidate steps)
  1. 07
    Action

    Step 4: Build Access Request and Approval Workflow

    Source-described action candidate under “Step 4: Build Access Request and Approval Workflow”; not verified execution.

  2. 08
    Action

    Step 5: Implement Orphaned Account Detection and Remediation

    Source-described action candidate under “Step 5: Implement Orphaned Account Detection and Remediation”; not verified execution.

  3. 09
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  4. 10
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  5. 11
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  6. 12
    Action

    Scenario: Building JML Process for 10,000-Employee Organization

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  7. 13
    Input

    Integrate Workday as authoritative source with daily delta sync to IGA platform

    Source-described input candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  8. 14
    Action

    Mine existing access patterns to define birthright roles for the top 20 job codes (covering 80% of employees)

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  9. 15
    Action

    Implement pre-hire provisioning triggered 7 days before start date for AD, email, and birthright apps

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  10. 16
    Action

    Build termination workflow that disables all access within 1 hour of HR status change

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  11. 17
    Action

    Create mover workflow that recalculates roles when job code or department changes

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  12. 18
    Action

    Deploy self-service access request portal with risk-based approval chains

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  13. 19
    Action

    Run orphaned account detection to identify and remediate the 2,300 existing orphans

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  14. 20
    Action

    Schedule quarterly access certifications to prevent access accumulation

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  15. 21
    Input

    Not defining a single authoritative source leads to conflicting identity data from multiple HR systems

    Source-described input candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  16. 22
    Action

    Mining roles without business validation creates technical roles that do not align with organizational structure

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  17. 23
    Action

    Automating termination without grace period for knowledge transfer frustrates business managers

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  18. 24
    Action

    Not handling contractor and vendor identities that exist outside the HR system

    Source-described action candidate under “Scenario: Building JML Process for 10,000-Employee Organization”; not verified execution.

  19. 25
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

42 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

27 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 27 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

13 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 13 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

2 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/building-identity-governance-lifecycle-process/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/building-identity-governance-lifecycle-process/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/building-identity-governance-lifecycle-process
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.