# Require tenant security programs to preserve the airport program's protection > Use 49 CFR 1542.113 -- Airport Security to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/require-tenant-security-programs-to-preserve-the-airport-program-s-protection/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:10:35+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.113 -- 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.113 -- 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: Require tenant security programs to preserve the airport program’s protection. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [49 CFR 1542.113 — Airport Security](https://www.ecfr.gov/current/title-49/section-1542.113) from Transportation Security Administration via eCFR supports the following bounded statements: - Under 49 CFR 1542, the rule requires that the airport tenant security program include the following: measures by which the airport operator will monitor and audit the tenant’s compliance with the security program. The research record locates this support at 49 CFR 1542.113(b)(3), read with 49 CFR 1542.113(b) (eCFR anchor p-1542.113(b)(3)). - Under 49 CFR 1542, the rule requires that the airport tenant security program include the following: procedures by which the tenant will immediately notify the airport operator of and provide for alternative security measures for changed conditions as described in section 1542.103(a). The research record locates this support at 49 CFR 1542.113(b)(8), read with 49 CFR 1542.113(b) (eCFR anchor p-1542.113(b)(8)). These statements are the factual basis for this document. Do not extend them into a broader assurance. Review access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths only where the source and recorded environment align. ## 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.113(b)(3), read with 49 CFR 1542.113(b) (eCFR anchor p-1542.113(b)(3)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 49 CFR 1542.113(b)(8), read with 49 CFR 1542.113(b) (eCFR anchor p-1542.113(b)(8)), 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. Start with applicability, then compare the observed state with the cited source. 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 A reviewer should be able to retrace the decision from 49 CFR 1542.113(b)(3), read with 49 CFR 1542.113(b) (eCFR anchor p-1542.113(b)(3)); 49 CFR 1542.113(b)(8), read with 49 CFR 1542.113(b) (eCFR anchor p-1542.113(b)(8)) through asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Record what was collected, where, when, by whom, and which system or role it represents. 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. ## Official references - [49 CFR 1542.113 — Airport Security](https://www.ecfr.gov/current/title-49/section-1542.113) — Transportation Security Administration via eCFR ## Primary reference - Name: 49 CFR 1542.113 -- Airport Security - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-49/section-1542.113 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Require tenant security programs to preserve the airport program's protection,” DSE Security, https://update.dsesecurity.com/updates/require-tenant-security-programs-to-preserve-the-airport-program-s-protection/ 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.