diff --git a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/edr-integrations-back.png b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/edr-integrations-back.png
new file mode 100644
index 00000000..8f9785af
Binary files /dev/null and b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/edr-integrations-back.png differ
diff --git a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/edr-integrations.png b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/edr-integrations.png
index 8f9785af..e19a4788 100644
Binary files a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/edr-integrations.png and b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/edr-integrations.png differ
diff --git a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/compliance-config.png b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/compliance-config.png
new file mode 100644
index 00000000..74166d28
Binary files /dev/null and b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/compliance-config.png differ
diff --git a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/console-config.png b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/console-config.png
new file mode 100644
index 00000000..e45f4449
Binary files /dev/null and b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/console-config.png differ
diff --git a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/edr-approval-required.png b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/edr-approval-required.png
new file mode 100644
index 00000000..37b80a18
Binary files /dev/null and b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/edr-approval-required.png differ
diff --git a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/getting-started.png b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/getting-started.png
new file mode 100644
index 00000000..27f5b016
Binary files /dev/null and b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/getting-started.png differ
diff --git a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/group-config.png b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/group-config.png
new file mode 100644
index 00000000..e507e8ab
Binary files /dev/null and b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/group-config.png differ
diff --git a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/service-user.png b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/service-user.png
new file mode 100644
index 00000000..054ab5ac
Binary files /dev/null and b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/service-user.png differ
diff --git a/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/sync-config.png b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/sync-config.png
new file mode 100644
index 00000000..f7706b9c
Binary files /dev/null and b/public/docs-static/img/how-to-guides/endpoint-detection-and-response/sentinelone/sync-config.png differ
diff --git a/src/components/NavigationDocs.jsx b/src/components/NavigationDocs.jsx
index 729640ed..fad3975c 100644
--- a/src/components/NavigationDocs.jsx
+++ b/src/components/NavigationDocs.jsx
@@ -111,6 +111,7 @@ export const docsNavigation = [
links: [
{ title: 'CrowdStrike Falcon', href: '/how-to/crowdstrike-edr' },
{ title: 'Microsoft Intune', href: '/how-to/intune-mdm' },
+ { title: 'SentinelOne Singularity', href: '/how-to/sentinelone-edr' },
]
},
diff --git a/src/pages/how-to/endpoint-detection-and-response.mdx b/src/pages/how-to/endpoint-detection-and-response.mdx
index cfd909d8..42291dc6 100644
--- a/src/pages/how-to/endpoint-detection-and-response.mdx
+++ b/src/pages/how-to/endpoint-detection-and-response.mdx
@@ -37,3 +37,4 @@ NetBird integrates with the following EDR platforms:
* [CrowdStrike Falcon](/how-to/crowdstrike-edr)
* [Microsoft Intune](/how-to/intune-mdm)
+* [SentinelOne Singularity](/how-to/sentinelone-edr)
diff --git a/src/pages/how-to/sentinelone-edr.mdx b/src/pages/how-to/sentinelone-edr.mdx
new file mode 100644
index 00000000..833eb94d
--- /dev/null
+++ b/src/pages/how-to/sentinelone-edr.mdx
@@ -0,0 +1,110 @@
+# Restrict Network Access with SentinelOne Singularity™
+
+[SentinelOne Singularity](https://www.sentinelone.com/platform/) is an autonomous cybersecurity platform that provides
+comprehensive endpoint protection, detection, and response capabilities. The SentinelOne agent runs on your devices (endpoints),
+collecting and analyzing endpoint data to detect and respond to threats in real-time. The agent's presence on endpoints and the
+security data it collects can be utilized to enforce access policies and limit network access according to the "health" status
+of the endpoints.
+
+The integration of NetBird with SentinelOne provides organizations with robust security controls that allow
+only IT-managed devices running SentinelOne to access the network. Additionally, the integration uses SentinelOne's threat
+detection capabilities, enabling administrators to further limit network access based on the security posture of each device.
+
+SentinelOne's endpoint protection provides real-time threat detection and automated response capabilities. By integrating with
+SentinelOne Singularity, NetBird can ensure that only devices with active security monitoring and protection can access the network.
+
+In this guide, we will walk you through the configuration steps to integrate SentinelOne Singularity with NetBird and use
+endpoint security status to control network access for devices that meet your security requirements.
+
+## Prerequisites
+
+Before you start creating and configuring a SentinelOne integration, ensure that you have the following:
+- A SentinelOne account with the permissions to create and manage API tokens.
+ If you don't have the required permissions, ask your SentinelOne administrator to grant them to you.
+
+## Create a SentinelOne API Token
+
+- Navigate to your SentinelOne Management Console
+- Go to **Settings** » **Users** » **Service Users**
+- Click **Create Service User**
+- Fill in the form:
+ - **Name**: `NetBird Integration`
+ - **Description**: `API token for NetBird EDR integration` (optional)
+ - **Expiration Date**: Set your preferred expiration date
+- Click **Next**
+- Select Site and set **Scope** to **Viewer**
+- Click **Create User**
+- Copy the generated API token immediately (it will only be displayed once)
+- Note your SentinelOne console URL from your browser's address bar (e.g., `https://your-tenant.sentinelone.net`)
+
+
+Treat the API token securely and store it safely. You will need both the console URL and API token for the NetBird integration configuration.
+
+
+## Configure a SentinelOne Integration in NetBird
+
+- Navigate to the [Integrations » EDR](https://app.netbird.io/integrations?tab=edr) tab in the NetBird dashboard
+- Click **Connect SentinelOne** to start the configuration wizard
+
+ 
+
+- Click the **Get Started** button to initiate the integration process
+- Enter your SentinelOne console URL (e.g., `https://your-tenant.sentinelone.net`) and click **Continue**
+
+
+ 
+
+
+- Enter the API token you created in the previous step and click **Continue** to verify the connection
+
+
+ 
+
+
+- Select the **groups** you want to apply the integration to and click **Connect**
+
+
+ 
+
+
+
+
+ The EDR check will apply only to peers in the selected groups and will require a running SentinelOne agent.
+ You can also use groups [synchronized from your Identity Provider (IdP)](/how-to/idp-sync).
+
+
+- Configure the compliance criteria that devices must meet to access your network. These security requirements ensure only healthy, properly configured devices can connect. Select the criteria that align with your organization's security policies:
+ - **Allowed Active Threats**: Maximum number of active threats allowed on a device. Default is set to `0` to block devices with any active threats.
+ - **Disk Encryption**: Requires disk encryption to be enabled on the device.
+ - **Firewall**: Requires the device firewall to be enabled and active.
+ - **Block Infected Devices**: Prevents network access for devices with confirmed active infections.
+ - **Network Connectivity**: Requires active network connection between the device and SentinelOne services.
+ - **Active Status**: Requires the SentinelOne agent to be active and reporting. The agent must be in operational state (not disabled, corrupted, or experiencing errors).
+ - **Latest Agent Version**: Requires the SentinelOne agent to be running the most current version.
+
+
+ 
+
+
+
+- Configure the **SentinelOne Sync Window** (default is 24 hours). This setting determines which devices NetBird will consider for network access based on their recent activity in SentinelOne. Only devices that have been active and reporting to SentinelOne within this time window will be synchronized. These devices must then also meet the configured compliance criteria to gain network access.
+
+
+ 
+
+
+- Click **Connect** to complete the integration setup
+
+- Only peers that have the SentinelOne agent installed and meet all the configured compliance criteria will be granted access to the network.
+ Peers without the SentinelOne agent or those that don't meet the compliance requirements will appear with an `Approval required` mark in the peers list and won't be able to access
+ the network until they have the agent installed and satisfy all the specified security requirements.
+
+
+ 
+
+
+
+
+ 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.
+
+