{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/",
        "slug": "scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state",
        "url": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/"
        },
        "title": "Scope Appendix E - Securing Enterprise Admins Groups in Active Directory in observed AD/DNS state",
        "summary": "Use Appendix E - Securing Enterprise Admins Groups in Active Directory to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "briefing",
            "name": "Briefing"
        },
        "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": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "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-27T17:06:45+00:00",
        "modified_at": "2026-08-27T17:07:31+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 627,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Appendix E - Securing Enterprise Admins Groups in Active Directory",
        "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": "Appendix E - Securing Enterprise Admins Groups in Active Directory",
            "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-E--Securing-Enterprise-Admins-Groups-in-Active-Directory",
            "published_on": null,
            "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 resolve one bounded operational decision: Scope Appendix E &#8211; Securing Enterprise Admins Groups in Active Directory in observed AD/DNS state. 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/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-E--Securing-Enterprise-Admins-Groups-in-Active-Directory\" target=\"_blank\" rel=\"noopener noreferrer\">Appendix E &#8211; Securing Enterprise Admins Groups in Active Directory</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Appendix E: Securing Enterprise Admins Groups in Active Directory, Microsoft states: “Enterprise Admins are, by default, members of the Administrators group in each domain in the forest.” The research record locates this support at <strong>Appendix E: Securing Enterprise Admins Groups in Active Directory</strong>.</li>\n<li>At Appendix E: Securing Enterprise Admins Groups in Active Directory, Microsoft states: “You should not remove the EA group from the Administrators groups in each domain because in the event of a forest disaster recovery scenario, EA rights will likely be required.” The research record locates this support at <strong>Appendix E: Securing Enterprise Admins Groups in Active Directory</strong>.</li>\n</ul>\n<p>The source support ends with the statements listed above. Use them to examine forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles in the applicable environment, not to imply a wider guarantee.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. No current deployment state or change approval follows from the source alone. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, 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>Appendix E: Securing Enterprise Admins Groups in Active Directory</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Appendix E: Securing Enterprise Admins Groups in Active Directory</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Within forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, which versions, roles, and configuration states define the review population?</li>\n<li>Could Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity invalidate the test, hide a failure, or change applicability?</li>\n<li>Who owns the decision, and which observation requires stopping, escalation, or rollback?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation.</p>\n<p>If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>A reviewer should be able to retrace the decision from <strong>Appendix E: Securing Enterprise Admins Groups in Active Directory</strong>; <strong>Appendix E: Securing Enterprise Admins Groups in Active Directory</strong> through directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests. Record what was collected, where, when, by whom, and which system or role it represents.</p>\n<p>Label this evidence set <strong>DSE-20260827-041</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>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.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-E--Securing-Enterprise-Admins-Groups-in-Active-Directory\" target=\"_blank\" rel=\"noopener noreferrer\">Appendix E &#8211; Securing Enterprise Admins Groups in Active Directory</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to resolve one bounded operational decision: Scope Appendix E – Securing Enterprise Admins Groups in Active Directory in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Appendix E – Securing Enterprise Admins Groups in Active Directory from Microsoft supports the following bounded statements:\n\nAt Appendix E: Securing Enterprise Admins Groups in Active Directory, Microsoft states: “Enterprise Admins are, by default, members of the Administrators group in each domain in the forest.” The research record locates this support at Appendix E: Securing Enterprise Admins Groups in Active Directory.\nAt Appendix E: Securing Enterprise Admins Groups in Active Directory, Microsoft states: “You should not remove the EA group from the Administrators groups in each domain because in the event of a forest disaster recovery scenario, EA rights will likely be required.” The research record locates this support at Appendix E: Securing Enterprise Admins Groups in Active Directory.\n\nThe source support ends with the statements listed above. Use them to examine forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. No current deployment state or change approval follows from the source alone. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at Appendix E: Securing Enterprise Admins Groups in Active Directory, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Appendix E: Securing Enterprise Admins Groups in Active Directory, which observable configuration, record, or test can confirm applicability here?\nWithin forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, which versions, roles, and configuration states define the review population?\nCould Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, 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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.\nVerification and evidence\nA reviewer should be able to retrace the decision from Appendix E: Securing Enterprise Admins Groups in Active Directory; Appendix E: Securing Enterprise Admins Groups in Active Directory through directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests. Record what was collected, where, when, by whom, and which system or role it represents.\nLabel this evidence set DSE-20260827-041 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\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\nAppendix E – Securing Enterprise Admins Groups in Active Directory — Microsoft",
        "content_markdown": "Use this document to resolve one bounded operational decision: Scope Appendix E – Securing Enterprise Admins Groups in Active Directory in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Appendix E – Securing Enterprise Admins Groups in Active Directory](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-E--Securing-Enterprise-Admins-Groups-in-Active-Directory) from Microsoft supports the following bounded statements:\n\n- At Appendix E: Securing Enterprise Admins Groups in Active Directory, Microsoft states: “Enterprise Admins are, by default, members of the Administrators group in each domain in the forest.” The research record locates this support at Appendix E: Securing Enterprise Admins Groups in Active Directory.\n\n- At Appendix E: Securing Enterprise Admins Groups in Active Directory, Microsoft states: “You should not remove the EA group from the Administrators groups in each domain because in the event of a forest disaster recovery scenario, EA rights will likely be required.” The research record locates this support at Appendix E: Securing Enterprise Admins Groups in Active Directory.\n\nThe source support ends with the statements listed above. Use them to examine forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles in the applicable environment, not to imply a wider guarantee.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. No current deployment state or change approval follows from the source alone. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, and treat examples or options as conditional inputs rather than defaults.\n\n## Applicability questions\n\n- For source statement 1 at Appendix E: Securing Enterprise Admins Groups in Active Directory, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Appendix E: Securing Enterprise Admins Groups in Active Directory, which observable configuration, record, or test can confirm applicability here?\n\n- Within forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, which versions, roles, and configuration states define the review population?\n\n- Could Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity invalidate the test, hide a failure, or change applicability?\n\n- Who owns the decision, and which observation requires stopping, escalation, or rollback?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, 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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.\n\n## Verification and evidence\n\nA reviewer should be able to retrace the decision from Appendix E: Securing Enterprise Admins Groups in Active Directory; Appendix E: Securing Enterprise Admins Groups in Active Directory through directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests. Record what was collected, where, when, by whom, and which system or role it represents.\n\nLabel this evidence set DSE-20260827-041 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\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- [Appendix E – Securing Enterprise Admins Groups in Active Directory](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-E--Securing-Enterprise-Admins-Groups-in-Active-Directory) — 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/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/",
                "url": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Scope Appendix E - Securing Enterprise Admins Groups in Active Directory in observed AD/DNS state",
                        "item": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/#article",
                "identifier": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/",
                "url": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/",
                "headline": "Scope Appendix E - Securing Enterprise Admins Groups in Active Directory in observed AD/DNS state",
                "description": "Use Appendix E - Securing Enterprise Admins Groups in Active Directory to review this narrow operational decision without extending the source beyond…",
                "abstract": "Use Appendix E - Securing Enterprise Admins Groups in Active Directory to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to resolve one bounded operational decision: Scope Appendix E – Securing Enterprise Admins Groups in Active Directory in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Appendix E – Securing Enterprise Admins Groups in Active Directory from Microsoft supports the following bounded statements:\n\nAt Appendix E: Securing Enterprise Admins Groups in Active Directory, Microsoft states: “Enterprise Admins are, by default, members of the Administrators group in each domain in the forest.” The research record locates this support at Appendix E: Securing Enterprise Admins Groups in Active Directory.\nAt Appendix E: Securing Enterprise Admins Groups in Active Directory, Microsoft states: “You should not remove the EA group from the Administrators groups in each domain because in the event of a forest disaster recovery scenario, EA rights will likely be required.” The research record locates this support at Appendix E: Securing Enterprise Admins Groups in Active Directory.\n\nThe source support ends with the statements listed above. Use them to examine forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. No current deployment state or change approval follows from the source alone. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at Appendix E: Securing Enterprise Admins Groups in Active Directory, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Appendix E: Securing Enterprise Admins Groups in Active Directory, which observable configuration, record, or test can confirm applicability here?\nWithin forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, which versions, roles, and configuration states define the review population?\nCould Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, 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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.\nVerification and evidence\nA reviewer should be able to retrace the decision from Appendix E: Securing Enterprise Admins Groups in Active Directory; Appendix E: Securing Enterprise Admins Groups in Active Directory through directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests. Record what was collected, where, when, by whom, and which system or role it represents.\nLabel this evidence set DSE-20260827-041 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\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\nAppendix E – Securing Enterprise Admins Groups in Active Directory — Microsoft",
                "datePublished": "2026-08-27T17:06:45+00:00",
                "dateModified": "2026-08-27T17:07:31+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/"
                },
                "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/scope-appendix-e-securing-enterprise-admins-groups-in-active-directory-in-observed-ad-dns-state/#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": "Scope Appendix E - Securing Enterprise Admins Groups in Active Directory in observed AD/DNS state"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Briefing",
                    "Advisory priority"
                ],
                "genre": "Briefing",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 627,
                "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": "Appendix E - Securing Enterprise Admins Groups in Active Directory",
                    "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-E--Securing-Enterprise-Admins-Groups-in-Active-Directory"
                }
            }
        ]
    }
}