[GH-ISSUE #4771] Add time/calendar based availability to networks or connections #9804

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

Originally created by @enttdede on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4771

Is your feature request related to a problem? Please describe.
A topic which is most often discarded or never really considered in regards to ACL is time dependent availability.
Not a "real" problem, since I am able to solve it via router configs, but it would be another layer of security and create more transparency for the users.

Describe the solution you'd like
The ability to define when a network or connection is available.
E.g. from mondays to fridays from 09:00 - 17:00. With a gui notification to the users of said connection.

Describe alternatives you've considered
It is possible to define availability of specific connections via cron jobs on servers and firewalls, but it is not transparent to users, since another communication channel is needed for such decisions.

Additional context
A simple way to minimize the attack vector space for organizations — why should the average user exfil gigs of data at 02:30 am? — and also to enforce work-life-balance rules. On one hand another layer of security and also creating the possibility of notifying users of specific networks of scheduled down-times.
In a future step one could even import a calendar with time-slots, so the user just need to define it via an .ics file.

P.S.: I really like em dashes, I have not written this request with AI. And yes, I know in regards to i18n and l10n it could be a hairy topic.

Originally created by @enttdede on GitHub (Nov 10, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4771 **Is your feature request related to a problem? Please describe.** A topic which is most often discarded or never really considered in regards to ACL is time dependent availability. Not a "real" problem, since I am able to solve it via router configs, but it would be another layer of security and create more transparency for the users. **Describe the solution you'd like** The ability to define when a network or connection is available. E.g. from mondays to fridays from 09:00 - 17:00. With a gui notification to the users of said connection. **Describe alternatives you've considered** It is possible to define availability of specific connections via cron jobs on servers and firewalls, but it is not transparent to users, since another communication channel is needed for such decisions. **Additional context** A simple way to minimize the attack vector space for organizations — why should the average user exfil gigs of data at 02:30 am? — and also to enforce work-life-balance rules. On one hand another layer of security and also creating the possibility of notifying users of specific networks of scheduled down-times. In a future step one could even import a calendar with time-slots, so the user just need to define it via an .ics file. **P.S.:** I really like em dashes, I have not written this request with AI. And yes, I know in regards to **i18n** and **l10n** it could be a hairy topic.
saavagebueno added the feature-request label 2026-08-05 01:23:31 -04:00
Author
Owner

@1nerdyguy commented on GitHub (Nov 12, 2025):

I haven't heard of many people doing this, but I like the idea.

<!-- gh-comment-id:3521903469 --> @1nerdyguy commented on GitHub (Nov 12, 2025): I haven't heard of many people doing this, but I like the idea.
Author
Owner

@enttdede commented on GitHub (Nov 13, 2025):

@1nerdyguy welcome to the club, we are dozens!
In my experience a lot people are always surprised by the idea of making systems not be available 24/7. It breaks with the accepted believe, that 100% uptime is equal to 24 hours availability.
And in regards to security I had fun exchanges with pentesters who have been annoyed with gaining persistence on machines, but they didn't not know, that they were ephemeral (running just for a few hours max per day). So the next day they had to replay their whole attack chain to regain access, which in itself makes it more likely to discovered because of suspicious network activity.

<!-- gh-comment-id:3526871342 --> @enttdede commented on GitHub (Nov 13, 2025): @1nerdyguy welcome to the club, we are dozens! In my experience a lot people are always surprised by the idea of making systems not be available 24/7. It breaks with the accepted believe, that 100% uptime is equal to 24 hours availability. And in regards to security I had fun exchanges with pentesters who have been annoyed with gaining persistence on machines, but they didn't not know, that they were ephemeral (running just for a few hours max per day). So the next day they had to replay their whole attack chain to regain access, which in itself makes it more likely to discovered because of suspicious network activity.
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#9804