{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/screen-people-baggage-and-stores-entering-cruise-ship-terminals/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals/",
        "slug": "screen-people-baggage-and-stores-entering-cruise-ship-terminals",
        "url": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/screen-people-baggage-and-stores-entering-cruise-ship-terminals/"
        },
        "title": "Screen people, baggage, and stores entering cruise-ship terminals",
        "summary": "Use 33 CFR 105.290 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "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:02+00:00",
        "modified_at": "2026-08-27T13:09:38+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 601,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 33 CFR 105.290 -- 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.290 -- Maritime Security: Facilities",
            "url": "https://www.ecfr.gov/current/title-33/section-105.290",
            "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 connect an official requirement or behavior to observable evidence: Screen people, baggage, and stores entering cruise-ship terminals. 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.290\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.290 &#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 rule requires that when a provision is fulfilled by a vessel, the applicable section of the terminal security program (TSP) refer to that fact. The research record locates this support at <strong>33 CFR 105.290(a) (eCFR anchor p-105.290(a))</strong>.</li>\n<li>Under 33 CFR 105, the rule requires that at all MARSEC Levels, in coordination with a vessel moored at the facility, the facility owner or operator ensure the following security measures: provide additional security personnel to designated holding, waiting, or embarkation areas within the facility&#8217;s secure area. The research record locates this support at <strong>33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d))</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces 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 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.290(a) (eCFR anchor p-105.290(a))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d))</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. Use a two-person review for the source interpretation and the resulting operational decision. 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>Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators. Handle credentials, keys, recovery data, and personal information through approved secure channels.</p>\n<h2>Verification and evidence</h2>\n<p>Keep the source locations <strong>33 CFR 105.290(a) (eCFR anchor p-105.290(a))</strong>; <strong>33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d))</strong> adjacent to the sanitized artifacts used for comparison. Prefer approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, with enough identity and timing data for an independent recheck.</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.290\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.290 &#8212; Maritime Security: Facilities</a> — U.S. Coast Guard via eCFR</li>\n</ul>",
        "content_text": "Use this document to connect an official requirement or behavior to observable evidence: Screen people, baggage, and stores entering cruise-ship terminals. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.290 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, the rule requires that when a provision is fulfilled by a vessel, the applicable section of the terminal security program (TSP) refer to that fact. The research record locates this support at 33 CFR 105.290(a) (eCFR anchor p-105.290(a)).\nUnder 33 CFR 105, the rule requires that at all MARSEC Levels, in coordination with a vessel moored at the facility, the facility owner or operator ensure the following security measures: provide additional security personnel to designated holding, waiting, or embarkation areas within the facility’s secure area. The research record locates this support at 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces 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 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.290(a) (eCFR anchor p-105.290(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)), 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. Use a two-person review for the source interpretation and the resulting operational decision. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nKeep the source locations 33 CFR 105.290(a) (eCFR anchor p-105.290(a)); 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)) adjacent to the sanitized artifacts used for comparison. Prefer approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, with enough identity and timing data for an independent recheck.\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.290 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
        "content_markdown": "Use this document to connect an official requirement or behavior to observable evidence: Screen people, baggage, and stores entering cruise-ship terminals. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [33 CFR 105.290 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.290) from U.S. Coast Guard via eCFR supports the following bounded statements:\n\n- Under 33 CFR 105, the rule requires that when a provision is fulfilled by a vessel, the applicable section of the terminal security program (TSP) refer to that fact. The research record locates this support at 33 CFR 105.290(a) (eCFR anchor p-105.290(a)).\n\n- Under 33 CFR 105, the rule requires that at all MARSEC Levels, in coordination with a vessel moored at the facility, the facility owner or operator ensure the following security measures: provide additional security personnel to designated holding, waiting, or embarkation areas within the facility’s secure area. The research record locates this support at 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces 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 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.290(a) (eCFR anchor p-105.290(a)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)), 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. Use a two-person review for the source interpretation and the resulting operational decision. 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\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nKeep the source locations 33 CFR 105.290(a) (eCFR anchor p-105.290(a)); 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)) adjacent to the sanitized artifacts used for comparison. Prefer approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, with enough identity and timing data for an independent recheck.\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.290 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.290) — 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/screen-people-baggage-and-stores-entering-cruise-ship-terminals/",
                "url": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Screen people, baggage, and stores entering cruise-ship terminals",
                        "item": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals/#article",
                "identifier": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals/",
                "url": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals/",
                "headline": "Screen people, baggage, and stores entering cruise-ship terminals",
                "description": "Use 33 CFR 105.290 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 33 CFR 105.290 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to connect an official requirement or behavior to observable evidence: Screen people, baggage, and stores entering cruise-ship terminals. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.290 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, the rule requires that when a provision is fulfilled by a vessel, the applicable section of the terminal security program (TSP) refer to that fact. The research record locates this support at 33 CFR 105.290(a) (eCFR anchor p-105.290(a)).\nUnder 33 CFR 105, the rule requires that at all MARSEC Levels, in coordination with a vessel moored at the facility, the facility owner or operator ensure the following security measures: provide additional security personnel to designated holding, waiting, or embarkation areas within the facility’s secure area. The research record locates this support at 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces 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 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.290(a) (eCFR anchor p-105.290(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)), 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. Use a two-person review for the source interpretation and the resulting operational decision. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nKeep the source locations 33 CFR 105.290(a) (eCFR anchor p-105.290(a)); 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)) adjacent to the sanitized artifacts used for comparison. Prefer approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, with enough identity and timing data for an independent recheck.\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.290 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
                "datePublished": "2026-08-27T12:11:02+00:00",
                "dateModified": "2026-08-27T13:09:38+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/screen-people-baggage-and-stores-entering-cruise-ship-terminals/"
                },
                "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/screen-people-baggage-and-stores-entering-cruise-ship-terminals/#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": "Screen people, baggage, and stores entering cruise-ship terminals"
                },
                "articleSection": [
                    "Access Control",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Access Control",
                    "Cybersecurity",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "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": 601,
                "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.290 -- Maritime Security: Facilities",
                    "url": "https://www.ecfr.gov/current/title-33/section-105.290"
                }
            }
        ]
    }
}