> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/lifecycle-management/jitpbac.md).

# JITPBAC

**What is JITPBAC?**

JITPBAC (Just-in-Time Purpose-Based Access Control) is a dynamic and purpose-driven access control framework designed to enhance security and operational efficiency by provisioning access to identities in Cloud, SaaS applications only when it is explicitly required and for a defined period of time. The model reduces the exposure of sensitive resources to potential threats, particularly when credentials are compromised, by adhering to the principle of least privilege.

**Key Features of JITPBAC**

1. **Default Deny Policy (Zero Trust)**: Identities have no access by default. Access is provisioned only through assigned Purposes, ensuring strict access control.
2. **Purpose-Centric Access**: Access is organized under **Purposes**, which define specific combinations of users, resources, and temporal access windows.
3. **Eligibility and Approval**: Identity owners must request access to a Purpose and provide supporting details (e.g., duration, time of use). Approval from a risk manager is required to ensure compliance with organizational policies.
4. **Automated Provisioning and De-provisioning**: Access is automatically provisioned at the start of a defined time window and de-provisioned at its end. Notifications are sent before de-provisioning to allow extensions if permitted.
5. **Constraints for Enhanced Security**: Constraints define rules that limit or restrict access based on organizational policies or specific conditions. Purposes and Constraints are interdependent to prevent violations.

{% embed url="<https://vimeo.com/1151693855>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/lifecycle-management/jitpbac.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
