{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/submit-protect-and-implement-the-facility-security-plan-only-after-approval/", "item": { "id": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval/", "slug": "submit-protect-and-implement-the-facility-security-plan-only-after-approval", "url": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval.md", "json": "https://update.dsesecurity.com/api/v1/posts/submit-protect-and-implement-the-facility-security-plan-only-after-approval/" }, "title": "Submit, protect, and implement the Facility Security Plan only after approval", "summary": "Use 33 CFR 105.410 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "explainer", "name": "Explainer" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "access-control", "name": "Access Control", "url": "https://update.dsesecurity.com/topic/access-control/" }, { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-08-27T12:10:53+00:00", "modified_at": "2026-08-27T13:09:38+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 614, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 33 CFR 105.410 -- 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.410 -- Maritime Security: Facilities", "url": "https://www.ecfr.gov/current/title-33/section-105.410", "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": "

Frame this document as a source-led configuration and assurance check: Submit, protect, and implement the Facility Security Plan only after approval. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official 33 CFR 105.410 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:

\n\n

Only the traced statements above are asserted as source facts. Apply the review to access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths after confirming that the source and deployed context match.

\n

What the source does not establish

\n

Applies only to facilities within 33 CFR part 105 and the cited section. Confirm Coast Guard jurisdiction, the approved Facility Security Plan, the current MARSEC level, and any approved alternatives; this is not legal advice or a universal facility-design standard. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision.

\n

Applicability questions

\n\n

DSE recommendation:

\n

DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation.

\n

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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.

\n

Verification and evidence

\n

Tie each conclusion back to 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)); 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)) and to observable material such as asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.

\n

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’s observation is not a continuing guarantee.

\n

Official references

\n", "content_text": "Frame this document as a source-led configuration and assurance check: Submit, protect, and implement the Facility Security Plan only after approval. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.410 — 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 each facility currently in operation either: submit one copy of their Facility Security Plan (FSP) for review and approval to the cognizant COTP and a letter certifying that the FSP meets applicable requirements of this part. The research record locates this support at 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)).\nUnder 33 CFR 105, the cognizant COTP will examine each submission for compliance with this part and either: approve it and specify any conditions of approval, returning to the submitter a letter stating its acceptance and any conditions. The research record locates this support at 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)).\n\nOnly the traced statements above are asserted as source facts. Apply the review to access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths after confirming that the source and deployed context match.\nWhat the source does not establish\nApplies only to facilities within 33 CFR part 105 and the cited section. Confirm Coast Guard jurisdiction, the approved Facility Security Plan, the current MARSEC level, and any approved alternatives; this is not legal advice or a universal facility-design standard. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?\nWhat baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation.\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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie each conclusion back to 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)); 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)) and to observable material such as asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.\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.410 — Maritime Security: Facilities — U.S. Coast Guard via eCFR", "content_markdown": "Frame this document as a source-led configuration and assurance check: Submit, protect, and implement the Facility Security Plan only after approval. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [33 CFR 105.410 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.410) 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 each facility currently in operation either: submit one copy of their Facility Security Plan (FSP) for review and approval to the cognizant COTP and a letter certifying that the FSP meets applicable requirements of this part. The research record locates this support at 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)).\n\n- Under 33 CFR 105, the cognizant COTP will examine each submission for compliance with this part and either: approve it and specify any conditions of approval, returning to the submitter a letter stating its acceptance and any conditions. The research record locates this support at 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)).\n\nOnly the traced statements above are asserted as source facts. Apply the review to access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths after confirming that the source and deployed context match.\n\n## What the source does not establish\n\nApplies only to facilities within 33 CFR part 105 and the cited section. Confirm Coast Guard jurisdiction, the approved Facility Security Plan, the current MARSEC level, and any approved alternatives; this is not legal advice or a universal facility-design standard. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)), which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?\n\n- What baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation?\n\n- Which success, stop, and escalation criteria are written before testing begins?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation.\n\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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nTie each conclusion back to 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)); 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)) and to observable material such as asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.\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.410 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.410) — 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/submit-protect-and-implement-the-facility-security-plan-only-after-approval/", "url": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Submit, protect, and implement the Facility Security Plan only after approval", "item": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval/#article", "identifier": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval/", "url": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval/", "headline": "Submit, protect, and implement the Facility Security Plan only after approval", "description": "Use 33 CFR 105.410 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.", "abstract": "Use 33 CFR 105.410 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Frame this document as a source-led configuration and assurance check: Submit, protect, and implement the Facility Security Plan only after approval. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 33 CFR 105.410 — 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 each facility currently in operation either: submit one copy of their Facility Security Plan (FSP) for review and approval to the cognizant COTP and a letter certifying that the FSP meets applicable requirements of this part. The research record locates this support at 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)).\nUnder 33 CFR 105, the cognizant COTP will examine each submission for compliance with this part and either: approve it and specify any conditions of approval, returning to the submitter a letter stating its acceptance and any conditions. The research record locates this support at 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)).\n\nOnly the traced statements above are asserted as source facts. Apply the review to access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths after confirming that the source and deployed context match.\nWhat the source does not establish\nApplies only to facilities within 33 CFR part 105 and the cited section. Confirm Coast Guard jurisdiction, the approved Facility Security Plan, the current MARSEC level, and any approved alternatives; this is not legal advice or a universal facility-design standard. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)), which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?\nWhat baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation.\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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie each conclusion back to 33 CFR 105.410(a)(1), read with 33 CFR 105.410(a) (eCFR anchor p-105.410(a)(1)); 33 CFR 105.410(c)(1), read with 33 CFR 105.410(c) (eCFR anchor p-105.410(c)(1)) and to observable material such as asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.\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.410 — Maritime Security: Facilities — U.S. Coast Guard via eCFR", "datePublished": "2026-08-27T12:10:53+00:00", "dateModified": "2026-08-27T13:09:38+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/submit-protect-and-implement-the-facility-security-plan-only-after-approval/" }, "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/submit-protect-and-implement-the-facility-security-plan-only-after-approval/#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": "Submit, protect, and implement the Facility Security Plan only after approval" }, "articleSection": [ "Access Control", "Cybersecurity", "Video Surveillance" ], "keywords": [ "Access Control", "Cybersecurity", "Video Surveillance", "Explainer", "Advisory priority" ], "genre": "Explainer", "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": 614, "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.410 -- Maritime Security: Facilities", "url": "https://www.ecfr.gov/current/title-33/section-105.410" } } ] } }