{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/xprotect-export-encryption-signature-validation/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation/",
        "slug": "xprotect-export-encryption-signature-validation",
        "url": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/xprotect-export-encryption-signature-validation/"
        },
        "title": "Check XProtect export encryption and signatures separately",
        "summary": "Treat recipient access and recording-signature verification as separate checks when preparing an XProtect evidence export.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "physical-security",
            "label": "Physical security",
            "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "video-surveillance",
                "name": "Video Surveillance",
                "url": "https://update.dsesecurity.com/topic/video-surveillance/"
            }
        ],
        "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-10-15T00:43:16+00:00",
        "modified_at": "2026-10-15T00:44:32+00:00",
        "reviewed_on": "2026-10-14",
        "reading_minutes": 2,
        "word_count": 237,
        "potentially_affected": "These details concern the cited 2026 R1 XProtect-format settings. Confirm the deployed release and recipient’s Windows playback environment before choosing an export workflow.",
        "dse_recommendation": "DSE recommends an export checklist with distinct entries for authorized footage, privacy treatment, password delivery, player compatibility, and signature results.",
        "primary_source": {
            "name": "Milestone — XProtect Smart Client 2026 R1, XProtect format settings",
            "url": "https://doc.milestonesys.com/xprotect/xprotect-smart-client/2026r1/en/xprotect-format-settings",
            "published_on": null,
            "authority": "doc.milestonesys.com"
        },
        "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>Treat recipient access and recording-signature verification as separate checks when preparing an XProtect evidence export.</p>\n<h2>Source facts</h2>\n<p>The XProtect Smart Client 2026 R1 documentation separates password encryption from digital signatures in XProtect-format exports. Encryption uses AES-256 and requires a password to open the export. Including digital signatures verifies existing recording signatures during export; a failed verification can prevent a device’s export. Recipients can verify signatures in Smart Client Player. Applying privacy masks removes recording-server signatures, and very recent recordings can have only partial signature coverage.</p>\n<p>Source: <a href=\"https://doc.milestonesys.com/xprotect/xprotect-smart-client/2026r1/en/xprotect-format-settings\">Milestone — XProtect Smart Client 2026 R1, XProtect format settings</a>.</p>\n<h2>Applicability</h2>\n<p>These details concern the cited 2026 R1 XProtect-format settings. Confirm the deployed release and recipient’s Windows playback environment before choosing an export workflow.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends an export checklist with distinct entries for authorized footage, privacy treatment, password delivery, player compatibility, and signature results. Have the case owner approve cameras and time boundaries. Deliver the password through an agreed separate channel and restrict access to the exported files. Record any missing or partial signature coverage rather than describing the package simply as verified. Preserve the original export and document subsequent handling in the case record.</p>\n<h2>Verification</h2>\n<p>Open a sample package in the intended recipient environment and check playback and signature status. Record the exact export options and outcome. These checks support operational handling; they do not establish legal admissibility.</p>\n<h2>Official reference</h2>\n<p><a href=\"https://doc.milestonesys.com/xprotect/xprotect-smart-client/2026r1/en/xprotect-format-settings\">Milestone — XProtect Smart Client 2026 R1, XProtect format settings</a>. Reviewed October 14, 2026.</p>",
        "content_text": "Treat recipient access and recording-signature verification as separate checks when preparing an XProtect evidence export.\nSource facts\nThe XProtect Smart Client 2026 R1 documentation separates password encryption from digital signatures in XProtect-format exports. Encryption uses AES-256 and requires a password to open the export. Including digital signatures verifies existing recording signatures during export; a failed verification can prevent a device’s export. Recipients can verify signatures in Smart Client Player. Applying privacy masks removes recording-server signatures, and very recent recordings can have only partial signature coverage.\nSource: Milestone — XProtect Smart Client 2026 R1, XProtect format settings.\nApplicability\nThese details concern the cited 2026 R1 XProtect-format settings. Confirm the deployed release and recipient’s Windows playback environment before choosing an export workflow.\nDSE recommendation\nDSE recommends an export checklist with distinct entries for authorized footage, privacy treatment, password delivery, player compatibility, and signature results. Have the case owner approve cameras and time boundaries. Deliver the password through an agreed separate channel and restrict access to the exported files. Record any missing or partial signature coverage rather than describing the package simply as verified. Preserve the original export and document subsequent handling in the case record.\nVerification\nOpen a sample package in the intended recipient environment and check playback and signature status. Record the exact export options and outcome. These checks support operational handling; they do not establish legal admissibility.\nOfficial reference\nMilestone — XProtect Smart Client 2026 R1, XProtect format settings. Reviewed October 14, 2026.",
        "content_markdown": "Treat recipient access and recording-signature verification as separate checks when preparing an XProtect evidence export.\n\n## Source facts\n\nThe XProtect Smart Client 2026 R1 documentation separates password encryption from digital signatures in XProtect-format exports. Encryption uses AES-256 and requires a password to open the export. Including digital signatures verifies existing recording signatures during export; a failed verification can prevent a device’s export. Recipients can verify signatures in Smart Client Player. Applying privacy masks removes recording-server signatures, and very recent recordings can have only partial signature coverage.\n\nSource: [Milestone — XProtect Smart Client 2026 R1, XProtect format settings](https://doc.milestonesys.com/xprotect/xprotect-smart-client/2026r1/en/xprotect-format-settings).\n\n## Applicability\n\nThese details concern the cited 2026 R1 XProtect-format settings. Confirm the deployed release and recipient’s Windows playback environment before choosing an export workflow.\n\n## DSE recommendation\n\nDSE recommends an export checklist with distinct entries for authorized footage, privacy treatment, password delivery, player compatibility, and signature results. Have the case owner approve cameras and time boundaries. Deliver the password through an agreed separate channel and restrict access to the exported files. Record any missing or partial signature coverage rather than describing the package simply as verified. Preserve the original export and document subsequent handling in the case record.\n\n## Verification\n\nOpen a sample package in the intended recipient environment and check playback and signature status. Record the exact export options and outcome. These checks support operational handling; they do not establish legal admissibility.\n\n## Official reference\n\n[Milestone — XProtect Smart Client 2026 R1, XProtect format settings](https://doc.milestonesys.com/xprotect/xprotect-smart-client/2026r1/en/xprotect-format-settings). Reviewed October 14, 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/xprotect-export-encryption-signature-validation/",
                "url": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-10-14"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Check XProtect export encryption and signatures separately",
                        "item": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation/#article",
                "identifier": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation/",
                "url": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation/",
                "headline": "Check XProtect export encryption and signatures separately",
                "description": "Treat recipient access and recording-signature verification as separate checks when preparing an XProtect evidence export.",
                "abstract": "Treat recipient access and recording-signature verification as separate checks when preparing an XProtect evidence export.",
                "articleBody": "Treat recipient access and recording-signature verification as separate checks when preparing an XProtect evidence export.\nSource facts\nThe XProtect Smart Client 2026 R1 documentation separates password encryption from digital signatures in XProtect-format exports. Encryption uses AES-256 and requires a password to open the export. Including digital signatures verifies existing recording signatures during export; a failed verification can prevent a device’s export. Recipients can verify signatures in Smart Client Player. Applying privacy masks removes recording-server signatures, and very recent recordings can have only partial signature coverage.\nSource: Milestone — XProtect Smart Client 2026 R1, XProtect format settings.\nApplicability\nThese details concern the cited 2026 R1 XProtect-format settings. Confirm the deployed release and recipient’s Windows playback environment before choosing an export workflow.\nDSE recommendation\nDSE recommends an export checklist with distinct entries for authorized footage, privacy treatment, password delivery, player compatibility, and signature results. Have the case owner approve cameras and time boundaries. Deliver the password through an agreed separate channel and restrict access to the exported files. Record any missing or partial signature coverage rather than describing the package simply as verified. Preserve the original export and document subsequent handling in the case record.\nVerification\nOpen a sample package in the intended recipient environment and check playback and signature status. Record the exact export options and outcome. These checks support operational handling; they do not establish legal admissibility.\nOfficial reference\nMilestone — XProtect Smart Client 2026 R1, XProtect format settings. Reviewed October 14, 2026.",
                "datePublished": "2026-10-15T00:43:16+00:00",
                "dateModified": "2026-10-15T00:44:32+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/xprotect-export-encryption-signature-validation/"
                },
                "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/xprotect-export-encryption-signature-validation/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Check XProtect export encryption and signatures separately"
                },
                "articleSection": [
                    "Video Surveillance"
                ],
                "keywords": [
                    "Video Surveillance",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Video Surveillance",
                        "url": "https://update.dsesecurity.com/topic/video-surveillance/"
                    }
                ],
                "wordCount": 237,
                "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": "Milestone — XProtect Smart Client 2026 R1, XProtect format settings",
                    "url": "https://doc.milestonesys.com/xprotect/xprotect-smart-client/2026r1/en/xprotect-format-settings"
                }
            }
        ]
    }
}