{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/build-alternate-worksite-plan-identity-connectivity-data-people/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people/",
        "slug": "build-alternate-worksite-plan-identity-connectivity-data-people",
        "url": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/build-alternate-worksite-plan-identity-connectivity-data-people/"
        },
        "title": "Build an alternate-worksite plan around identity, connectivity, data, and people",
        "summary": "An alternate location is useful only if authorized people can reach it, authenticate, communicate, obtain governed data, perform priority work, and sustain operations. Design and exercise the entire capability, not just the address.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "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": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "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-08-17T12:46:00+00:00",
        "modified_at": "2026-08-17T19:22:10+00:00",
        "reviewed_on": "2026-08-17",
        "reading_minutes": 3,
        "word_count": 613,
        "potentially_affected": "Continuity and remote-work programs; alternate facilities; personnel and delegations; identity and privileged access; devices; connectivity; applications and data; communications; suppliers; physical security; and exercise programs.",
        "dse_recommendation": "Use business-impact priorities to define alternate-worksite capability, map people and technology dependencies, prepare secure identity and connectivity paths, protect data, document activation and authority, and exercise end-to-end work.",
        "primary_source": {
            "name": "FEMA Continuity Guidance Circular",
            "url": "https://www.fema.gov/sites/default/files/documents/fema_continuity-guidance-circular_082024.pdf",
            "published_on": null,
            "authority": "Federal Emergency Management Agency"
        },
        "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": "<h2>Source facts: continuity capability combines people, facilities, communications, and information</h2>\n<p>FEMA&#8217;s <a href=\"https://www.fema.gov/sites/default/files/documents/fema_continuity-guidance-circular_082024.pdf\" target=\"_blank\" rel=\"noopener noreferrer\">Continuity Guidance Circular</a> presents continuity concepts including essential functions, orders of succession, delegations of authority, continuity facilities, communications, essential records, human capital, devolution, reconstitution, testing, training, and exercises. These elements show why an alternate facility cannot succeed as an isolated real-estate decision.</p>\n<p>NIST <a href=\"https://csrc.nist.gov/pubs/sp/800/34/r1/final\" target=\"_blank\" rel=\"noopener noreferrer\">SP 800-34 Rev. 1</a> connects information-system contingency planning to business impact analysis, preventive controls, recovery strategies, plan development, testing, training, exercises, and maintenance. It emphasizes selecting strategies according to system impact and recovery requirements.</p>\n<p>FEMA guidance often describes public-sector continuity targets and models. Those materials can inform commercial planning, but they are not automatically contractual requirements for a private organization. The business impact analysis, safety obligations, laws, contracts, insurer conditions, and actual architecture govern the plan.</p>\n\n<h2>DSE recommendation: prove the alternate site can perform priority work</h2>\n<p>Design from required outcomes: who must do which work, by when, using what information and authority, when the primary workplace or technology path is unavailable.</p>\n<ol>\n<li><strong>Define essential workflows and tolerances.</strong> Use the business impact analysis to identify priority services, minimum staffing, recovery time, acceptable backlog, maximum interruption, data needs, dependencies, peak periods, and manual alternatives. Avoid planning to reproduce every normal capability immediately.</li>\n<li><strong>Select a strategy by scenario.</strong> Compare remote work, another company facility, contracted workspace, reciprocal arrangement, mobile capability, and distributed teams against regional outage, building denial, cyber incident, carrier failure, public-health event, and staff displacement. One alternate location may share the same hazard as the primary.</li>\n<li><strong>Prepare people and authority.</strong> Maintain call trees, succession, delegations, role assignments, accessibility needs, travel and family considerations, safety, transportation, lodging, and alternates. Make essential contacts and authority records available when primary identity or document systems are unavailable.</li>\n<li><strong>Engineer identity and devices.</strong> Provide managed endpoints, phishing-resistant authentication where supported, emergency accounts with controlled custody, privileged access, software, certificates, chargers, spares, secure configuration, replacement and wipe procedures. Test first-time sign-in and recovery without relying on the unavailable office.</li>\n<li><strong>Provide diverse communications and connectivity.</strong> Validate internet, voice, collaboration, VPN or zero-trust access, DNS, identity reachability, carrier diversity, power, capacity, and support. Document degraded modes and prevent the alternate path from bypassing segmentation or monitoring.</li>\n<li><strong>Protect data and records.</strong> Identify authoritative records, offline or protected copies, synchronization, recovery point, encryption, access, printing, disposal, transport, and return. Prevent local convenience copies from becoming ungoverned long-term systems of record.</li>\n<li><strong>Exercise activation through reconstitution.</strong> Trigger notification, travel or remote activation, identity, connectivity, application access, a representative workflow, communications, shift turnover, outage support, and return to normal operations. Capture decisions, timings, failures, workarounds, and corrective actions.</li>\n</ol>\n<p>Plan for the alternate location itself to fail or become unavailable. Identify the decision point for moving to distributed work, a second location, manual service, or temporary suspension. Preserve current reservations, access instructions, keys or badges, equipment assignments, and supplier escalation without exposing the site&#8217;s security details more broadly than necessary.</p>\n<p>Include sustained operations, not only first-day activation. Exercise shift coverage, fatigue, supervision, replenishment, secure disposal, software updates, device replacement, helpdesk, privileged administration, backup jobs, incident response, mail and deliveries, financial approvals, and reconciliation of work created while systems were degraded. Set conditions for safe reconstitution at the primary site.</p>\n<p><strong>Factual boundary:</strong> The cited federal guidance provides planning models, not a universal mandate or proof that a commercial arrangement is sufficient. Employee safety, labor, accessibility, privacy, insurance, lease, regulatory, customer, and technology requirements require appropriate qualified review.</p>\n<p>Measure activation time, reachable staff, authentication success, usable capacity, essential workflow completion, data reconciliation, unplanned dependencies, and corrective-action closure. A signed contract for space is not continuity evidence; a safely exercised operating capability is.</p>\n\n<h2>Official references</h2>\n<ul>\n<li>FEMA, <a href=\"https://www.fema.gov/sites/default/files/documents/fema_continuity-guidance-circular_082024.pdf\" target=\"_blank\" rel=\"noopener noreferrer\"><em>Continuity Guidance Circular</em></a>.</li>\n<li>NIST, <a href=\"https://csrc.nist.gov/pubs/sp/800/34/r1/final\" target=\"_blank\" rel=\"noopener noreferrer\"><em>SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems</em></a>.</li>\n</ul>",
        "content_text": "Source facts: continuity capability combines people, facilities, communications, and information\nFEMA’s Continuity Guidance Circular presents continuity concepts including essential functions, orders of succession, delegations of authority, continuity facilities, communications, essential records, human capital, devolution, reconstitution, testing, training, and exercises. These elements show why an alternate facility cannot succeed as an isolated real-estate decision.\nNIST SP 800-34 Rev. 1 connects information-system contingency planning to business impact analysis, preventive controls, recovery strategies, plan development, testing, training, exercises, and maintenance. It emphasizes selecting strategies according to system impact and recovery requirements.\nFEMA guidance often describes public-sector continuity targets and models. Those materials can inform commercial planning, but they are not automatically contractual requirements for a private organization. The business impact analysis, safety obligations, laws, contracts, insurer conditions, and actual architecture govern the plan.\n\nDSE recommendation: prove the alternate site can perform priority work\nDesign from required outcomes: who must do which work, by when, using what information and authority, when the primary workplace or technology path is unavailable.\n\nDefine essential workflows and tolerances. Use the business impact analysis to identify priority services, minimum staffing, recovery time, acceptable backlog, maximum interruption, data needs, dependencies, peak periods, and manual alternatives. Avoid planning to reproduce every normal capability immediately.\nSelect a strategy by scenario. Compare remote work, another company facility, contracted workspace, reciprocal arrangement, mobile capability, and distributed teams against regional outage, building denial, cyber incident, carrier failure, public-health event, and staff displacement. One alternate location may share the same hazard as the primary.\nPrepare people and authority. Maintain call trees, succession, delegations, role assignments, accessibility needs, travel and family considerations, safety, transportation, lodging, and alternates. Make essential contacts and authority records available when primary identity or document systems are unavailable.\nEngineer identity and devices. Provide managed endpoints, phishing-resistant authentication where supported, emergency accounts with controlled custody, privileged access, software, certificates, chargers, spares, secure configuration, replacement and wipe procedures. Test first-time sign-in and recovery without relying on the unavailable office.\nProvide diverse communications and connectivity. Validate internet, voice, collaboration, VPN or zero-trust access, DNS, identity reachability, carrier diversity, power, capacity, and support. Document degraded modes and prevent the alternate path from bypassing segmentation or monitoring.\nProtect data and records. Identify authoritative records, offline or protected copies, synchronization, recovery point, encryption, access, printing, disposal, transport, and return. Prevent local convenience copies from becoming ungoverned long-term systems of record.\nExercise activation through reconstitution. Trigger notification, travel or remote activation, identity, connectivity, application access, a representative workflow, communications, shift turnover, outage support, and return to normal operations. Capture decisions, timings, failures, workarounds, and corrective actions.\n\nPlan for the alternate location itself to fail or become unavailable. Identify the decision point for moving to distributed work, a second location, manual service, or temporary suspension. Preserve current reservations, access instructions, keys or badges, equipment assignments, and supplier escalation without exposing the site’s security details more broadly than necessary.\nInclude sustained operations, not only first-day activation. Exercise shift coverage, fatigue, supervision, replenishment, secure disposal, software updates, device replacement, helpdesk, privileged administration, backup jobs, incident response, mail and deliveries, financial approvals, and reconciliation of work created while systems were degraded. Set conditions for safe reconstitution at the primary site.\nFactual boundary: The cited federal guidance provides planning models, not a universal mandate or proof that a commercial arrangement is sufficient. Employee safety, labor, accessibility, privacy, insurance, lease, regulatory, customer, and technology requirements require appropriate qualified review.\nMeasure activation time, reachable staff, authentication success, usable capacity, essential workflow completion, data reconciliation, unplanned dependencies, and corrective-action closure. A signed contract for space is not continuity evidence; a safely exercised operating capability is.\n\nOfficial references\n\nFEMA, Continuity Guidance Circular.\nNIST, SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems.",
        "content_markdown": "## Source facts: continuity capability combines people, facilities, communications, and information\n\nFEMA’s [Continuity Guidance Circular](https://www.fema.gov/sites/default/files/documents/fema_continuity-guidance-circular_082024.pdf) presents continuity concepts including essential functions, orders of succession, delegations of authority, continuity facilities, communications, essential records, human capital, devolution, reconstitution, testing, training, and exercises. These elements show why an alternate facility cannot succeed as an isolated real-estate decision.\n\nNIST [SP 800-34 Rev. 1](https://csrc.nist.gov/pubs/sp/800/34/r1/final) connects information-system contingency planning to business impact analysis, preventive controls, recovery strategies, plan development, testing, training, exercises, and maintenance. It emphasizes selecting strategies according to system impact and recovery requirements.\n\nFEMA guidance often describes public-sector continuity targets and models. Those materials can inform commercial planning, but they are not automatically contractual requirements for a private organization. The business impact analysis, safety obligations, laws, contracts, insurer conditions, and actual architecture govern the plan.\n\n## DSE recommendation: prove the alternate site can perform priority work\n\nDesign from required outcomes: who must do which work, by when, using what information and authority, when the primary workplace or technology path is unavailable.\n\n- Define essential workflows and tolerances. Use the business impact analysis to identify priority services, minimum staffing, recovery time, acceptable backlog, maximum interruption, data needs, dependencies, peak periods, and manual alternatives. Avoid planning to reproduce every normal capability immediately.\n\n- Select a strategy by scenario. Compare remote work, another company facility, contracted workspace, reciprocal arrangement, mobile capability, and distributed teams against regional outage, building denial, cyber incident, carrier failure, public-health event, and staff displacement. One alternate location may share the same hazard as the primary.\n\n- Prepare people and authority. Maintain call trees, succession, delegations, role assignments, accessibility needs, travel and family considerations, safety, transportation, lodging, and alternates. Make essential contacts and authority records available when primary identity or document systems are unavailable.\n\n- Engineer identity and devices. Provide managed endpoints, phishing-resistant authentication where supported, emergency accounts with controlled custody, privileged access, software, certificates, chargers, spares, secure configuration, replacement and wipe procedures. Test first-time sign-in and recovery without relying on the unavailable office.\n\n- Provide diverse communications and connectivity. Validate internet, voice, collaboration, VPN or zero-trust access, DNS, identity reachability, carrier diversity, power, capacity, and support. Document degraded modes and prevent the alternate path from bypassing segmentation or monitoring.\n\n- Protect data and records. Identify authoritative records, offline or protected copies, synchronization, recovery point, encryption, access, printing, disposal, transport, and return. Prevent local convenience copies from becoming ungoverned long-term systems of record.\n\n- Exercise activation through reconstitution. Trigger notification, travel or remote activation, identity, connectivity, application access, a representative workflow, communications, shift turnover, outage support, and return to normal operations. Capture decisions, timings, failures, workarounds, and corrective actions.\n\nPlan for the alternate location itself to fail or become unavailable. Identify the decision point for moving to distributed work, a second location, manual service, or temporary suspension. Preserve current reservations, access instructions, keys or badges, equipment assignments, and supplier escalation without exposing the site’s security details more broadly than necessary.\n\nInclude sustained operations, not only first-day activation. Exercise shift coverage, fatigue, supervision, replenishment, secure disposal, software updates, device replacement, helpdesk, privileged administration, backup jobs, incident response, mail and deliveries, financial approvals, and reconciliation of work created while systems were degraded. Set conditions for safe reconstitution at the primary site.\n\nFactual boundary: The cited federal guidance provides planning models, not a universal mandate or proof that a commercial arrangement is sufficient. Employee safety, labor, accessibility, privacy, insurance, lease, regulatory, customer, and technology requirements require appropriate qualified review.\n\nMeasure activation time, reachable staff, authentication success, usable capacity, essential workflow completion, data reconciliation, unplanned dependencies, and corrective-action closure. A signed contract for space is not continuity evidence; a safely exercised operating capability is.\n\n## Official references\n\n- FEMA, [Continuity Guidance Circular](https://www.fema.gov/sites/default/files/documents/fema_continuity-guidance-circular_082024.pdf).\n\n- NIST, [SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems](https://csrc.nist.gov/pubs/sp/800/34/r1/final)."
    },
    "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/build-alternate-worksite-plan-identity-connectivity-data-people/",
                "url": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-17"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Build an alternate-worksite plan around identity, connectivity, data, and people",
                        "item": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people/#article",
                "identifier": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people/",
                "url": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people/",
                "headline": "Build an alternate-worksite plan around identity, connectivity, data, and people",
                "description": "An alternate location is useful only if authorized people can reach it, authenticate, communicate, obtain governed data, perform priority work, and…",
                "abstract": "An alternate location is useful only if authorized people can reach it, authenticate, communicate, obtain governed data, perform priority work, and sustain operations. Design and exercise the entire capability, not just the address.",
                "articleBody": "Source facts: continuity capability combines people, facilities, communications, and information\nFEMA’s Continuity Guidance Circular presents continuity concepts including essential functions, orders of succession, delegations of authority, continuity facilities, communications, essential records, human capital, devolution, reconstitution, testing, training, and exercises. These elements show why an alternate facility cannot succeed as an isolated real-estate decision.\nNIST SP 800-34 Rev. 1 connects information-system contingency planning to business impact analysis, preventive controls, recovery strategies, plan development, testing, training, exercises, and maintenance. It emphasizes selecting strategies according to system impact and recovery requirements.\nFEMA guidance often describes public-sector continuity targets and models. Those materials can inform commercial planning, but they are not automatically contractual requirements for a private organization. The business impact analysis, safety obligations, laws, contracts, insurer conditions, and actual architecture govern the plan.\n\nDSE recommendation: prove the alternate site can perform priority work\nDesign from required outcomes: who must do which work, by when, using what information and authority, when the primary workplace or technology path is unavailable.\n\nDefine essential workflows and tolerances. Use the business impact analysis to identify priority services, minimum staffing, recovery time, acceptable backlog, maximum interruption, data needs, dependencies, peak periods, and manual alternatives. Avoid planning to reproduce every normal capability immediately.\nSelect a strategy by scenario. Compare remote work, another company facility, contracted workspace, reciprocal arrangement, mobile capability, and distributed teams against regional outage, building denial, cyber incident, carrier failure, public-health event, and staff displacement. One alternate location may share the same hazard as the primary.\nPrepare people and authority. Maintain call trees, succession, delegations, role assignments, accessibility needs, travel and family considerations, safety, transportation, lodging, and alternates. Make essential contacts and authority records available when primary identity or document systems are unavailable.\nEngineer identity and devices. Provide managed endpoints, phishing-resistant authentication where supported, emergency accounts with controlled custody, privileged access, software, certificates, chargers, spares, secure configuration, replacement and wipe procedures. Test first-time sign-in and recovery without relying on the unavailable office.\nProvide diverse communications and connectivity. Validate internet, voice, collaboration, VPN or zero-trust access, DNS, identity reachability, carrier diversity, power, capacity, and support. Document degraded modes and prevent the alternate path from bypassing segmentation or monitoring.\nProtect data and records. Identify authoritative records, offline or protected copies, synchronization, recovery point, encryption, access, printing, disposal, transport, and return. Prevent local convenience copies from becoming ungoverned long-term systems of record.\nExercise activation through reconstitution. Trigger notification, travel or remote activation, identity, connectivity, application access, a representative workflow, communications, shift turnover, outage support, and return to normal operations. Capture decisions, timings, failures, workarounds, and corrective actions.\n\nPlan for the alternate location itself to fail or become unavailable. Identify the decision point for moving to distributed work, a second location, manual service, or temporary suspension. Preserve current reservations, access instructions, keys or badges, equipment assignments, and supplier escalation without exposing the site’s security details more broadly than necessary.\nInclude sustained operations, not only first-day activation. Exercise shift coverage, fatigue, supervision, replenishment, secure disposal, software updates, device replacement, helpdesk, privileged administration, backup jobs, incident response, mail and deliveries, financial approvals, and reconciliation of work created while systems were degraded. Set conditions for safe reconstitution at the primary site.\nFactual boundary: The cited federal guidance provides planning models, not a universal mandate or proof that a commercial arrangement is sufficient. Employee safety, labor, accessibility, privacy, insurance, lease, regulatory, customer, and technology requirements require appropriate qualified review.\nMeasure activation time, reachable staff, authentication success, usable capacity, essential workflow completion, data reconciliation, unplanned dependencies, and corrective-action closure. A signed contract for space is not continuity evidence; a safely exercised operating capability is.\n\nOfficial references\n\nFEMA, Continuity Guidance Circular.\nNIST, SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems.",
                "datePublished": "2026-08-17T12:46:00+00:00",
                "dateModified": "2026-08-17T19:22:10+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/build-alternate-worksite-plan-identity-connectivity-data-people/"
                },
                "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/build-alternate-worksite-plan-identity-connectivity-data-people/#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": "Build an alternate-worksite plan around identity, connectivity, data, and people"
                },
                "articleSection": [
                    "Business Continuity",
                    "Cybersecurity",
                    "IT"
                ],
                "keywords": [
                    "Business Continuity",
                    "Cybersecurity",
                    "IT",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 613,
                "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": "FEMA Continuity Guidance Circular",
                    "url": "https://www.fema.gov/sites/default/files/documents/fema_continuity-guidance-circular_082024.pdf"
                }
            }
        ]
    }
}