{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/keep-approved-maritime-security-compliance-documents-available-and-protected/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected/",
        "slug": "keep-approved-maritime-security-compliance-documents-available-and-protected",
        "url": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/keep-approved-maritime-security-compliance-documents-available-and-protected/"
        },
        "title": "Keep approved maritime-security compliance documents available and protected",
        "summary": "Use 33 CFR 105.120 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "playbook",
            "name": "Playbook"
        },
        "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": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "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-08-27T12:10:46+00:00",
        "modified_at": "2026-08-27T13:09:38+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 611,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 33 CFR 105.120 -- Maritime Security: Facilities",
        "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": "33 CFR 105.120 -- Maritime Security: Facilities",
            "url": "https://www.ecfr.gov/current/title-33/section-105.120",
            "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>Keep this document to one review outcome: Keep approved maritime-security compliance documents available and protected. 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-33/section-105.120\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.120 &#8212; Maritime Security: Facilities</a> from U.S. Coast Guard via eCFR supports the following bounded statements:</p>\n<ul>\n<li>Under 33 CFR 105, a covered facility must keep its approved Facility Security Plan, approved revisions or amendments, and a COTP approval letter dated within the last five years available at the facility and to the Coast Guard on request. The research record locates this support at <strong>33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a))</strong>.</li>\n<li>Under 33 CFR 105, a facility awaiting FSP approval may continue operating under its submitted plan when it holds the COTP acknowledgment described in paragraph (b) and remains compliant with that submitted plan. The research record locates this support at <strong>33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b))</strong>.</li>\n</ul>\n<p>Keep the evidence boundary at these traced claims. They support a review of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths; they do not support conclusions outside the source&#8217;s stated conditions.</p>\n<h2>What the source does not establish</h2>\n<p>Applies only to facilities within 33 CFR part 105 and the cited section. Confirm Coast Guard jurisdiction, the approved Facility Security Plan, the current MARSEC level, and any approved alternatives; this is not legal advice or a universal facility-design standard. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?</li>\n<li>What baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel 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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response 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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a))</strong>; <strong>33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b))</strong>. Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.</p>\n<p>Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-33/section-105.120\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.120 &#8212; Maritime Security: Facilities</a> — U.S. Coast Guard via eCFR</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Keep approved maritime-security compliance documents available and protected. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.120 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, a covered facility must keep its approved Facility Security Plan, approved revisions or amendments, and a COTP approval letter dated within the last five years available at the facility and to the Coast Guard on request. The research record locates this support at 33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a)).\nUnder 33 CFR 105, a facility awaiting FSP approval may continue operating under its submitted plan when it holds the COTP acknowledgment described in paragraph (b) and remains compliant with that submitted plan. The research record locates this support at 33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b)).\n\nKeep the evidence boundary at these traced claims. They support a review of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nApplies only to facilities within 33 CFR part 105 and the cited section. Confirm Coast Guard jurisdiction, the approved Facility Security Plan, the current MARSEC level, and any approved alternatives; this is not legal advice or a universal facility-design standard. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?\nWhat baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel 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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response 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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel and sanitize protected material before retention.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a)); 33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\n33 CFR 105.120 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
        "content_markdown": "Keep this document to one review outcome: Keep approved maritime-security compliance documents available and protected. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [33 CFR 105.120 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.120) from U.S. Coast Guard via eCFR supports the following bounded statements:\n\n- Under 33 CFR 105, a covered facility must keep its approved Facility Security Plan, approved revisions or amendments, and a COTP approval letter dated within the last five years available at the facility and to the Coast Guard on request. The research record locates this support at 33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a)).\n\n- Under 33 CFR 105, a facility awaiting FSP approval may continue operating under its submitted plan when it holds the COTP acknowledgment described in paragraph (b) and remains compliant with that submitted plan. The research record locates this support at 33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b)).\n\nKeep the evidence boundary at these traced claims. They support a review of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths; they do not support conclusions outside the source’s stated conditions.\n\n## What the source does not establish\n\nApplies only to facilities within 33 CFR part 105 and the cited section. Confirm Coast Guard jurisdiction, the approved Facility Security Plan, the current MARSEC level, and any approved alternatives; this is not legal advice or a universal facility-design standard. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at 33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b)), which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?\n\n- What baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel 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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response 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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel and sanitize protected material before retention.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a)); 33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.\n\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\n\n## Official references\n\n- [33 CFR 105.120 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.120) — U.S. Coast Guard 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/keep-approved-maritime-security-compliance-documents-available-and-protected/",
                "url": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Keep approved maritime-security compliance documents available and protected",
                        "item": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected/#article",
                "identifier": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected/",
                "url": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected/",
                "headline": "Keep approved maritime-security compliance documents available and protected",
                "description": "Use 33 CFR 105.120 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 33 CFR 105.120 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Keep approved maritime-security compliance documents available and protected. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.120 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, a covered facility must keep its approved Facility Security Plan, approved revisions or amendments, and a COTP approval letter dated within the last five years available at the facility and to the Coast Guard on request. The research record locates this support at 33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a)).\nUnder 33 CFR 105, a facility awaiting FSP approval may continue operating under its submitted plan when it holds the COTP acknowledgment described in paragraph (b) and remains compliant with that submitted plan. The research record locates this support at 33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b)).\n\nKeep the evidence boundary at these traced claims. They support a review of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nApplies only to facilities within 33 CFR part 105 and the cited section. Confirm Coast Guard jurisdiction, the approved Facility Security Plan, the current MARSEC level, and any approved alternatives; this is not legal advice or a universal facility-design standard. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?\nWhat baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel 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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response 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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel and sanitize protected material before retention.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.120(a), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(a)); 33 CFR 105.120(b), read with the unnumbered introductory paragraph of 33 CFR 105.120 (eCFR anchor p-105.120(b)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\n33 CFR 105.120 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
                "datePublished": "2026-08-27T12:10:46+00:00",
                "dateModified": "2026-08-27T13:09:38+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/keep-approved-maritime-security-compliance-documents-available-and-protected/"
                },
                "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/keep-approved-maritime-security-compliance-documents-available-and-protected/#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": "Keep approved maritime-security compliance documents available and protected"
                },
                "articleSection": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance"
                ],
                "keywords": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Access Control",
                        "url": "https://update.dsesecurity.com/topic/access-control/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Video Surveillance",
                        "url": "https://update.dsesecurity.com/topic/video-surveillance/"
                    }
                ],
                "wordCount": 611,
                "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": "33 CFR 105.120 -- Maritime Security: Facilities",
                    "url": "https://www.ecfr.gov/current/title-33/section-105.120"
                }
            }
        ]
    }
}