{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/",
        "slug": "monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity",
        "url": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/"
        },
        "title": "Monitor maritime approaches, access points, restricted areas, and waterside activity",
        "summary": "Use 33 CFR 105.275 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "briefing",
            "name": "Briefing"
        },
        "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:11:05+00:00",
        "modified_at": "2026-08-27T13:09:38+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 563,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 33 CFR 105.275 -- 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.275 -- Maritime Security: Facilities",
            "url": "https://www.ecfr.gov/current/title-33/section-105.275",
            "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>Use this document to resolve one bounded operational decision: Monitor maritime approaches, access points, restricted areas, and waterside activity. 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.275\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.275 &#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, the approved FSP must provide continuous monitoring of the facility and its landward and waterside approaches through the specified combination of lighting, personnel, patrols, intrusion detection, or surveillance equipment. The research record locates this support at <strong>33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1))</strong>.</li>\n<li>Under 33 CFR 105, the approved FSP&#8217;s continuous-monitoring capability must cover restricted areas within the facility. The research record locates this support at <strong>33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2))</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows and the conditions the source actually describes.</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. No current deployment state or change approval follows from the source alone. Validate identity, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring, and treat examples or options as conditional inputs rather than defaults.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows, including exceptions?</li>\n<li>What baseline for identity, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring 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 cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows, 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, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>Keep the source locations <strong>33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1))</strong>; <strong>33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2))</strong> adjacent to the sanitized artifacts used for comparison. Prefer device and firmware inventory, stream tests, retention observations, access logs, export tests, time alignment, and failure alarms, 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-33/section-105.275\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.275 &#8212; Maritime Security: Facilities</a> — U.S. Coast Guard via eCFR</li>\n</ul>",
        "content_text": "Use this document to resolve one bounded operational decision: Monitor maritime approaches, access points, restricted areas, and waterside activity. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.275 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, the approved FSP must provide continuous monitoring of the facility and its landward and waterside approaches through the specified combination of lighting, personnel, patrols, intrusion detection, or surveillance equipment. The research record locates this support at 33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1)).\nUnder 33 CFR 105, the approved FSP’s continuous-monitoring capability must cover restricted areas within the facility. The research record locates this support at 33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows and the conditions the source actually describes.\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. No current deployment state or change approval follows from the source alone. Validate identity, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows, including exceptions?\nWhat baseline for identity, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring 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 cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows, 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, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring and sanitize protected material before retention.\nVerification and evidence\nKeep the source locations 33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1)); 33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2)) adjacent to the sanitized artifacts used for comparison. Prefer device and firmware inventory, stream tests, retention observations, access logs, export tests, time alignment, and failure alarms, 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\n33 CFR 105.275 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
        "content_markdown": "Use this document to resolve one bounded operational decision: Monitor maritime approaches, access points, restricted areas, and waterside activity. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [33 CFR 105.275 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.275) from U.S. Coast Guard via eCFR supports the following bounded statements:\n\n- Under 33 CFR 105, the approved FSP must provide continuous monitoring of the facility and its landward and waterside approaches through the specified combination of lighting, personnel, patrols, intrusion detection, or surveillance equipment. The research record locates this support at 33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1)).\n\n- Under 33 CFR 105, the approved FSP’s continuous-monitoring capability must cover restricted areas within the facility. The research record locates this support at 33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows and the conditions the source actually describes.\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. No current deployment state or change approval follows from the source alone. Validate identity, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring, and treat examples or options as conditional inputs rather than defaults.\n\n## Applicability questions\n\n- For source statement 1 at 33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2)), which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows, including exceptions?\n\n- What baseline for identity, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring 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 cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows, 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, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring and sanitize protected material before retention.\n\n## Verification and evidence\n\nKeep the source locations 33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1)); 33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2)) adjacent to the sanitized artifacts used for comparison. Prefer device and firmware inventory, stream tests, retention observations, access logs, export tests, time alignment, and failure alarms, 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- [33 CFR 105.275 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.275) — 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/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/",
                "url": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Monitor maritime approaches, access points, restricted areas, and waterside activity",
                        "item": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/#article",
                "identifier": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/",
                "url": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/",
                "headline": "Monitor maritime approaches, access points, restricted areas, and waterside activity",
                "description": "Use 33 CFR 105.275 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 33 CFR 105.275 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to resolve one bounded operational decision: Monitor maritime approaches, access points, restricted areas, and waterside activity. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.275 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, the approved FSP must provide continuous monitoring of the facility and its landward and waterside approaches through the specified combination of lighting, personnel, patrols, intrusion detection, or surveillance equipment. The research record locates this support at 33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1)).\nUnder 33 CFR 105, the approved FSP’s continuous-monitoring capability must cover restricted areas within the facility. The research record locates this support at 33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows and the conditions the source actually describes.\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. No current deployment state or change approval follows from the source alone. Validate identity, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows, including exceptions?\nWhat baseline for identity, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring 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 cameras, encoders, recorders, video-management services, storage, users, exports, analytics, and monitoring workflows, 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, DNS where used, time, networks, storage, certificates, power, privacy controls, and monitoring and sanitize protected material before retention.\nVerification and evidence\nKeep the source locations 33 CFR 105.275(a)(1), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(1)); 33 CFR 105.275(a)(2), read with 33 CFR 105.275(a) (eCFR anchor p-105.275(a)(2)) adjacent to the sanitized artifacts used for comparison. Prefer device and firmware inventory, stream tests, retention observations, access logs, export tests, time alignment, and failure alarms, 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\n33 CFR 105.275 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
                "datePublished": "2026-08-27T12:11:05+00:00",
                "dateModified": "2026-08-27T13:09:38+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/"
                },
                "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/monitor-maritime-approaches-access-points-restricted-areas-and-waterside-activity/#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": "Monitor maritime approaches, access points, restricted areas, and waterside activity"
                },
                "articleSection": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance"
                ],
                "keywords": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance",
                    "Briefing",
                    "Advisory priority"
                ],
                "genre": "Briefing",
                "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": 563,
                "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.275 -- Maritime Security: Facilities",
                    "url": "https://www.ecfr.gov/current/title-33/section-105.275"
                }
            }
        ]
    }
}