[GH-ISSUE #5314] Just-in-Time (JIT) Access Policies for Granular, Time-Bound Control #11127

Open
opened 2026-08-05 01:28:36 -04:00 by saavagebueno · 3 comments
Owner

Originally created by @SonNgo2211 on GitHub (Feb 13, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5314

Is your feature request related to a problem? Please describe.
I'm frustrated when managing user access permissions in a Zero Trust environment because I have to manually revoke access after temporary tasks (like hotfixes or vendor maintenance) are completed. Currently, policies are static, which means if I forget to revoke permissions, those users retain standing privileges, creating a significant security risk if their accounts are compromised.

Describe the solution you'd like
I would like NetBird to implement Just-in-Time (JIT) Access Policies. This feature should allow administrators to define access rules that automatically expire after a specific duration. Ideally, this would include:

  • A "Time-to-Live (TTL)" or "Expiration Time" setting within the existing Policy engine.
  • A workflow to approve on-demand access requests that are time-bound.

Describe alternatives you've considered
Currently, the only alternative is manually creating a policy, monitoring the task, and manually deleting or disabling the policy afterward. This is time-consuming, prone to human error, and does not scale well with many vendors or emergency situations.

Similar functionality exists in other mesh VPN solutions (like Tailscale's capabilities). Implementing this would greatly enhance NetBird's security posture and make it more attractive for enterprise use cases where strict compliance (SOC2/ISO27001) regarding privileged access is required.

Originally created by @SonNgo2211 on GitHub (Feb 13, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5314 **Is your feature request related to a problem? Please describe.** I'm frustrated when managing user access permissions in a Zero Trust environment because I have to manually revoke access after temporary tasks (like hotfixes or vendor maintenance) are completed. Currently, policies are static, which means if I forget to revoke permissions, those users retain standing privileges, creating a significant security risk if their accounts are compromised. **Describe the solution you'd like** I would like NetBird to implement Just-in-Time (JIT) Access Policies. This feature should allow administrators to define access rules that automatically expire after a specific duration. Ideally, this would include: - A "Time-to-Live (TTL)" or "Expiration Time" setting within the existing Policy engine. - A workflow to approve on-demand access requests that are time-bound. **Describe alternatives you've considered** Currently, the only alternative is manually creating a policy, monitoring the task, and manually deleting or disabling the policy afterward. This is time-consuming, prone to human error, and does not scale well with many vendors or emergency situations. Similar functionality exists in other mesh VPN solutions (like Tailscale's capabilities). Implementing this would greatly enhance NetBird's security posture and make it more attractive for enterprise use cases where strict compliance (SOC2/ISO27001) regarding privileged access is required.
saavagebueno added the feature-request label 2026-08-05 01:28:36 -04:00
Author
Owner

@alexschomb commented on GitHub (Feb 22, 2026):

FYI this has been added to the last release of gravitl/netmaker as beta functionality: https://github.com/gravitl/netmaker/commit/c2423bf20b5590ceb2aac91ada8a9865fab848cd

<!-- gh-comment-id:3941358158 --> @alexschomb commented on GitHub (Feb 22, 2026): FYI this has been added to the [last release](https://github.com/gravitl/netmaker/releases/tag/v1.5.0) of [gravitl/netmaker](https://github.com/gravitl/netmaker) as beta functionality: [https://github.com/gravitl/netmaker/commit/c2423bf20b5590ceb2aac91ada8a9865fab848cd](https://github.com/gravitl/netmaker/commit/c2423bf20b5590ceb2aac91ada8a9865fab848cd)
Author
Owner

@SonNgo2211 commented on GitHub (Feb 22, 2026):

FYI this has been added to the last release of gravitl/netmaker as beta functionality: gravitl/netmaker@c2423bf

Thanks @alexschomb. I'd prefer to stay with NetBird, but if they don't support JIT soon, I'll definitely have to switch to Netmaker/Tailscale for that specific control.

<!-- gh-comment-id:3941389806 --> @SonNgo2211 commented on GitHub (Feb 22, 2026): > FYI this has been added to the [last release](https://github.com/gravitl/netmaker/releases/tag/v1.5.0) of [gravitl/netmaker](https://github.com/gravitl/netmaker) as beta functionality: [gravitl/netmaker@c2423bf](https://github.com/gravitl/netmaker/commit/c2423bf20b5590ceb2aac91ada8a9865fab848cd) Thanks @alexschomb. I'd prefer to stay with NetBird, but if they don't support JIT soon, I'll definitely have to switch to Netmaker/Tailscale for that specific control.
Author
Owner

@alexschomb commented on GitHub (Feb 22, 2026):

FYI this has been added to the last release of gravitl/netmaker as beta functionality: gravitl/netmaker@c2423bf

Thanks @alexschomb. I'd prefer to stay with NetBird, but if they don't support JIT soon, I'll definitely have to switch to Netmaker/Tailscale for that specific control.

Agreed. Another downside is that this is Netmaker Enterprise only.

<!-- gh-comment-id:3941423664 --> @alexschomb commented on GitHub (Feb 22, 2026): > > FYI this has been added to the [last release](https://github.com/gravitl/netmaker/releases/tag/v1.5.0) of [gravitl/netmaker](https://github.com/gravitl/netmaker) as beta functionality: [gravitl/netmaker@c2423bf](https://github.com/gravitl/netmaker/commit/c2423bf20b5590ceb2aac91ada8a9865fab848cd) > > Thanks [@alexschomb](https://github.com/alexschomb). I'd prefer to stay with NetBird, but if they don't support JIT soon, I'll definitely have to switch to Netmaker/Tailscale for that specific control. Agreed. Another downside is that this is Netmaker Enterprise only.
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11127