{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/", "item": { "id": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/", "slug": "keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data", "url": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data.md", "json": "https://update.dsesecurity.com/api/v1/posts/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/" }, "title": "Keep VPN identity enrichment on sensor v2 and validate RADIUS accounting data", "summary": "Use Defender for Identity VPN integration in Microsoft Defender to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "checklist", "name": "Checklist" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "identity-cloud", "label": "Identity & cloud", "alt": "Governed cloud identity system with connected service and lifecycle nodes.", "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "microsoft-365-identity", "name": "Microsoft 365 & Identity", "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-08-27T12:12:44+00:00", "modified_at": "2026-08-27T13:04:10+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 511, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Defender for Identity VPN integration in Microsoft Defender", "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.", "primary_source": { "name": "Defender for Identity VPN integration in Microsoft Defender", "url": "https://learn.microsoft.com/en-us/defender-for-identity/vpn-integration", "published_on": "2026-08-07", "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Treat this document as a focused evidence review: Keep VPN identity enrichment on sensor v2 and validate RADIUS accounting data. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official Defender for Identity VPN integration in Microsoft Defender from Microsoft supports the following bounded statements:

\n\n

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs and the conditions the source actually describes.

\n

What the source does not establish

\n

The source says the integration is unsupported in FIPS environments; RADIUS location is context, not proof of a user’s physical presence. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations before translating the source into an operational decision.

\n

Applicability questions

\n\n

DSE recommendation:

\n

DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs, observed and expected states, owner, and reason for deviation.

\n

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations before and after the test, and store only sanitized operational evidence.

\n

Verification and evidence

\n

Build a reproducible chain from Opening applicability statement; VPN data and investigation description to the observed environment. Useful domain evidence includes integration configuration, connectivity tests, event timestamps, alert correlation, role assignments, and case records; label every item with scope, timestamp, collector, and stable identifier.

\n

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

\n

Official references

\n", "content_text": "Treat this document as a focused evidence review: Keep VPN identity enrichment on sensor v2 and validate RADIUS accounting data. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Defender for Identity VPN integration in Microsoft Defender from Microsoft supports the following bounded statements:\n\nDefender for Identity VPN integration is supported only by sensor v2.x. The research record locates this support at Opening applicability statement.\nThe integration listens to forwarded RADIUS accounting events and can add connection IP address and location context plus an abnormal-VPN-connection detection. The research record locates this support at VPN data and investigation description.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs and the conditions the source actually describes.\nWhat the source does not establish\nThe source says the integration is unsupported in FIPS environments; RADIUS location is context, not proof of a user’s physical presence. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Opening applicability statement, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at VPN data and investigation description, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs, observed and expected states, owner, and reason for deviation.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nBuild a reproducible chain from Opening applicability statement; VPN data and investigation description to the observed environment. Useful domain evidence includes integration configuration, connectivity tests, event timestamps, alert correlation, role assignments, and case records; label every item with scope, timestamp, collector, and stable identifier.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nDefender for Identity VPN integration in Microsoft Defender — Microsoft", "content_markdown": "Treat this document as a focused evidence review: Keep VPN identity enrichment on sensor v2 and validate RADIUS accounting data. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Defender for Identity VPN integration in Microsoft Defender](https://learn.microsoft.com/en-us/defender-for-identity/vpn-integration) from Microsoft supports the following bounded statements:\n\n- Defender for Identity VPN integration is supported only by sensor v2.x. The research record locates this support at Opening applicability statement.\n\n- The integration listens to forwarded RADIUS accounting events and can add connection IP address and location context plus an abnormal-VPN-connection detection. The research record locates this support at VPN data and investigation description.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs and the conditions the source actually describes.\n\n## What the source does not establish\n\nThe source says the integration is unsupported in FIPS environments; RADIUS location is context, not proof of a user’s physical presence. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at Opening applicability statement, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at VPN data and investigation description, which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs will be compared with the source, and why that instance?\n\n- How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs, observed and expected states, owner, and reason for deviation.\n\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations before and after the test, and store only sanitized operational evidence.\n\n## Verification and evidence\n\nBuild a reproducible chain from Opening applicability statement; VPN data and investigation description to the observed environment. Useful domain evidence includes integration configuration, connectivity tests, event timestamps, alert correlation, role assignments, and case records; label every item with scope, timestamp, collector, and stable identifier.\n\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\n\n## Official references\n\n- [Defender for Identity VPN integration in Microsoft Defender](https://learn.microsoft.com/en-us/defender-for-identity/vpn-integration) — Microsoft" }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/", "url": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Keep VPN identity enrichment on sensor v2 and validate RADIUS accounting data", "item": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/#article", "identifier": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/", "url": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/", "headline": "Keep VPN identity enrichment on sensor v2 and validate RADIUS accounting data", "description": "Use Defender for Identity VPN integration in Microsoft Defender to review this narrow operational decision without extending the source beyond its…", "abstract": "Use Defender for Identity VPN integration in Microsoft Defender to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Treat this document as a focused evidence review: Keep VPN identity enrichment on sensor v2 and validate RADIUS accounting data. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Defender for Identity VPN integration in Microsoft Defender from Microsoft supports the following bounded statements:\n\nDefender for Identity VPN integration is supported only by sensor v2.x. The research record locates this support at Opening applicability statement.\nThe integration listens to forwarded RADIUS accounting events and can add connection IP address and location context plus an abnormal-VPN-connection detection. The research record locates this support at VPN data and investigation description.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs and the conditions the source actually describes.\nWhat the source does not establish\nThe source says the integration is unsupported in FIPS environments; RADIUS location is context, not proof of a user’s physical presence. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Opening applicability statement, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at VPN data and investigation description, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of identity sensors, connected directories, cloud security services, event flows, roles, alerts, and investigation handoffs, observed and expected states, owner, and reason for deviation.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, time, certificates, cloud identity, endpoint telemetry, network paths, and security operations before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nBuild a reproducible chain from Opening applicability statement; VPN data and investigation description to the observed environment. Useful domain evidence includes integration configuration, connectivity tests, event timestamps, alert correlation, role assignments, and case records; label every item with scope, timestamp, collector, and stable identifier.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nDefender for Identity VPN integration in Microsoft Defender — Microsoft", "datePublished": "2026-08-27T12:12:44+00:00", "dateModified": "2026-08-27T13:04:10+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/keep-vpn-identity-enrichment-on-sensor-v2-and-validate-radius-data/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Keep VPN identity enrichment on sensor v2 and validate RADIUS accounting data" }, "articleSection": [ "Cybersecurity", "IT", "Microsoft 365 & Identity" ], "keywords": [ "Cybersecurity", "IT", "Microsoft 365 & Identity", "Checklist", "Advisory priority" ], "genre": "Checklist", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Microsoft 365 & Identity", "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/" } ], "wordCount": 511, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Defender for Identity VPN integration in Microsoft Defender", "url": "https://learn.microsoft.com/en-us/defender-for-identity/vpn-integration", "datePublished": "2026-08-07" } } ] } }