{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/submit-system-specific-records-storage-fire-certification-evidence-to-nara/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara/",
        "slug": "submit-system-specific-records-storage-fire-certification-evidence-to-nara",
        "url": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/submit-system-specific-records-storage-fire-certification-evidence-to-nara/"
        },
        "title": "Submit system-specific records-storage fire certification evidence to NARA",
        "summary": "Use 36 CFR 1234.32 - Fire-safety system certification to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "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": "access-control",
                "name": "Access Control",
                "url": "https://update.dsesecurity.com/topic/access-control/"
            },
            {
                "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/"
            }
        ],
        "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-27T12:11:29+00:00",
        "modified_at": "2026-08-27T13:07:00+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 620,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 36 CFR 1234.32 - Fire-safety system certification",
        "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": "36 CFR 1234.32 - Fire-safety system certification",
            "url": "https://www.ecfr.gov/current/title-36/section-1234.32",
            "published_on": null,
            "authority": "www.ecfr.gov"
        },
        "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 this document as a focused evidence review: Submit system-specific records-storage fire certification evidence to NARA. 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://www.ecfr.gov/current/title-36/section-1234.32\" target=\"_blank\" rel=\"noopener noreferrer\">36 CFR 1234.32 &#8211; Fire-safety system certification</a> from National Archives and Records Administration via eCFR supports the following bounded statements:</p>\n<ul>\n<li>Under 36 CFR 1234, the rule requires that the documentation demonstrate how that system meets the requirement in section 1234.12(s) through: a report under seal of a licensed fire protection engineer that details the characteristics of the system. The research record locates this support at <strong>36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii))</strong>.</li>\n<li>Under 36 CFR 1234, the rule requires that the documentation demonstrate how that system meets the requirement in section 1234.12(s) through: a statement that the facility is using a NARA certified system as described in Appendix B to this part. The research record locates this support at <strong>36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1))</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths and the conditions the source actually describes.</p>\n<h2>What the source does not establish</h2>\n<p>Federal records-storage regulation; certification path, live-fire or modeling evidence, facility changes, system type, NARA approval, and incorporated standards require qualified review. It does not establish a deployment&#8217;s current state, authorize a production change, prove compliance, or show that identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders are healthy. Documented options are review inputs, not universal mandates.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, including exceptions?</li>\n<li>What baseline for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders must accompany the source-specific observation?</li>\n<li>Which success, stop, and escalation criteria are written before testing begins?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.</p>\n<p>If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>Keep the source locations <strong>36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii))</strong>; <strong>36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1))</strong> adjacent to the sanitized artifacts used for comparison. Prefer facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions, with enough identity and timing data for an independent recheck.</p>\n<p>Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today&#8217;s observation is not a continuing guarantee.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-36/section-1234.32\" target=\"_blank\" rel=\"noopener noreferrer\">36 CFR 1234.32 &#8211; Fire-safety system certification</a> — National Archives and Records Administration via eCFR</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: Submit system-specific records-storage fire certification evidence to NARA. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 36 CFR 1234.32 – Fire-safety system certification from National Archives and Records Administration via eCFR supports the following bounded statements:\n\nUnder 36 CFR 1234, the rule requires that the documentation demonstrate how that system meets the requirement in section 1234.12(s) through: a report under seal of a licensed fire protection engineer that details the characteristics of the system. The research record locates this support at 36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii)).\nUnder 36 CFR 1234, the rule requires that the documentation demonstrate how that system meets the requirement in section 1234.12(s) through: a statement that the facility is using a NARA certified system as described in Appendix B to this part. The research record locates this support at 36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths and the conditions the source actually describes.\nWhat the source does not establish\nFederal records-storage regulation; certification path, live-fire or modeling evidence, facility changes, system type, NARA approval, and incorporated standards require qualified review. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders are healthy. Documented options are review inputs, not universal mandates.\nApplicability questions\n\nFor source statement 1 at 36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, including exceptions?\nWhat baseline for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and sanitize protected material before retention.\nVerification and evidence\nKeep the source locations 36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii)); 36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1)) adjacent to the sanitized artifacts used for comparison. Prefer facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions, with enough identity and timing data for an independent recheck.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\n36 CFR 1234.32 – Fire-safety system certification — National Archives and Records Administration via eCFR",
        "content_markdown": "Treat this document as a focused evidence review: Submit system-specific records-storage fire certification evidence to NARA. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [36 CFR 1234.32 – Fire-safety system certification](https://www.ecfr.gov/current/title-36/section-1234.32) from National Archives and Records Administration via eCFR supports the following bounded statements:\n\n- Under 36 CFR 1234, the rule requires that the documentation demonstrate how that system meets the requirement in section 1234.12(s) through: a report under seal of a licensed fire protection engineer that details the characteristics of the system. The research record locates this support at 36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii)).\n\n- Under 36 CFR 1234, the rule requires that the documentation demonstrate how that system meets the requirement in section 1234.12(s) through: a statement that the facility is using a NARA certified system as described in Appendix B to this part. The research record locates this support at 36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths and the conditions the source actually describes.\n\n## What the source does not establish\n\nFederal records-storage regulation; certification path, live-fire or modeling evidence, facility changes, system type, NARA approval, and incorporated standards require qualified review. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders are healthy. Documented options are review inputs, not universal mandates.\n\n## Applicability questions\n\n- For source statement 1 at 36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1)), which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, including exceptions?\n\n- What baseline for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders must accompany the source-specific observation?\n\n- Which success, stop, and escalation criteria are written before testing begins?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\n\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and sanitize protected material before retention.\n\n## Verification and evidence\n\nKeep the source locations 36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii)); 36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1)) adjacent to the sanitized artifacts used for comparison. Prefer facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions, with enough identity and timing data for an independent recheck.\n\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\n\n## Official references\n\n- [36 CFR 1234.32 – Fire-safety system certification](https://www.ecfr.gov/current/title-36/section-1234.32) — National Archives and Records Administration via eCFR"
    },
    "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/submit-system-specific-records-storage-fire-certification-evidence-to-nara/",
                "url": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Submit system-specific records-storage fire certification evidence to NARA",
                        "item": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara/#article",
                "identifier": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara/",
                "url": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara/",
                "headline": "Submit system-specific records-storage fire certification evidence to NARA",
                "description": "Use 36 CFR 1234.32 - Fire-safety system certification to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 36 CFR 1234.32 - Fire-safety system certification to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Treat this document as a focused evidence review: Submit system-specific records-storage fire certification evidence to NARA. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 36 CFR 1234.32 – Fire-safety system certification from National Archives and Records Administration via eCFR supports the following bounded statements:\n\nUnder 36 CFR 1234, the rule requires that the documentation demonstrate how that system meets the requirement in section 1234.12(s) through: a report under seal of a licensed fire protection engineer that details the characteristics of the system. The research record locates this support at 36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii)).\nUnder 36 CFR 1234, the rule requires that the documentation demonstrate how that system meets the requirement in section 1234.12(s) through: a statement that the facility is using a NARA certified system as described in Appendix B to this part. The research record locates this support at 36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths and the conditions the source actually describes.\nWhat the source does not establish\nFederal records-storage regulation; certification path, live-fire or modeling evidence, facility changes, system type, NARA approval, and incorporated standards require qualified review. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders are healthy. Documented options are review inputs, not universal mandates.\nApplicability questions\n\nFor source statement 1 at 36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, including exceptions?\nWhat baseline for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and sanitize protected material before retention.\nVerification and evidence\nKeep the source locations 36 CFR 1234.32(a)(3)(ii), read with 36 CFR 1234.32(a)(3) and 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(3)(ii)); 36 CFR 1234.32(a)(1), read with 36 CFR 1234.32(a) (eCFR anchor p-1234.32(a)(1)) adjacent to the sanitized artifacts used for comparison. Prefer facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions, with enough identity and timing data for an independent recheck.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\n36 CFR 1234.32 – Fire-safety system certification — National Archives and Records Administration via eCFR",
                "datePublished": "2026-08-27T12:11:29+00:00",
                "dateModified": "2026-08-27T13:07:00+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/submit-system-specific-records-storage-fire-certification-evidence-to-nara/"
                },
                "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/submit-system-specific-records-storage-fire-certification-evidence-to-nara/#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": "Submit system-specific records-storage fire certification evidence to NARA"
                },
                "articleSection": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Access Control",
                        "url": "https://update.dsesecurity.com/topic/access-control/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    }
                ],
                "wordCount": 620,
                "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": "36 CFR 1234.32 - Fire-safety system certification",
                    "url": "https://www.ecfr.gov/current/title-36/section-1234.32"
                }
            }
        ]
    }
}