{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/", "slug": "dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata", "url": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/" }, "title": "Treat Hyper-V key-value exchange as persistent host-visible metadata", "summary": "What should an application account for when using Hyper-V key-value exchange?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "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": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "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-09-08T18:15:19+00:00", "modified_at": "2026-09-08T18:23:26+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 219, "potentially_affected": "Administrators and developers reviewing Hyper-V Data Exchange integration services.", "dse_recommendation": "Create a small metadata contract naming each key, its meaning, its owner, and when it should be updated or removed.", "primary_source": { "name": "Data Exchange: Using key-value pairs to share information between the host and guest on Hyper-V", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/integration-services-data-exchange", "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

Hyper-V Data Exchange shares small pieces of information between a guest VM and its host, including automatically generated and custom key-value pairs. Keys and values are strings. The information travels over VMbus without requiring a network connection between host and guest. Pairs persist until deleted and travel with the VM during live migration. Microsoft tells applications to remove pairs that are no longer needed. Microsoft documentation.

\n

Applicability

\n

Identify the producer, consumer, data contents, and lifecycle of each proposed key. Review whether the integration service and guest implementation required by the application are present in the supported configuration.

\n

DSE recommendation

\n

Create a small metadata contract naming each key, its meaning, its owner, and when it should be updated or removed. Avoid placing credentials or unnecessary sensitive data in the contract. Define how consumers should handle a missing or stale value and who will investigate conflicting entries.

\n

Verification

\n

Create and read a non-sensitive test pair from the intended endpoints, change it, and confirm deletion when the task finishes. Include a controlled VM migration if the application relies on migration continuity. Record the actual values and timing observed rather than interpreting a stale pair as current guest health.

\n

Official references

\n

Microsoft Learn: Data Exchange: Using key-value pairs to share information between the host and guest on Hyper-V. Source reviewed September 8, 2026.

", "content_text": "Source facts\nHyper-V Data Exchange shares small pieces of information between a guest VM and its host, including automatically generated and custom key-value pairs. Keys and values are strings. The information travels over VMbus without requiring a network connection between host and guest. Pairs persist until deleted and travel with the VM during live migration. Microsoft tells applications to remove pairs that are no longer needed. Microsoft documentation.\nApplicability\nIdentify the producer, consumer, data contents, and lifecycle of each proposed key. Review whether the integration service and guest implementation required by the application are present in the supported configuration.\nDSE recommendation\nCreate a small metadata contract naming each key, its meaning, its owner, and when it should be updated or removed. Avoid placing credentials or unnecessary sensitive data in the contract. Define how consumers should handle a missing or stale value and who will investigate conflicting entries.\nVerification\nCreate and read a non-sensitive test pair from the intended endpoints, change it, and confirm deletion when the task finishes. Include a controlled VM migration if the application relies on migration continuity. Record the actual values and timing observed rather than interpreting a stale pair as current guest health.\nOfficial references\nMicrosoft Learn: Data Exchange: Using key-value pairs to share information between the host and guest on Hyper-V. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nHyper-V Data Exchange shares small pieces of information between a guest VM and its host, including automatically generated and custom key-value pairs. Keys and values are strings. The information travels over VMbus without requiring a network connection between host and guest. Pairs persist until deleted and travel with the VM during live migration. Microsoft tells applications to remove pairs that are no longer needed. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/integration-services-data-exchange).\n\n## Applicability\n\nIdentify the producer, consumer, data contents, and lifecycle of each proposed key. Review whether the integration service and guest implementation required by the application are present in the supported configuration.\n\n## DSE recommendation\n\nCreate a small metadata contract naming each key, its meaning, its owner, and when it should be updated or removed. Avoid placing credentials or unnecessary sensitive data in the contract. Define how consumers should handle a missing or stale value and who will investigate conflicting entries.\n\n## Verification\n\nCreate and read a non-sensitive test pair from the intended endpoints, change it, and confirm deletion when the task finishes. Include a controlled VM migration if the application relies on migration continuity. Record the actual values and timing observed rather than interpreting a stale pair as current guest health.\n\n## Official references\n\n[Microsoft Learn: Data Exchange: Using key-value pairs to share information between the host and guest on Hyper-V](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/integration-services-data-exchange). 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-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/", "url": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Treat Hyper-V key-value exchange as persistent host-visible metadata", "item": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/", "url": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/", "headline": "Treat Hyper-V key-value exchange as persistent host-visible metadata", "description": "What should an application account for when using Hyper-V key-value exchange?", "abstract": "What should an application account for when using Hyper-V key-value exchange?", "articleBody": "Source facts\nHyper-V Data Exchange shares small pieces of information between a guest VM and its host, including automatically generated and custom key-value pairs. Keys and values are strings. The information travels over VMbus without requiring a network connection between host and guest. Pairs persist until deleted and travel with the VM during live migration. Microsoft tells applications to remove pairs that are no longer needed. Microsoft documentation.\nApplicability\nIdentify the producer, consumer, data contents, and lifecycle of each proposed key. Review whether the integration service and guest implementation required by the application are present in the supported configuration.\nDSE recommendation\nCreate a small metadata contract naming each key, its meaning, its owner, and when it should be updated or removed. Avoid placing credentials or unnecessary sensitive data in the contract. Define how consumers should handle a missing or stale value and who will investigate conflicting entries.\nVerification\nCreate and read a non-sensitive test pair from the intended endpoints, change it, and confirm deletion when the task finishes. Include a controlled VM migration if the application relies on migration continuity. Record the actual values and timing observed rather than interpreting a stale pair as current guest health.\nOfficial references\nMicrosoft Learn: Data Exchange: Using key-value pairs to share information between the host and guest on Hyper-V. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:15:19+00:00", "dateModified": "2026-09-08T18:23:26+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/" }, "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-112-treat-hyper-v-key-value-exchange-as-persistent-host-visible-metadata/#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": "Treat Hyper-V key-value exchange as persistent host-visible metadata" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 219, "timeRequired": "PT1M", "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": "Data Exchange: Using key-value pairs to share information between the host and guest on Hyper-V", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/integration-services-data-exchange" } } ] } }