-
Notifications
You must be signed in to change notification settings - Fork 18
Open
Labels
area:identityIdentity, RBAC, Entra ID, access controlIdentity, RBAC, Entra ID, access controlpriority:p0Highest priorityHighest prioritytype:featureFeature work itemFeature work item
Description
Parent: #810
✨ FEATURE — Identity Foundation (Landing Zone)
Parent Epic
🎯 EPIC — Dev Box–Ready Landing Zone (FOUNDATION)
Milestone
M0 — Platform Readiness & Guardrails Locked
📝 Feature Description
Establish the identity and access foundations required by a Dev Box–Ready Landing Zone, including
tenant readiness assumptions, group-based access strategy, privileged access separation, and
break-glass access requirements.
❓ Problem Statement
Without a clear identity foundation, platform deployments rely on ad-hoc permissions and unsafe RBAC
practices, which later block Dev Box adoption and trigger security/governance pushback.
💡 Proposed Solution
Define and document:
- Entra ID tenant readiness assumptions
- Group-based access model (no per-user RBAC)
- Privileged access boundaries (admins vs operators)
- Break-glass access requirements and usage guidance
🔀 Alternative Solutions
- Per-user RBAC assignments
- Broad Owner/Contributor usage
🔧 Dev Box Component
- Identity & Access
- Documentation
👤 Use Case
Security and platform teams agree on identity assumptions before any platform or Dev Box resources are deployed.
✨ Expected Benefits
- Clear separation of duties
- Reduced security risk
- Fewer access blockers downstream
Acceptance Criteria
- Identity assumptions documented
- Group-based access model defined
- Privileged access boundaries clear
- Break-glass approach documented
Dependencies
None
Definition of Done
- Identity foundation documented and approved
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area:identityIdentity, RBAC, Entra ID, access controlIdentity, RBAC, Entra ID, access controlpriority:p0Highest priorityHighest prioritytype:featureFeature work itemFeature work item