[GH-ISSUE #3803] Public IP Posture Check #7514

Open
opened 2026-08-05 01:13:18 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @BlueConfetti on GitHub (May 8, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3803

There's no reliable method for determining whether an agent is connected to a "trusted" network.

I'd love to see a public IP posture check, similar to the current peer IP check. Being able to specify a range/pool, ip, or ddns name would be amazing.

I had to create a custom service which runs a number of specific compliance checks, including a public IP check. I then use a process posture check against this service.
I had tried using the peer IP Allow/Block posture check – this wasn't a great solution, as some private subnet ranges were overlapping for remote agents.

Originally created by @BlueConfetti on GitHub (May 8, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3803 There's no reliable method for determining whether an agent is connected to a "trusted" network. I'd love to see a public IP posture check, similar to the current peer IP check. Being able to specify a range/pool, ip, or ddns name would be amazing. I had to create a custom service which runs a number of specific compliance checks, including a public IP check. I then use a process posture check against this service. I had tried using the peer IP Allow/Block posture check – this wasn't a great solution, as some private subnet ranges were overlapping for remote agents.
saavagebueno added the feature-request label 2026-08-05 01:13:18 -04:00
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#7514