{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/",
        "slug": "provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities",
        "url": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/"
        },
        "title": "Provide documented seafarer, visitor, and welfare access through regulated maritime facilities",
        "summary": "Use 33 CFR 105.237 -- Maritime Security: Facilities 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": "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:14+00:00",
        "modified_at": "2026-08-27T13:09:37+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 585,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 33 CFR 105.237 -- 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.237 -- Maritime Security: Facilities",
            "url": "https://www.ecfr.gov/current/title-33/section-105.237",
            "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: Provide documented seafarer, visitor, and welfare access through regulated maritime facilities. 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.237\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.237 &#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 individuals to whom the facility owner or operator must provide the access described in this section include representatives of seafarers&#8217; welfare and labor organizations. The research record locates this support at <strong>33 CFR 105.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3))</strong>.</li>\n<li>Under 33 CFR 105, the rule requires that the facility owner or operator ensure that the access described in this section is provided through one or more of the following methods: arrangements with seafarers&#8217; welfare organizations to facilitate the access described in this section. The research record locates this support at <strong>33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4))</strong>.</li>\n</ul>\n<p>Keep the evidence boundary at these traced claims. They support a review of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces; 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. No current deployment state or change approval follows from the source alone. Validate identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators, 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.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, including exceptions?</li>\n<li>What baseline for identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators 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 credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, observed and expected states, owner, and reason for deviation.</p>\n<p>Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators, while excluding secrets and sensitive personal or topology data from ordinary tickets.</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.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3))</strong>; <strong>33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4))</strong>. Favor approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, linked to stable identifiers, time, and operator.</p>\n<p>Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-33/section-105.237\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.237 &#8212; Maritime Security: Facilities</a> — U.S. Coast Guard via eCFR</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: Provide documented seafarer, visitor, and welfare access through regulated maritime facilities. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.237 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, the individuals to whom the facility owner or operator must provide the access described in this section include representatives of seafarers’ welfare and labor organizations. The research record locates this support at 33 CFR 105.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3)).\nUnder 33 CFR 105, the rule requires that the facility owner or operator ensure that the access described in this section is provided through one or more of the following methods: arrangements with seafarers’ welfare organizations to facilitate the access described in this section. The research record locates this support at 33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4)).\n\nKeep the evidence boundary at these traced claims. They support a review of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces; 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. No current deployment state or change approval follows from the source alone. Validate identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, including exceptions?\nWhat baseline for identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators 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 credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3)); 33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4)). Favor approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, linked to stable identifiers, time, and operator.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\n33 CFR 105.237 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
        "content_markdown": "Treat this document as a focused evidence review: Provide documented seafarer, visitor, and welfare access through regulated maritime facilities. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [33 CFR 105.237 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.237) from U.S. Coast Guard via eCFR supports the following bounded statements:\n\n- Under 33 CFR 105, the individuals to whom the facility owner or operator must provide the access described in this section include representatives of seafarers’ welfare and labor organizations. The research record locates this support at 33 CFR 105.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3)).\n\n- Under 33 CFR 105, the rule requires that the facility owner or operator ensure that the access described in this section is provided through one or more of the following methods: arrangements with seafarers’ welfare organizations to facilitate the access described in this section. The research record locates this support at 33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4)).\n\nKeep the evidence boundary at these traced claims. They support a review of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces; 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. No current deployment state or change approval follows from the source alone. Validate identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators, 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.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4)), which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, including exceptions?\n\n- What baseline for identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators 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 credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, observed and expected states, owner, and reason for deviation.\n\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators, while excluding secrets and sensitive personal or topology data from ordinary tickets.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3)); 33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4)). Favor approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, linked to stable identifiers, time, and operator.\n\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\n\n## Official references\n\n- [33 CFR 105.237 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.237) — 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/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/",
                "url": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Provide documented seafarer, visitor, and welfare access through regulated maritime facilities",
                        "item": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/#article",
                "identifier": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/",
                "url": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/",
                "headline": "Provide documented seafarer, visitor, and welfare access through regulated maritime facilities",
                "description": "Use 33 CFR 105.237 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 33 CFR 105.237 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Treat this document as a focused evidence review: Provide documented seafarer, visitor, and welfare access through regulated maritime facilities. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.237 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, the individuals to whom the facility owner or operator must provide the access described in this section include representatives of seafarers’ welfare and labor organizations. The research record locates this support at 33 CFR 105.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3)).\nUnder 33 CFR 105, the rule requires that the facility owner or operator ensure that the access described in this section is provided through one or more of the following methods: arrangements with seafarers’ welfare organizations to facilitate the access described in this section. The research record locates this support at 33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4)).\n\nKeep the evidence boundary at these traced claims. They support a review of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces; 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. No current deployment state or change approval follows from the source alone. Validate identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, including exceptions?\nWhat baseline for identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators 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 credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.237(b)(3), read with 33 CFR 105.237(b) (eCFR anchor p-105.237(b)(3)); 33 CFR 105.237(d)(4), read with 33 CFR 105.237(d) (eCFR anchor p-105.237(d)(4)). Favor approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, linked to stable identifiers, time, and operator.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\n33 CFR 105.237 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
                "datePublished": "2026-08-27T12:11:14+00:00",
                "dateModified": "2026-08-27T13:09:37+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/"
                },
                "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/provide-documented-seafarer-visitor-and-welfare-access-through-regulated-maritime-facilities/#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": "Provide documented seafarer, visitor, and welfare access through regulated maritime facilities"
                },
                "articleSection": [
                    "Access Control",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Access Control",
                    "Cybersecurity",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "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/"
                    }
                ],
                "wordCount": 585,
                "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.237 -- Maritime Security: Facilities",
                    "url": "https://www.ecfr.gov/current/title-33/section-105.237"
                }
            }
        ]
    }
}