{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/",
        "slug": "publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening",
        "url": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/"
        },
        "title": "Publish and control a prohibited-items list for cruise-terminal screening",
        "summary": "Use 33 CFR 105.515 -- 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:10:49+00:00",
        "modified_at": "2026-08-27T13:09:38+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 565,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 33 CFR 105.515 -- 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.515 -- Maritime Security: Facilities",
            "url": "https://www.ecfr.gov/current/title-33/section-105.515",
            "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: Publish and control a prohibited-items list for cruise-terminal screening. 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.515\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.515 &#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 the owner or operator of a cruise ship terminal obtain from the Coast Guard and maintain a Prohibited Items List (PIL) consisting of dangerous substances and devices for purposes of section 105.290(a). The research record locates this support at <strong>33 CFR 105.515(a) (eCFR anchor p-105.515(a))</strong>.</li>\n<li>Under 33 CFR 105, the rule requires that facility personnel report the discovery of a prohibited item introduced by violating security measures at a cruise ship terminal as a breach of security in accordance with section 101.305(b) of this subchapter. The research record locates this support at <strong>33 CFR 105.515(d) (eCFR anchor p-105.515(d))</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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators 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.515(a) (eCFR anchor p-105.515(a))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>33 CFR 105.515(d) (eCFR anchor p-105.515(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. 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>An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators before and after the test, and store only sanitized operational evidence.</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.515(a) (eCFR anchor p-105.515(a))</strong>; <strong>33 CFR 105.515(d) (eCFR anchor p-105.515(d))</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>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.515\" target=\"_blank\" rel=\"noopener noreferrer\">33 CFR 105.515 &#8212; Maritime Security: Facilities</a> — U.S. Coast Guard via eCFR</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: Publish and control a prohibited-items list for cruise-terminal screening. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.515 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, the rule requires that the owner or operator of a cruise ship terminal obtain from the Coast Guard and maintain a Prohibited Items List (PIL) consisting of dangerous substances and devices for purposes of section 105.290(a). The research record locates this support at 33 CFR 105.515(a) (eCFR anchor p-105.515(a)).\nUnder 33 CFR 105, the rule requires that facility personnel report the discovery of a prohibited item introduced by violating security measures at a cruise ship terminal as a breach of security in accordance with section 101.305(b) of this subchapter. The research record locates this support at 33 CFR 105.515(d) (eCFR anchor p-105.515(d)).\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.515(a) (eCFR anchor p-105.515(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.515(d) (eCFR anchor p-105.515(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. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.515(a) (eCFR anchor p-105.515(a)); 33 CFR 105.515(d) (eCFR anchor p-105.515(d)). Favor approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, linked to stable identifiers, time, and operator.\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.515 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
        "content_markdown": "Treat this document as a focused evidence review: Publish and control a prohibited-items list for cruise-terminal screening. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [33 CFR 105.515 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.515) from U.S. Coast Guard via eCFR supports the following bounded statements:\n\n- Under 33 CFR 105, the rule requires that the owner or operator of a cruise ship terminal obtain from the Coast Guard and maintain a Prohibited Items List (PIL) consisting of dangerous substances and devices for purposes of section 105.290(a). The research record locates this support at 33 CFR 105.515(a) (eCFR anchor p-105.515(a)).\n\n- Under 33 CFR 105, the rule requires that facility personnel report the discovery of a prohibited item introduced by violating security measures at a cruise ship terminal as a breach of security in accordance with section 101.305(b) of this subchapter. The research record locates this support at 33 CFR 105.515(d) (eCFR anchor p-105.515(d)).\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at 33 CFR 105.515(a) (eCFR anchor p-105.515(a)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 33 CFR 105.515(d) (eCFR anchor p-105.515(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. 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\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators before and after the test, and store only sanitized operational evidence.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.515(a) (eCFR anchor p-105.515(a)); 33 CFR 105.515(d) (eCFR anchor p-105.515(d)). Favor approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, linked to stable identifiers, time, and operator.\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.515 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.515) — 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/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/",
                "url": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Publish and control a prohibited-items list for cruise-terminal screening",
                        "item": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/#article",
                "identifier": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/",
                "url": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/",
                "headline": "Publish and control a prohibited-items list for cruise-terminal screening",
                "description": "Use 33 CFR 105.515 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 33 CFR 105.515 -- 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: Publish and control a prohibited-items list for cruise-terminal screening. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.515 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:\n\nUnder 33 CFR 105, the rule requires that the owner or operator of a cruise ship terminal obtain from the Coast Guard and maintain a Prohibited Items List (PIL) consisting of dangerous substances and devices for purposes of section 105.290(a). The research record locates this support at 33 CFR 105.515(a) (eCFR anchor p-105.515(a)).\nUnder 33 CFR 105, the rule requires that facility personnel report the discovery of a prohibited item introduced by violating security measures at a cruise ship terminal as a breach of security in accordance with section 101.305(b) of this subchapter. The research record locates this support at 33 CFR 105.515(d) (eCFR anchor p-105.515(d)).\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.515(a) (eCFR anchor p-105.515(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.515(d) (eCFR anchor p-105.515(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. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.515(a) (eCFR anchor p-105.515(a)); 33 CFR 105.515(d) (eCFR anchor p-105.515(d)). Favor approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, linked to stable identifiers, time, and operator.\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.515 — Maritime Security: Facilities — U.S. Coast Guard via eCFR",
                "datePublished": "2026-08-27T12:10:49+00:00",
                "dateModified": "2026-08-27T13:09:38+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/"
                },
                "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/publish-and-control-a-prohibited-items-list-for-cruise-terminal-screening/#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": "Publish and control a prohibited-items list for cruise-terminal screening"
                },
                "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": 565,
                "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.515 -- Maritime Security: Facilities",
                    "url": "https://www.ecfr.gov/current/title-33/section-105.515"
                }
            }
        ]
    }
}