{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/use-identity-alerts-for-detections-not-complete-audit-history/", "item": { "id": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/", "slug": "use-identity-alerts-for-detections-not-complete-audit-history", "url": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history.md", "json": "https://update.dsesecurity.com/api/v1/posts/use-identity-alerts-for-detections-not-complete-audit-history/" }, "title": "Use Defender for Identity alerts for detections, not complete audit history", "summary": "Use Security alerts in Microsoft Defender for Identity to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "playbook", "name": "Playbook" }, "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:13:01+00:00", "modified_at": "2026-08-27T13:04:09+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 503, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Security alerts in Microsoft Defender for Identity", "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": "Security alerts in Microsoft Defender for Identity", "url": "https://learn.microsoft.com/en-us/defender-for-identity/alerts-overview", "published_on": "2026-07-01", "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": "

Keep this document to one review outcome: Use Defender for Identity alerts for detections, not complete audit history. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official Security alerts in Microsoft Defender for Identity from Microsoft supports the following bounded statements:

\n\n

These statements are the factual basis for this document. Do not extend them into a broader assurance. Review identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions only where the source and recorded environment align.

\n

What the source does not establish

\n

Preserve separate authoritative audit and log-retention controls; alert absence is not proof that an activity did not occur. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, 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. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.

\n

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations and sanitize protected material before retention.

\n

Verification and evidence

\n

Keep the source locations Opening overview; Audit-boundary paragraph adjacent to the sanitized artifacts used for comparison. Prefer sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes, with enough identity and timing data for an independent recheck.

\n

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

\n

Official references

\n", "content_text": "Keep this document to one review outcome: Use Defender for Identity alerts for detections, not complete audit history. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Security alerts in Microsoft Defender for Identity from Microsoft supports the following bounded statements:\n\nDefender for Identity alerts describe suspicious activities and identify involved actors and computers with direct evidence links. The research record locates this support at Opening overview.\nMicrosoft explicitly says Defender for Identity is not an auditing or logging solution for every server operation and captures only data needed for detections and recommendations. The research record locates this support at Audit-boundary paragraph.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions only where the source and recorded environment align.\nWhat the source does not establish\nPreserve separate authoritative audit and log-retention controls; alert absence is not proof that an activity did not occur. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Audit-boundary paragraph, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions 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, sensor health, time, network visibility, cloud analytics, endpoint evidence, 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. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations and sanitize protected material before retention.\nVerification and evidence\nKeep the source locations Opening overview; Audit-boundary paragraph adjacent to the sanitized artifacts used for comparison. Prefer sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes, with enough identity and timing data for an independent recheck.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nSecurity alerts in Microsoft Defender for Identity — Microsoft", "content_markdown": "Keep this document to one review outcome: Use Defender for Identity alerts for detections, not complete audit history. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Security alerts in Microsoft Defender for Identity](https://learn.microsoft.com/en-us/defender-for-identity/alerts-overview) from Microsoft supports the following bounded statements:\n\n- Defender for Identity alerts describe suspicious activities and identify involved actors and computers with direct evidence links. The research record locates this support at Opening overview.\n\n- Microsoft explicitly says Defender for Identity is not an auditing or logging solution for every server operation and captures only data needed for detections and recommendations. The research record locates this support at Audit-boundary paragraph.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions only where the source and recorded environment align.\n\n## What the source does not establish\n\nPreserve separate authoritative audit and log-retention controls; alert absence is not proof that an activity did not occur. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Audit-boundary paragraph, which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions 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, sensor health, time, network visibility, cloud analytics, endpoint evidence, 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. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.\n\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations and sanitize protected material before retention.\n\n## Verification and evidence\n\nKeep the source locations Opening overview; Audit-boundary paragraph adjacent to the sanitized artifacts used for comparison. Prefer sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes, with enough identity and timing data for an independent recheck.\n\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\n\n## Official references\n\n- [Security alerts in Microsoft Defender for Identity](https://learn.microsoft.com/en-us/defender-for-identity/alerts-overview) — 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/use-identity-alerts-for-detections-not-complete-audit-history/", "url": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Use Defender for Identity alerts for detections, not complete audit history", "item": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/#article", "identifier": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/", "url": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/", "headline": "Use Defender for Identity alerts for detections, not complete audit history", "description": "Use Security alerts in Microsoft Defender for Identity to review this narrow operational decision without extending the source beyond its stated scope.", "abstract": "Use Security alerts in Microsoft Defender for Identity to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Keep this document to one review outcome: Use Defender for Identity alerts for detections, not complete audit history. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Security alerts in Microsoft Defender for Identity from Microsoft supports the following bounded statements:\n\nDefender for Identity alerts describe suspicious activities and identify involved actors and computers with direct evidence links. The research record locates this support at Opening overview.\nMicrosoft explicitly says Defender for Identity is not an auditing or logging solution for every server operation and captures only data needed for detections and recommendations. The research record locates this support at Audit-boundary paragraph.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions only where the source and recorded environment align.\nWhat the source does not establish\nPreserve separate authoritative audit and log-retention controls; alert absence is not proof that an activity did not occur. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Audit-boundary paragraph, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions 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, sensor health, time, network visibility, cloud analytics, endpoint evidence, 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. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations and sanitize protected material before retention.\nVerification and evidence\nKeep the source locations Opening overview; Audit-boundary paragraph adjacent to the sanitized artifacts used for comparison. Prefer sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes, with enough identity and timing data for an independent recheck.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nSecurity alerts in Microsoft Defender for Identity — Microsoft", "datePublished": "2026-08-27T12:13:01+00:00", "dateModified": "2026-08-27T13:04:09+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/use-identity-alerts-for-detections-not-complete-audit-history/" }, "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/use-identity-alerts-for-detections-not-complete-audit-history/#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": "Use Defender for Identity alerts for detections, not complete audit history" }, "articleSection": [ "Cybersecurity", "IT", "Microsoft 365 & Identity" ], "keywords": [ "Cybersecurity", "IT", "Microsoft 365 & Identity", "Playbook", "Advisory priority" ], "genre": "Playbook", "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": 503, "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": "Security alerts in Microsoft Defender for Identity", "url": "https://learn.microsoft.com/en-us/defender-for-identity/alerts-overview", "datePublished": "2026-07-01" } } ] } }