# Supplement airport law-enforcement staffing only under approved procedures > Use 49 CFR 1542.219 -- Airport Security to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/supplement-airport-law-enforcement-staffing-only-under-approved-procedures/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:10:25+00:00 - Modified: 2026-08-27T13:12:21+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Briefing - DSE priority: Advisory - Topics: Access Control, Cybersecurity, Video Surveillance - Reading time: 3 minutes ## What you need to know Use 49 CFR 1542.219 -- Airport Security to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of 49 CFR 1542.219 -- Airport Security ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Use this document to resolve one bounded operational decision: Supplement airport law-enforcement staffing only under approved procedures. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [49 CFR 1542.219 — Airport Security](https://www.ecfr.gov/current/title-49/section-1542.219) from Transportation Security Administration via eCFR supports the following bounded statements: - Under 49 CFR 1542, a request for Federal personnel must describe available qualified law-enforcement personnel, the airport operator’s efforts to obtain State, local, and private support, and those agencies’ responses. The research record locates this support at 49 CFR 1542.219(b)(4), read with 49 CFR 1542.219(b) (eCFR anchor p-1542.219(b)(4)). - Under 49 CFR 1542, the request must estimate how many Federal personnel are needed to supplement available law enforcement and how long they are needed. The research record locates this support at 49 CFR 1542.219(b)(5), read with 49 CFR 1542.219(b) (eCFR anchor p-1542.219(b)(5)). Keep the evidence boundary at these traced claims. They support a review of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths; they do not support conclusions outside the source’s stated conditions. ## What the source does not establish Applies only to airport operators, tenants, personnel, and areas covered by 49 CFR part 1542 and the cited section. Confirm the TSA-approved security program and current directives; this is not legal advice or a universal access-control standard. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel and the environment’s recorded constraints. ## Applicability questions - For source statement 1 at 49 CFR 1542.219(b)(4), read with 49 CFR 1542.219(b) (eCFR anchor p-1542.219(b)(4)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 49 CFR 1542.219(b)(5), read with 49 CFR 1542.219(b) (eCFR anchor p-1542.219(b)(5)), which observable configuration, record, or test can confirm applicability here? - Which owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions? - What baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation? - Which success, stop, and escalation criteria are written before testing begins? ## DSE recommendation: 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 access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation. An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before and after the test, and store only sanitized operational evidence. ## Verification and evidence Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 49 CFR 1542.219(b)(4), read with 49 CFR 1542.219(b) (eCFR anchor p-1542.219(b)(4)); 49 CFR 1542.219(b)(5), read with 49 CFR 1542.219(b) (eCFR anchor p-1542.219(b)(5)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator. 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. ## Official references - [49 CFR 1542.219 — Airport Security](https://www.ecfr.gov/current/title-49/section-1542.219) — Transportation Security Administration via eCFR ## Primary reference - Name: 49 CFR 1542.219 -- Airport Security - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-49/section-1542.219 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Supplement airport law-enforcement staffing only under approved procedures,” DSE Security, https://update.dsesecurity.com/updates/supplement-airport-law-enforcement-staffing-only-under-approved-procedures/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.