♻️
Identity lifecycle
Joiner, Mover and Leaver runbooks driven by authoritative employment attributes, approvals, target validation and exception handling.
IAM Support Operations &
Identity Governance
I designed and deployed a fictional, sanitized identity-operations environment demonstrating JML governance, risk assessment, access reviews, segregation of duties, privileged-access controls, exception handling, human escalation and audit-ready evidence.
5Incident case studies
3Lifecycle runbooks
31Fictional assignments reviewed
7Regression tests
Capabilities
What this lab demonstrates
Operational IAM work is more than creating accounts. The lab shows how access is validated, provisioned, investigated, reviewed and removed with evidence at every stage.
🧭
Incident troubleshooting
Structured investigation across account state, authentication, policy, authorization, synchronization, provisioning and the target application.
🛡️
Access governance
Role and entitlement mapping, segregation-of-duties controls, recurring access reviews, remediation and target-state confirmation.
⚠
Risk Assessment
Business impact, identity state, entitlement sensitivity, approval and target exposure drive P1-P4 handling.
✓
Access Reviews
A fictional campaign evaluates 31 assignments with documented approval, revocation, time-limit and investigation outcomes.
🔑
Privileged Access
Privileged and emergency requests leave the standard path for elevated human approval, ownership and removal evidence.
↗
Exception Handling
Out-of-role, conflicting, orphaned and failed requests receive named owners, due dates or expiration, and target confirmation.
▤
Audit Evidence
Requests, approvals, timestamps, correlation IDs, entitlement state, actions and closure decisions remain reviewable.
⚙
Production Readiness
Architecture, logging, monitoring, failure handling, backup, recovery, security, CI, expected load, limitations and runbooks are explicit.
Support method
Evidence before escalation
A repeatable decision path keeps access restoration safe, reduces handoff time and preserves an audit trail.
01 · ValidateIdentity, requestor and approval
02 · CaptureError, time, resource and impact
03 · InspectAccount, authentication and policy
04 · CompareRoles, entitlements and target state
05 · ActResolve or contain within authority
06 · ConfirmValidate, document and prevent recurrence
Incident laboratory
Five realistic IAM cases
Each case includes business impact, validation, sanitized evidence, root cause, resolution, closure criteria and preventive action.
IAM-001
Repeated Active Directory lockout
Traced recurring failures to stale credentials stored in a mobile email profile.
AUTHENTICATIONIAM-002
Completed request, missing entitlement
Compared governance and target state to identify a provisioning connector timeout.
PROVISIONINGIAM-003
Conditional Access denial
Verified that compliant-device policy correctly blocked a sensitive application.
CLOUD IDENTITYIAM-004
Failed leaver deprovisioning
Contained an active connected account after the application connector failed.
P1 SECURITYIAM-005
Mover access conflict
Removed sensitive Finance access retained after a department transfer.
GOVERNANCEOperational identity governance
Aggregation and account correlation
Entitlement catalog and access requests
Provisioning transaction investigation
Orphan-account handling
Certification decisions and remediation
Evidence recruiters can inspect
Architecture and trust boundaries
Joiner-Mover-Leaver runbooks
Role and entitlement matrix
Access review and remediation report
Safety-first PowerShell examples
Operate the IAM support simulator.
Run lifecycle workflows, approve access, troubleshoot incidents, conduct reviews and inspect evidence using a safe fictional dataset.