Add force approval docs

This commit is contained in:
mlsmaycon
2026-01-16 21:36:54 +01:00
parent 2900964bd6
commit d560e9c2ff
6 changed files with 25 additions and 1 deletions

View File

@@ -126,6 +126,7 @@ export const docsNavigation = [
{ title: 'Microsoft Intune', href: '/manage/access-control/endpoint-detection-and-response/intune-mdm' },
{ title: 'SentinelOne Singularity', href: '/manage/access-control/endpoint-detection-and-response/sentinelone-edr' },
{ title: 'Huntress', href: '/manage/access-control/endpoint-detection-and-response/huntress-edr' },
{ title: 'Force Approval', href: '/manage/access-control/endpoint-detection-and-response/force-approval' },
]
},
]

View File

@@ -86,3 +86,7 @@ with a `Approval required` mark in the peers list and won't be able to access th
If you install the CrowdStrike agent on a peer after it joined the network, you will need to disconnect and reconnect
this peer for the `Approval required` mark to disappear.
</Note>
## Managing Exceptions
If you need to grant network access to a peer that fails CrowdStrike compliance checks, you can use the force approval feature. See [Force Approve EDR-Rejected Peers](/manage/access-control/endpoint-detection-and-response/force-approval) for details.

View File

@@ -88,4 +88,8 @@ Treat the API credentials securely and store them safely. You will need both the
<Note>
NetBird matches the Huntress agent to the peer using the Serial Number of the device. You must ensure that each of your devices has a unique serial number.
</Note>
</Note>
## Managing Exceptions
If you need to grant network access to a peer that fails Huntress compliance checks, you can use the force approval feature. See [Force Approve EDR-Rejected Peers](/manage/access-control/endpoint-detection-and-response/force-approval) for details.

View File

@@ -36,5 +36,12 @@ the checks to apply.
NetBird integrates with the following EDR platforms:
* [CrowdStrike Falcon](/manage/access-control/endpoint-detection-and-response/crowdstrike-edr)
* [Huntress](/manage/access-control/endpoint-detection-and-response/huntress-edr)
* [Microsoft Intune](/manage/access-control/endpoint-detection-and-response/intune-mdm)
* [SentinelOne Singularity](/manage/access-control/endpoint-detection-and-response/sentinelone-edr)
## Managing Exceptions
In some cases, you may need to grant network access to devices that don't meet EDR compliance requirements. NetBird provides a force approval mechanism for these scenarios:
* [Force Approve EDR-Rejected Peers](/manage/access-control/endpoint-detection-and-response/force-approval)

View File

@@ -163,3 +163,7 @@ with a `Approval required` mark in the peers list and won't be able to access th
- Devices with a Intune compliance state of `Compliant` or `InGracePeriod` are accepted; all other states are rejected.
- New devices or those that recently achieved compliance may need to be disconnected and reconnected to NetBird to propagate updated status.
- NetBird regularly synchronizes with Intune every few minutes, so changes in compliance can take some time to reflect on the dashboard.
## Managing Exceptions
If you need to grant network access to a peer that fails Intune compliance checks, you can use the force approval feature. See [Force Approve EDR-Rejected Peers](/manage/access-control/endpoint-detection-and-response/force-approval) for details.

View File

@@ -110,3 +110,7 @@ Treat the API token securely and store it safely. You will need both the console
NetBird matches the SentinelOne agent to the peer using the Serial Number of the device. You must ensure that each of your devices has a unique serial number.
</Note>
## Managing Exceptions
If you need to grant network access to a peer that fails SentinelOne compliance checks, you can use the force approval feature. See [Force Approve EDR-Rejected Peers](/manage/access-control/endpoint-detection-and-response/force-approval) for details.