[GH-ISSUE #4537] Add Time-Based Posture Check for Peers #9690

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

Originally created by @Marcus1Pierce on GitHub (Sep 24, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4537

Is your feature request related to a problem? Please describe.
Currently, NetBird does not provide a way to enforce time-based access policies. Users who are granted access to certain peers or resources can connect at any time as long as they meet the posture requirements. In some environments, organizations need to limit access to sensitive resources during specific hours (e.g., business hours only).

Describe the solution you'd like
I would like NetBird to support time-based access control in policies. For example, administrators should be able to define that a group can only connect to specific peers between 8 AM and 5 PM. Outside these hours, access should automatically be denied.
This would allow more granular and flexible security enforcement that aligns with organizational working hours or compliance requirements.

Additional context
Example in an office environment:

  • Employees should only be able to access office resources (such as internal file servers, printers, or the company intranet) during office hours, from 8 AM to 5 PM.
  • Outside office hours, access to these peers should automatically be disabled to reduce the risk of unauthorized activity.
  • This ensures that access to office infrastructure is restricted to normal working hours, while still allowing administrators to maintain full control without manual intervention.
Originally created by @Marcus1Pierce on GitHub (Sep 24, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4537 **Is your feature request related to a problem? Please describe.** Currently, NetBird does not provide a way to enforce time-based access policies. Users who are granted access to certain peers or resources can connect at any time as long as they meet the posture requirements. In some environments, organizations need to limit access to sensitive resources during specific hours (e.g., business hours only). **Describe the solution you'd like** I would like NetBird to support time-based access control in policies. For example, administrators should be able to define that a group can only connect to specific peers between 8 AM and 5 PM. Outside these hours, access should automatically be denied. This would allow more granular and flexible security enforcement that aligns with organizational working hours or compliance requirements. **Additional context** Example in an office environment: - Employees should only be able to access office resources (such as internal file servers, printers, or the company intranet) during office hours, from 8 AM to 5 PM. - Outside office hours, access to these peers should automatically be disabled to reduce the risk of unauthorized activity. - This ensures that access to office infrastructure is restricted to normal working hours, while still allowing administrators to maintain full control without manual intervention.
saavagebueno added the feature-request label 2026-08-05 01:23:05 -04:00
Author
Owner

@NABarnes commented on GitHub (Oct 3, 2025):

Came here to ask for exactly this - it would be very useful for several of our customers.

<!-- gh-comment-id:3364326250 --> @NABarnes commented on GitHub (Oct 3, 2025): Came here to ask for exactly this - it would be very useful for several of our customers.
Author
Owner

@sehari24jam commented on GitHub (Apr 27, 2026):

Several scenarios:

  • allowed from 8am to 5pm daily, UTC
  • allowed from 8am to 5pm on weekdays (Monday to Friday), Europe/Berlin
  • allowed from January 1st 2026 to January 31st 2026, -06:00
  • denied on December 25th every year, +06:00
  • denied on weekend (Saturday and Sunday), local client time

It might techically resemble cron-alike, with timezone and negate option.

<!-- gh-comment-id:4332235666 --> @sehari24jam commented on GitHub (Apr 27, 2026): Several scenarios: - allowed from 8am to 5pm daily, UTC - allowed from 8am to 5pm on weekdays (Monday to Friday), Europe/Berlin - allowed from January 1st 2026 to January 31st 2026, -06:00 - denied on December 25th every year, +06:00 - denied on weekend (Saturday and Sunday), local client time It might techically resemble cron-alike, with timezone and negate option.
Author
Owner

@USBAkimbo commented on GitHub (Jun 3, 2026):

Bumping this - I'm granting users who auth with SSO access to certain resources

Some users need access to an environment but only on a temporary basis, so time-based access for this would be fantastic

I'd add that expiration for group assignment would also be nice as well

For example - someone needs access to environment X for the next 3 days for a project - assignment can be set to expire at the end of the 3rd day

<!-- gh-comment-id:4613597451 --> @USBAkimbo commented on GitHub (Jun 3, 2026): Bumping this - I'm granting users who auth with SSO access to certain resources Some users need access to an environment but only on a temporary basis, so time-based access for this would be fantastic I'd add that expiration for group assignment would also be nice as well For example - someone needs access to environment X for the next 3 days for a project - assignment can be set to expire at the end of the 3rd day
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#9690