{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/disable-enabled-domain-guest-account-from-infrastructure-assessment/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment/",
        "slug": "disable-enabled-domain-guest-account-from-infrastructure-assessment",
        "url": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/disable-enabled-domain-guest-account-from-infrastructure-assessment/"
        },
        "title": "Disable an enabled domain Guest account surfaced by identity infrastructure assessments",
        "summary": "Use Identity infrastructure security assessments 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:06+00:00",
        "modified_at": "2026-08-27T13:01:32+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 Identity infrastructure security assessments",
        "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": "Identity infrastructure security assessments",
            "url": "https://learn.microsoft.com/en-us/defender-for-identity/security-posture-assessments/identity-infrastructure",
            "published_on": "2025-09-10",
            "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>Keep this document to one review outcome: Disable an enabled domain Guest account surfaced by identity infrastructure assessments. 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/security-posture-assessments/identity-infrastructure\" target=\"_blank\" rel=\"noopener noreferrer\">Identity infrastructure security assessments</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>The identity-infrastructure assessment includes a recommendation that identifies whether an Active Directory Guest account is enabled. The research record locates this support at <strong>Domain Guest account assessment description</strong>.</li>\n<li>The stated goal of that recommendation is for the domain Guest account not to be enabled. The research record locates this support at <strong>Domain Guest account assessment description</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking and the conditions the source actually describes.</p>\n<h2>What the source does not establish</h2>\n<p>Confirm application and recovery dependencies before changing the account and validate status after the documented assessment delay. No current deployment state or change approval follows from the source alone. Validate Active Directory data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners, and treat examples or options as conditional inputs rather than defaults.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Domain Guest account assessment description</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Domain Guest account assessment description</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which deployed instance of directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking 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 data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners?</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 directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking, 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 data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners 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>Domain Guest account assessment description</strong>; <strong>Domain Guest account assessment description</strong> to the observed environment. Useful domain evidence includes affected-entity lists, directory attributes, relationship paths, assessment timestamps, remediation tests, and accepted exceptions; 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/security-posture-assessments/identity-infrastructure\" target=\"_blank\" rel=\"noopener noreferrer\">Identity infrastructure security assessments</a> — Microsoft</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Disable an enabled domain Guest account surfaced by identity infrastructure assessments. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Identity infrastructure security assessments from Microsoft supports the following bounded statements:\n\nThe identity-infrastructure assessment includes a recommendation that identifies whether an Active Directory Guest account is enabled. The research record locates this support at Domain Guest account assessment description.\nThe stated goal of that recommendation is for the domain Guest account not to be enabled. The research record locates this support at Domain Guest account assessment description.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking and the conditions the source actually describes.\nWhat the source does not establish\nConfirm application and recovery dependencies before changing the account and validate status after the documented assessment delay. No current deployment state or change approval follows from the source alone. Validate Active Directory data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at Domain Guest account assessment description, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Domain Guest account assessment description, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners?\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 directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking, 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 data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nBuild a reproducible chain from Domain Guest account assessment description; Domain Guest account assessment description to the observed environment. Useful domain evidence includes affected-entity lists, directory attributes, relationship paths, assessment timestamps, remediation tests, and accepted exceptions; 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\nIdentity infrastructure security assessments — Microsoft",
        "content_markdown": "Keep this document to one review outcome: Disable an enabled domain Guest account surfaced by identity infrastructure assessments. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Identity infrastructure security assessments](https://learn.microsoft.com/en-us/defender-for-identity/security-posture-assessments/identity-infrastructure) from Microsoft supports the following bounded statements:\n\n- The identity-infrastructure assessment includes a recommendation that identifies whether an Active Directory Guest account is enabled. The research record locates this support at Domain Guest account assessment description.\n\n- The stated goal of that recommendation is for the domain Guest account not to be enabled. The research record locates this support at Domain Guest account assessment description.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking and the conditions the source actually describes.\n\n## What the source does not establish\n\nConfirm application and recovery dependencies before changing the account and validate status after the documented assessment delay. No current deployment state or change approval follows from the source alone. Validate Active Directory data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners, and treat examples or options as conditional inputs rather than defaults.\n\n## Applicability questions\n\n- For source statement 1 at Domain Guest account assessment description, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Domain Guest account assessment description, which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking 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 data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners?\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 directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking, 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 data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners 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 Domain Guest account assessment description; Domain Guest account assessment description to the observed environment. Useful domain evidence includes affected-entity lists, directory attributes, relationship paths, assessment timestamps, remediation tests, and accepted exceptions; 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- [Identity infrastructure security assessments](https://learn.microsoft.com/en-us/defender-for-identity/security-posture-assessments/identity-infrastructure) — 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/disable-enabled-domain-guest-account-from-infrastructure-assessment/",
                "url": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Disable an enabled domain Guest account surfaced by identity infrastructure assessments",
                        "item": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment/#article",
                "identifier": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment/",
                "url": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment/",
                "headline": "Disable an enabled domain Guest account surfaced by identity infrastructure assessments",
                "description": "Use Identity infrastructure security assessments to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use Identity infrastructure security assessments to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Disable an enabled domain Guest account surfaced by identity infrastructure assessments. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Identity infrastructure security assessments from Microsoft supports the following bounded statements:\n\nThe identity-infrastructure assessment includes a recommendation that identifies whether an Active Directory Guest account is enabled. The research record locates this support at Domain Guest account assessment description.\nThe stated goal of that recommendation is for the domain Guest account not to be enabled. The research record locates this support at Domain Guest account assessment description.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking and the conditions the source actually describes.\nWhat the source does not establish\nConfirm application and recovery dependencies before changing the account and validate status after the documented assessment delay. No current deployment state or change approval follows from the source alone. Validate Active Directory data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at Domain Guest account assessment description, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Domain Guest account assessment description, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners?\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 directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking, 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 data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nBuild a reproducible chain from Domain Guest account assessment description; Domain Guest account assessment description to the observed environment. Useful domain evidence includes affected-entity lists, directory attributes, relationship paths, assessment timestamps, remediation tests, and accepted exceptions; 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\nIdentity infrastructure security assessments — Microsoft",
                "datePublished": "2026-08-27T12:13:06+00:00",
                "dateModified": "2026-08-27T13:01:32+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/disable-enabled-domain-guest-account-from-infrastructure-assessment/"
                },
                "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/disable-enabled-domain-guest-account-from-infrastructure-assessment/#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": "Disable an enabled domain Guest account surfaced by identity infrastructure assessments"
                },
                "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": "Identity infrastructure security assessments",
                    "url": "https://learn.microsoft.com/en-us/defender-for-identity/security-posture-assessments/identity-infrastructure",
                    "datePublished": "2025-09-10"
                }
            }
        ]
    }
}