{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/", "slug": "dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path", "url": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/" }, "title": "Qualify PowerShell Direct as a host-to-guest administration path", "summary": "What conditions must hold before using PowerShell Direct for a Windows virtual machine?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "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-09-08T18:14:21+00:00", "modified_at": "2026-09-08T18:26:31+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 227, "potentially_affected": "Hyper-V administrators considering PowerShell Direct for a local Windows guest.", "dse_recommendation": "Define one bounded administrative action and the expected guest before opening a session.", "primary_source": { "name": "Manage Windows Virtual Machines with PowerShell Direct", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/powershell-direct", "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": "

Source facts

\n

PowerShell Direct runs PowerShell in a Windows guest from its Hyper-V host without depending on guest networking or remote-management configuration. Microsoft requires the virtual machine to be local, running, and to have a configured user profile. The operator must be a Hyper-V administrator on the host and provide valid credentials for the guest. Microsoft Learn.

\n

Applicability

\n

Check the host and guest versions against the current source, then confirm the virtual machine identifier and its actual host. Keep host privileges and guest authentication as two separate prerequisites. An unavailable guest network is only one part of the access decision.

\n

DSE recommendation

\n

Define one bounded administrative action and the expected guest before opening a session. Use the authorized guest account and protect its credentials through the approved handling process. Have the operator record the guest identity from inside the session before running the intended command. For repeatable work, decide when the session will be closed and who owns cleanup.

\n

Verification

\n

Use a harmless inventory command on a representative guest and compare its output with the known guest identity. Confirm the command executed inside that guest rather than on the host. Record failures by prerequisite: host authorization, VM location and state, guest credentials, or supported version. Close the session and retain a sanitized result.

\n

Official references

\n

Microsoft Learn: Manage Windows Virtual Machines with PowerShell Direct. Source reviewed September 8, 2026.

", "content_text": "Source facts\nPowerShell Direct runs PowerShell in a Windows guest from its Hyper-V host without depending on guest networking or remote-management configuration. Microsoft requires the virtual machine to be local, running, and to have a configured user profile. The operator must be a Hyper-V administrator on the host and provide valid credentials for the guest. Microsoft Learn.\nApplicability\nCheck the host and guest versions against the current source, then confirm the virtual machine identifier and its actual host. Keep host privileges and guest authentication as two separate prerequisites. An unavailable guest network is only one part of the access decision.\nDSE recommendation\nDefine one bounded administrative action and the expected guest before opening a session. Use the authorized guest account and protect its credentials through the approved handling process. Have the operator record the guest identity from inside the session before running the intended command. For repeatable work, decide when the session will be closed and who owns cleanup.\nVerification\nUse a harmless inventory command on a representative guest and compare its output with the known guest identity. Confirm the command executed inside that guest rather than on the host. Record failures by prerequisite: host authorization, VM location and state, guest credentials, or supported version. Close the session and retain a sanitized result.\nOfficial references\nMicrosoft Learn: Manage Windows Virtual Machines with PowerShell Direct. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nPowerShell Direct runs PowerShell in a Windows guest from its Hyper-V host without depending on guest networking or remote-management configuration. Microsoft requires the virtual machine to be local, running, and to have a configured user profile. The operator must be a Hyper-V administrator on the host and provide valid credentials for the guest. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/powershell-direct).\n\n## Applicability\n\nCheck the host and guest versions against the current source, then confirm the virtual machine identifier and its actual host. Keep host privileges and guest authentication as two separate prerequisites. An unavailable guest network is only one part of the access decision.\n\n## DSE recommendation\n\nDefine one bounded administrative action and the expected guest before opening a session. Use the authorized guest account and protect its credentials through the approved handling process. Have the operator record the guest identity from inside the session before running the intended command. For repeatable work, decide when the session will be closed and who owns cleanup.\n\n## Verification\n\nUse a harmless inventory command on a representative guest and compare its output with the known guest identity. Confirm the command executed inside that guest rather than on the host. Record failures by prerequisite: host authorization, VM location and state, guest credentials, or supported version. Close the session and retain a sanitized result.\n\n## Official references\n\n[Microsoft Learn: Manage Windows Virtual Machines with PowerShell Direct](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/powershell-direct). Source reviewed September 8, 2026." }, "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/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/", "url": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Qualify PowerShell Direct as a host-to-guest administration path", "item": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/", "url": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/", "headline": "Qualify PowerShell Direct as a host-to-guest administration path", "description": "What conditions must hold before using PowerShell Direct for a Windows virtual machine?", "abstract": "What conditions must hold before using PowerShell Direct for a Windows virtual machine?", "articleBody": "Source facts\nPowerShell Direct runs PowerShell in a Windows guest from its Hyper-V host without depending on guest networking or remote-management configuration. Microsoft requires the virtual machine to be local, running, and to have a configured user profile. The operator must be a Hyper-V administrator on the host and provide valid credentials for the guest. Microsoft Learn.\nApplicability\nCheck the host and guest versions against the current source, then confirm the virtual machine identifier and its actual host. Keep host privileges and guest authentication as two separate prerequisites. An unavailable guest network is only one part of the access decision.\nDSE recommendation\nDefine one bounded administrative action and the expected guest before opening a session. Use the authorized guest account and protect its credentials through the approved handling process. Have the operator record the guest identity from inside the session before running the intended command. For repeatable work, decide when the session will be closed and who owns cleanup.\nVerification\nUse a harmless inventory command on a representative guest and compare its output with the known guest identity. Confirm the command executed inside that guest rather than on the host. Record failures by prerequisite: host authorization, VM location and state, guest credentials, or supported version. Close the session and retain a sanitized result.\nOfficial references\nMicrosoft Learn: Manage Windows Virtual Machines with PowerShell Direct. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:21+00:00", "dateModified": "2026-09-08T18:26:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/" }, "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/dse-20260908-170-qualify-powershell-direct-as-a-host-to-guest-administration-path/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Qualify PowerShell Direct as a host-to-guest administration path" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 227, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Manage Windows Virtual Machines with PowerShell Direct", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/powershell-direct" } } ] } }