From d560e9c2ffd379f8857ff613001b38164ea4b88e Mon Sep 17 00:00:00 2001 From: mlsmaycon Date: Fri, 16 Jan 2026 21:36:54 +0100 Subject: [PATCH] Add force approval docs --- src/components/NavigationDocs.jsx | 1 + .../endpoint-detection-and-response/crowdstrike-edr.mdx | 4 ++++ .../endpoint-detection-and-response/huntress-edr.mdx | 6 +++++- .../endpoint-detection-and-response/index.mdx | 7 +++++++ .../endpoint-detection-and-response/intune-mdm.mdx | 4 ++++ .../endpoint-detection-and-response/sentinelone-edr.mdx | 4 ++++ 6 files changed, 25 insertions(+), 1 deletion(-) diff --git a/src/components/NavigationDocs.jsx b/src/components/NavigationDocs.jsx index 602de690..f186cf6e 100644 --- a/src/components/NavigationDocs.jsx +++ b/src/components/NavigationDocs.jsx @@ -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' }, ] }, ] diff --git a/src/pages/manage/access-control/endpoint-detection-and-response/crowdstrike-edr.mdx b/src/pages/manage/access-control/endpoint-detection-and-response/crowdstrike-edr.mdx index 82ccd3db..c65e225d 100644 --- a/src/pages/manage/access-control/endpoint-detection-and-response/crowdstrike-edr.mdx +++ b/src/pages/manage/access-control/endpoint-detection-and-response/crowdstrike-edr.mdx @@ -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. + +## 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. diff --git a/src/pages/manage/access-control/endpoint-detection-and-response/huntress-edr.mdx b/src/pages/manage/access-control/endpoint-detection-and-response/huntress-edr.mdx index cf0f3a0b..8b116cd5 100644 --- a/src/pages/manage/access-control/endpoint-detection-and-response/huntress-edr.mdx +++ b/src/pages/manage/access-control/endpoint-detection-and-response/huntress-edr.mdx @@ -88,4 +88,8 @@ Treat the API credentials securely and store them safely. You will need both the 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. - \ No newline at end of file + + +## 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. \ No newline at end of file diff --git a/src/pages/manage/access-control/endpoint-detection-and-response/index.mdx b/src/pages/manage/access-control/endpoint-detection-and-response/index.mdx index e4fcd93d..bfe4eda4 100644 --- a/src/pages/manage/access-control/endpoint-detection-and-response/index.mdx +++ b/src/pages/manage/access-control/endpoint-detection-and-response/index.mdx @@ -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) diff --git a/src/pages/manage/access-control/endpoint-detection-and-response/intune-mdm.mdx b/src/pages/manage/access-control/endpoint-detection-and-response/intune-mdm.mdx index 08f72f59..08689d74 100644 --- a/src/pages/manage/access-control/endpoint-detection-and-response/intune-mdm.mdx +++ b/src/pages/manage/access-control/endpoint-detection-and-response/intune-mdm.mdx @@ -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. diff --git a/src/pages/manage/access-control/endpoint-detection-and-response/sentinelone-edr.mdx b/src/pages/manage/access-control/endpoint-detection-and-response/sentinelone-edr.mdx index c7c66141..ae40890b 100644 --- a/src/pages/manage/access-control/endpoint-detection-and-response/sentinelone-edr.mdx +++ b/src/pages/manage/access-control/endpoint-detection-and-response/sentinelone-edr.mdx @@ -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. +## 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. +