implementing-just-in-time-access-provisioning
Implement Just-In-Time (JIT) access provisioning to eliminate standing privileges by granting temporary, time-bound access only when needed. This skill covers JIT architecture design, approval workflo
What this skill does
# Implementing Just-In-Time Access Provisioning ## Overview Implement Just-In-Time (JIT) access provisioning to eliminate standing privileges by granting temporary, time-bound access only when needed. This skill covers JIT architecture design, approval workflows, automatic expiration, integration with PAM and IGA platforms, and alignment with zero trust principles. ## When to Use - When deploying or configuring implementing just in time access provisioning capabilities in your environment - When establishing security controls aligned to compliance requirements - When building or improving security architecture for this domain - When conducting security assessments that require this implementation ## Prerequisites - Familiarity with identity access management concepts and tools - Access to a test or lab environment for safe execution - Python 3.8+ with required dependencies installed - Appropriate authorization for any testing activities ## Objectives - Design JIT access request and approval workflows - Implement time-bound access grants with automatic expiration - Configure risk-based approval routing (auto-approve low-risk, multi-approval for high-risk) - Integrate JIT with PAM for privileged access elevation - Monitor and audit all JIT access grants and usage - Reduce attack surface by eliminating standing privileges ## Key Concepts ### JIT Access Models 1. **Broker and Remove**: Grant access through approval, auto-remove after time window 2. **Elevation on Demand**: User has base access, elevates to privileged upon request 3. **Account Creation/Deletion**: Temporary account created, destroyed after use 4. **Group Membership Toggle**: Add to privileged group temporarily, auto-remove ### Zero Standing Privilege (ZSP) Principle - No user has permanent privileged access - All privileged access requires explicit request with business justification - Access automatically expires after defined time window - All access events logged and auditable ## Workflow ### Step 1: Identify Eligible Access Types - Privileged admin access (domain admin, root, DBA) - Production environment access - Sensitive data access (PII, financial, healthcare) - Emergency/break-glass access - Third-party vendor access ### Step 2: Design Approval Workflows - Self-service request portal with justification requirement - Auto-approve for pre-authorized low-risk access (< 1 hour) - Single approver for medium-risk (manager or resource owner) - Dual approval for high-risk (manager + security team) - Emergency bypass with post-facto review ### Step 3: Implement Time-Bound Access - Configure maximum access duration per resource type - Implement countdown timer with extension request capability - Auto-revoke at expiration regardless of session state - Grace period notification (15 min before expiry) - Automatic session termination on access expiry ### Step 4: Integration Architecture - Connect to IAM/IGA platform for provisioning/de-provisioning - Integrate with PAM for privileged credential checkout - Connect to ITSM for ticket correlation - Forward events to SIEM for monitoring - API integration for programmatic access requests ### Step 5: Monitoring and Compliance - Log all JIT requests, approvals, grants, and revocations - Alert on access used beyond approved scope - Track access not used (request but never connected) - Measure mean time to access (request to grant) - Report on access patterns for baseline optimization ## Security Controls | Control | NIST 800-53 | Description | |---------|-------------|-------------| | Temporary Access | AC-2(2) | Automated temporary account management | | Least Privilege | AC-6 | Time-bound minimum access | | Access Enforcement | AC-3 | Automated access grant/revoke | | Audit | AU-3 | Complete JIT access audit trail | | Risk Assessment | RA-3 | Risk-based approval routing | ## Common Pitfalls - Setting time windows too long, negating JIT benefits - Not implementing automatic revocation at expiration - Complex approval workflows causing access delays for legitimate needs - Not providing emergency bypass for critical incidents - Failing to audit approved but unused JIT access ## Verification - [ ] JIT request workflow functional end-to-end - [ ] Access automatically revoked at expiration - [ ] Approval routing correct for all risk levels - [ ] Emergency access bypass works with post-review - [ ] All JIT events logged to SIEM - [ ] Standing privileges reduced by measurable percentage - [ ] Mean time to access meets business SLA
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.