[GH-ISSUE #2210] Assign Posture Check for a specific peer #4631

Closed
opened 2026-08-05 00:58:50 -04:00 by saavagebueno · 1 comment
Owner

Originally created by @papoe on GitHub (Jun 27, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2210

Currently, it is only possible to assign a posture check to both peers in a policy configuration. For example, if you configure a "Process Posture Check," both peers need to run the same process. Therefore, you cannot set up a policy where, for example, Peer A runs a process and Peer B only sends sensor data to Peer A for this process.

There should be the possibility to assign posture checks to specific peers, instead of requiring both peers to fulfill the posture check.

Originally created by @papoe on GitHub (Jun 27, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2210 Currently, it is only possible to assign a posture check to both peers in a policy configuration. For example, if you configure a "Process Posture Check," both peers need to run the same process. Therefore, you cannot set up a policy where, for example, Peer A runs a process and Peer B only sends sensor data to Peer A for this process. There should be the possibility to assign posture checks to specific peers, instead of requiring both peers to fulfill the posture check.
saavagebueno added the feature-request label 2026-08-05 00:58:50 -04:00
Author
Owner

@bcmmbaga commented on GitHub (Jun 28, 2024):

Hello @papoe , Currently, the posture checks are only applied to the peers of the policy source group. We will update the docs and dashboard to make this clear.

For example, you could create a policy with peer B (as part of the source group) and peer A (as part of the destination group) and apply the posture check. This will only require peer B to fulfill the check requirement before connecting to peer A.

<!-- gh-comment-id:2196231998 --> @bcmmbaga commented on GitHub (Jun 28, 2024): Hello @papoe , Currently, the posture checks are only applied to the peers of the policy source group. We will update the docs and dashboard to make this clear. For example, you could create a policy with peer B (as part of the source group) and peer A (as part of the destination group) and apply the posture check. This will only require peer B to fulfill the check requirement before connecting to peer A.
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#4631