{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/create-account-correlation-rules-only-without-strong-identifiers/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers/",
        "slug": "create-account-correlation-rules-only-without-strong-identifiers",
        "url": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/create-account-correlation-rules-only-without-strong-identifiers/"
        },
        "title": "Create custom account-correlation rules only when strong identifiers are unavailable",
        "summary": "Use Manage account correlation rules in Microsoft Defender for Identity (Preview) to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "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:42+00:00",
        "modified_at": "2026-08-27T13:04:10+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 528,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Manage account correlation rules in Microsoft Defender for Identity (Preview)",
        "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": "Manage account correlation rules in Microsoft Defender for Identity (Preview)",
            "url": "https://learn.microsoft.com/en-us/defender-for-identity/custom-account-correlation-rules",
            "published_on": "2026-07-23",
            "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": "<p>Use this document to connect an official requirement or behavior to observable evidence: Create custom account-correlation rules only when strong identifiers are unavailable. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/defender-for-identity/custom-account-correlation-rules\" target=\"_blank\" rel=\"noopener noreferrer\">Manage account correlation rules in Microsoft Defender for Identity (Preview)</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>Custom correlation rules target accounts that do not share strong identifiers such as account ID, SID, object ID, or UPN. The research record locates this support at <strong>Opening overview</strong>.</li>\n<li>Microsoft describes the rules as especially useful for privileged accounts with unique naming conventions and documents creating, editing, and removing them in the Defender portal. The research record locates this support at <strong>Opening overview and scope</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions and the conditions the source actually describes.</p>\n<h2>What the source does not establish</h2>\n<p>The feature is marked Preview; a naming rule is an inference and must not override contradictory authoritative identity evidence. 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.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Opening overview</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Opening overview and scope</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>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?</li>\n<li>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?</li>\n<li>Who approves the conclusion, exception, test window, and rollback threshold?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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 detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.</p>\n<p>For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.</p>\n<h2>Verification and evidence</h2>\n<p>Build a reproducible chain from <strong>Opening overview</strong>; <strong>Opening overview and scope</strong> to the observed environment. Useful domain evidence includes sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes; label every item with scope, timestamp, collector, and stable identifier.</p>\n<p>Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/defender-for-identity/custom-account-correlation-rules\" target=\"_blank\" rel=\"noopener noreferrer\">Manage account correlation rules in Microsoft Defender for Identity (Preview)</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to connect an official requirement or behavior to observable evidence: Create custom account-correlation rules only when strong identifiers are unavailable. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Manage account correlation rules in Microsoft Defender for Identity (Preview) from Microsoft supports the following bounded statements:\n\nCustom correlation rules target accounts that do not share strong identifiers such as account ID, SID, object ID, or UPN. The research record locates this support at Opening overview.\nMicrosoft describes the rules as especially useful for privileged accounts with unique naming conventions and documents creating, editing, and removing them in the Defender portal. The research record locates this support at Opening overview and scope.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions and the conditions the source actually describes.\nWhat the source does not establish\nThe feature is marked Preview; a naming rule is an inference and must not override contradictory authoritative identity evidence. 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 Opening overview and scope, 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. Use a two-person review for the source interpretation and the resulting operational decision. 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.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nBuild a reproducible chain from Opening overview; Opening overview and scope to the observed environment. Useful domain evidence includes sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes; label every item with scope, timestamp, collector, and stable identifier.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nManage account correlation rules in Microsoft Defender for Identity (Preview) — Microsoft",
        "content_markdown": "Use this document to connect an official requirement or behavior to observable evidence: Create custom account-correlation rules only when strong identifiers are unavailable. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Manage account correlation rules in Microsoft Defender for Identity (Preview)](https://learn.microsoft.com/en-us/defender-for-identity/custom-account-correlation-rules) from Microsoft supports the following bounded statements:\n\n- Custom correlation rules target accounts that do not share strong identifiers such as account ID, SID, object ID, or UPN. The research record locates this support at Opening overview.\n\n- Microsoft describes the rules as especially useful for privileged accounts with unique naming conventions and documents creating, editing, and removing them in the Defender portal. The research record locates this support at Opening overview and scope.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions and the conditions the source actually describes.\n\n## What the source does not establish\n\nThe feature is marked Preview; a naming rule is an inference and must not override contradictory authoritative identity evidence. 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 Opening overview and scope, 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. Use a two-person review for the source interpretation and the resulting operational decision. 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\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\n\n## Verification and evidence\n\nBuild a reproducible chain from Opening overview; Opening overview and scope to the observed environment. Useful domain evidence includes sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes; label every item with scope, timestamp, collector, and stable identifier.\n\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\n\n## Official references\n\n- [Manage account correlation rules in Microsoft Defender for Identity (Preview)](https://learn.microsoft.com/en-us/defender-for-identity/custom-account-correlation-rules) — 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/create-account-correlation-rules-only-without-strong-identifiers/",
                "url": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Create custom account-correlation rules only when strong identifiers are unavailable",
                        "item": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers/#article",
                "identifier": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers/",
                "url": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers/",
                "headline": "Create custom account-correlation rules only when strong identifiers are unavailable",
                "description": "Use Manage account correlation rules in Microsoft Defender for Identity (Preview) to review this narrow operational decision without extending the…",
                "abstract": "Use Manage account correlation rules in Microsoft Defender for Identity (Preview) to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to connect an official requirement or behavior to observable evidence: Create custom account-correlation rules only when strong identifiers are unavailable. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Manage account correlation rules in Microsoft Defender for Identity (Preview) from Microsoft supports the following bounded statements:\n\nCustom correlation rules target accounts that do not share strong identifiers such as account ID, SID, object ID, or UPN. The research record locates this support at Opening overview.\nMicrosoft describes the rules as especially useful for privileged accounts with unique naming conventions and documents creating, editing, and removing them in the Defender portal. The research record locates this support at Opening overview and scope.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions and the conditions the source actually describes.\nWhat the source does not establish\nThe feature is marked Preview; a naming rule is an inference and must not override contradictory authoritative identity evidence. 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 Opening overview and scope, 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. Use a two-person review for the source interpretation and the resulting operational decision. 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.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nBuild a reproducible chain from Opening overview; Opening overview and scope to the observed environment. Useful domain evidence includes sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes; label every item with scope, timestamp, collector, and stable identifier.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nManage account correlation rules in Microsoft Defender for Identity (Preview) — Microsoft",
                "datePublished": "2026-08-27T12:12:42+00:00",
                "dateModified": "2026-08-27T13:04:10+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/create-account-correlation-rules-only-without-strong-identifiers/"
                },
                "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/create-account-correlation-rules-only-without-strong-identifiers/#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": "Create custom account-correlation rules only when strong identifiers are unavailable"
                },
                "articleSection": [
                    "Cybersecurity",
                    "IT",
                    "Microsoft 365 & Identity"
                ],
                "keywords": [
                    "Cybersecurity",
                    "IT",
                    "Microsoft 365 & Identity",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "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": 528,
                "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": "Manage account correlation rules in Microsoft Defender for Identity (Preview)",
                    "url": "https://learn.microsoft.com/en-us/defender-for-identity/custom-account-correlation-rules",
                    "datePublished": "2026-07-23"
                }
            }
        ]
    }
}