{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/",
        "slug": "review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes",
        "url": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/"
        },
        "title": "Review Appendix H - Securing Local Administrator Accounts and Groups before AD/DNS changes",
        "summary": "Use Appendix H - Securing Local Administrator Accounts and Groups 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": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-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:31+00:00",
        "modified_at": "2026-08-27T17:11:09+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 629,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Appendix H - Securing Local Administrator Accounts and Groups",
        "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 H - Securing Local Administrator Accounts and Groups",
            "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-H--Securing-Local-Administrator-Accounts-and-Groups",
            "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>Keep this document to one review outcome: Review Appendix H &#8211; Securing Local Administrator Accounts and Groups before AD/DNS changes. 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-H--Securing-Local-Administrator-Accounts-and-Groups\" target=\"_blank\" rel=\"noopener noreferrer\">Appendix H &#8211; Securing Local Administrator Accounts and Groups</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Appendix H: Securing Local Administrator Accounts and Groups, Microsoft states: “On all versions of Windows currently in mainstream support, the local Administrator account is disabled by default, which makes the account unusable for pass-the-hash and other credential theft attacks.” The research record locates this support at <strong>Appendix H: Securing Local Administrator Accounts and Groups</strong>.</li>\n<li>At Appendix H: Securing Local Administrator Accounts and Groups, Microsoft states: “However, in environments that contain legacy operating systems or in which local Administrator accounts have been enabled, these accounts can be used as previously described to propagate compromise across member servers and workstations.” The research record locates this support at <strong>Appendix H: Securing Local Administrator Accounts and Groups</strong>.</li>\n</ul>\n<p>These statements are the factual basis for this document. Do not extend them into a broader assurance. Review forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles only where the source and recorded environment align.</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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Appendix H: Securing Local Administrator Accounts and Groups</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Appendix H: Securing Local Administrator Accounts and Groups</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. Start with applicability, then compare the observed state with the cited source. 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>For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>Appendix H: Securing Local Administrator Accounts and Groups</strong>; <strong>Appendix H: Securing Local Administrator Accounts and Groups</strong>. Favor directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, linked to stable identifiers, time, and operator.</p>\n<p>Label this evidence set <strong>DSE-20260827-055</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</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/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-H--Securing-Local-Administrator-Accounts-and-Groups\" target=\"_blank\" rel=\"noopener noreferrer\">Appendix H &#8211; Securing Local Administrator Accounts and Groups</a> — Microsoft</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Review Appendix H – Securing Local Administrator Accounts and Groups before AD/DNS changes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Appendix H – Securing Local Administrator Accounts and Groups from Microsoft supports the following bounded statements:\n\nAt Appendix H: Securing Local Administrator Accounts and Groups, Microsoft states: “On all versions of Windows currently in mainstream support, the local Administrator account is disabled by default, which makes the account unusable for pass-the-hash and other credential theft attacks.” The research record locates this support at Appendix H: Securing Local Administrator Accounts and Groups.\nAt Appendix H: Securing Local Administrator Accounts and Groups, Microsoft states: “However, in environments that contain legacy operating systems or in which local Administrator accounts have been enabled, these accounts can be used as previously described to propagate compromise across member servers and workstations.” The research record locates this support at Appendix H: Securing Local Administrator Accounts and Groups.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles only where the source and recorded environment align.\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Appendix H: Securing Local Administrator Accounts and Groups, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Appendix H: Securing Local Administrator Accounts and Groups, 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. Start with applicability, then compare the observed state with the cited source. 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.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Appendix H: Securing Local Administrator Accounts and Groups; Appendix H: Securing Local Administrator Accounts and Groups. Favor directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-055 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\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\nAppendix H – Securing Local Administrator Accounts and Groups — Microsoft",
        "content_markdown": "Keep this document to one review outcome: Review Appendix H – Securing Local Administrator Accounts and Groups before AD/DNS changes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Appendix H – Securing Local Administrator Accounts and Groups](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-H--Securing-Local-Administrator-Accounts-and-Groups) from Microsoft supports the following bounded statements:\n\n- At Appendix H: Securing Local Administrator Accounts and Groups, Microsoft states: “On all versions of Windows currently in mainstream support, the local Administrator account is disabled by default, which makes the account unusable for pass-the-hash and other credential theft attacks.” The research record locates this support at Appendix H: Securing Local Administrator Accounts and Groups.\n\n- At Appendix H: Securing Local Administrator Accounts and Groups, Microsoft states: “However, in environments that contain legacy operating systems or in which local Administrator accounts have been enabled, these accounts can be used as previously described to propagate compromise across member servers and workstations.” The research record locates this support at Appendix H: Securing Local Administrator Accounts and Groups.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles only where the source and recorded environment align.\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at Appendix H: Securing Local Administrator Accounts and Groups, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Appendix H: Securing Local Administrator Accounts and Groups, 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. Start with applicability, then compare the observed state with the cited source. 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\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Appendix H: Securing Local Administrator Accounts and Groups; Appendix H: Securing Local Administrator Accounts and Groups. Favor directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, linked to stable identifiers, time, and operator.\n\nLabel this evidence set DSE-20260827-055 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\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- [Appendix H – Securing Local Administrator Accounts and Groups](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-H--Securing-Local-Administrator-Accounts-and-Groups) — 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/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/",
                "url": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Review Appendix H - Securing Local Administrator Accounts and Groups before AD/DNS changes",
                        "item": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/#article",
                "identifier": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/",
                "url": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/",
                "headline": "Review Appendix H - Securing Local Administrator Accounts and Groups before AD/DNS changes",
                "description": "Use Appendix H - Securing Local Administrator Accounts and Groups to review this narrow operational decision without extending the source beyond its…",
                "abstract": "Use Appendix H - Securing Local Administrator Accounts and Groups to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Review Appendix H – Securing Local Administrator Accounts and Groups before AD/DNS changes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Appendix H – Securing Local Administrator Accounts and Groups from Microsoft supports the following bounded statements:\n\nAt Appendix H: Securing Local Administrator Accounts and Groups, Microsoft states: “On all versions of Windows currently in mainstream support, the local Administrator account is disabled by default, which makes the account unusable for pass-the-hash and other credential theft attacks.” The research record locates this support at Appendix H: Securing Local Administrator Accounts and Groups.\nAt Appendix H: Securing Local Administrator Accounts and Groups, Microsoft states: “However, in environments that contain legacy operating systems or in which local Administrator accounts have been enabled, these accounts can be used as previously described to propagate compromise across member servers and workstations.” The research record locates this support at Appendix H: Securing Local Administrator Accounts and Groups.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles only where the source and recorded environment align.\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Appendix H: Securing Local Administrator Accounts and Groups, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Appendix H: Securing Local Administrator Accounts and Groups, 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. Start with applicability, then compare the observed state with the cited source. 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.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Appendix H: Securing Local Administrator Accounts and Groups; Appendix H: Securing Local Administrator Accounts and Groups. Favor directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-055 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\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\nAppendix H – Securing Local Administrator Accounts and Groups — Microsoft",
                "datePublished": "2026-08-27T17:06:31+00:00",
                "dateModified": "2026-08-27T17:11:09+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/"
                },
                "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/review-appendix-h-securing-local-administrator-accounts-and-groups-before-ad-dns-changes/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Review Appendix H - Securing Local Administrator Accounts and Groups before AD/DNS changes"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "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": 629,
                "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 H - Securing Local Administrator Accounts and Groups",
                    "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/Appendix-H--Securing-Local-Administrator-Accounts-and-Groups"
                }
            }
        ]
    }
}