Home » Industries » Airports

Cybersecurity Built for Airports

From curb to runway, airports run on interconnected IT and operational technology most security programs were never built to protect. Assura secures the systems that keep passengers moving and operations running, and we understand the TSA requirements you answer to.

Airports face a cybersecurity environment no other industry faces.

An airport is not one organization. It is dozens of them, airlines, TSA, CBP, concessionaires, ground handlers, fuel operators, and the airport authority itself, operating side by side and depending on systems the airport authority runs. At many airports, common-use platforms like CUPPS and CUSS let multiple airlines process passengers on airport-provided equipment. Building management, baggage handling, jet bridges, and access control run on operational technology that was never designed to touch the internet, and increasingly does.

Every one of those dependencies is a connection point: a vendor link, a common-use platform, a badge system used by thousands of tenant employees. Each is a trust boundary the airport authority has to secure, and a weakness at any of them can become a path into the operations that keep the airport running. Most security programs are built for a single organization with a single set of users. Airports have neither. And the risks that come with that show up in places even well-run airports have never thought to look.

Cyber risk is operational and physical risk at an airport. Built for the people accountable for all three.

You answer to TSA. We make sure the answer holds up.

For the executive who signs the security program and faces the auditor when something goes wrong. You need a partner who understands what you're accountable for, across cyber, operations, and physical security, not a vendor who hands you a report and walks away.

You inherited JEA 23-01. We have done this before.

For the IT or security lead operationalizing federal cyber mandates across a shared, multi-tenant airport environment. You need someone who knows where airports actually get it wrong, and how to close the gaps before an auditor or an attacker finds them.

You are building it right. We build to the standards.

For the CISO or security director building a program that has to hold up under TSA scrutiny from day one. You need it built to that standard from the start, not retrofitted after the first finding.
Whatever your role, the through-line is the same: an airport security program that satisfies your federal mandates, preserves passenger trust, and holds up when the systems that keep you running are tested. That is what Assura builds.

The services airports use to close the gap.

Your TSA cyber mandates and your contingency plan may never have been introduced to each other.

TSA Joint Emergency Amendment 23-01 tells airports to segment networks, control access, monitor continuously, and manage patching, all aimed at keeping an attacker out. But 49 CFR 1542.307 and 1542.301, the rules behind your incident management program and contingency plan, name physical threats: bomb threats, sabotage, and aircraft piracy. Cyber is not in the text, so the annual exercises that satisfy those rules almost never drill a cyberattack. The diagram below shows how that attack unfolds across airport systems, where JEA 23-01 coverage ends, and where the gap begins.

Diagram of how a cyberattack unfolds across airport systems, mapped to the NIST Cybersecurity Framework. Each stage of the attack is paired with the framework function and the Assura services that address it, and each service name in the diagram links to its page. TSA JEA 23-01 covers Identify, Protect, and Detect. Respond and Recover, where the 49 CFR Part 1542 contingency plans live, are rarely exercised for cyber, and that is the gap.
How Assura Supports Airport Cybersecurity and Resilience Assura services mapped to the NIST Cybersecurity Framework and an airport attack chain, as a vertical stack. Each attack stage is paired with the framework function and Assura services that address it. Govern spans the top. Identify, Protect, and Detect are covered by TSA JEA 23-01. Respond and Recover, where the 49 CFR Part 1542 contingency plans live, are a gap not usually tested for cyber. AuditArmor spans the bottom. How Assura Supports Airport Cybersecurity and Resilience Services mapped to the NIST Cybersecurity Framework (CSF) and the attack chain GOVERN (GV) The governance that directs every function below GRC-as-a-Service Security Program Development Assura defends, detects, and responds to cyber threats IDENTIFY (ID) Risk Assessment Penetration Testing Vulnerability Management-as-a-Service PROTECT (PR) ProDefense Secure Endpoint ProDefense Multi-Factor Authentication ProDefense Email Security DETECT (DE) ProDefense Managed Detection and Response ProDefense SIEM/XDR RESPOND (RS) Incident Response Planning RECOVER (RC) Business Continuity IT Disaster Recovery Covered by TSA JEA 23-01 THE ATTACK CHAIN Initial access Phishing, vulnerable service Unsegmented network Flat IT and OT environment Lateral movement Into operational systems Security systems Access control, cameras, OT Operational takedown The 49 CFR Part 1542 gap: not usually tested for cyber AUDITARMOR® GUARANTEE Every function above is defensible when TSA audits it. If a variance is found in Assura's work, we fix it at our expense. TSA JEA 23-01 covers Identify, Protect, and Detect. Respond and Recover, where your 1542 contingency plans live, are rarely exercised for cyber.
How Assura Supports Airport Cybersecurity and Resilience Assura services mapped to the NIST Cybersecurity Framework and an airport attack chain, as a vertical stack. Each attack stage is paired with the framework function and Assura services that address it. Govern spans the top. Identify, Protect, and Detect are covered by TSA JEA 23-01. Respond and Recover, where the 49 CFR Part 1542 contingency plans live, are a gap not usually tested for cyber. AuditArmor spans the bottom. How Assura Supports Airport Cybersecurity and Resilience Services mapped to NIST CSF and the attack chain GOVERN (GV) The governance that directs every function below GRC-as-a-Service Security Program Development HOW THE ATTACK UNFOLDS, AND WHAT STOPS IT 1 Initial access Phishing, vulnerable service IDENTIFY (ID) Risk Assessment Penetration Testing Vulnerability Management-as-a-Service 2 Unsegmented network Flat IT and OT environment PROTECT (PR) ProDefense Secure Endpoint ProDefense Multi-Factor Authentication ProDefense Email Security 3 Lateral movement Into operational systems DETECT (DE) ProDefense Managed Detection and Response ProDefense SIEM/XDR ProDefense 4 Security systems compromised Access control, cameras, OT RESPOND (RS) Incident Response Planning Managed Detection and Response 5 Operational takedown RECOVER (RC) Business Continuity IT Disaster Recovery Covered by TSA JEA 23-01 The 49 CFR Part 1542 gap: not usually tested for cyber AUDITARMOR® GUARANTEE Every function above is defensible when TSA audits it. If a variance is found, we fix it at our expense. JEA 23-01 covers ID, PR, and DE. Respond and Recover, where your 1542 plans live, are rarely tested for cyber.
Penetration Testing

Find the path an attacker would take before they do.

JEA 23-01 requires vulnerability assessments. A penetration test goes further, proving exactly where a real attacker could get in across your IT and OT environment.

Vulnerability Management-as-a-Service

Know your exposure continuously, not just at audit time.

Airport networks change constantly. New tenants, new systems, new connections. VMaaS keeps your vulnerability picture current between engagements and tied to CISA’s Known Exploited Vulnerabilities catalog.

ProDefense® Managed SIEM/XDR

Detect an intrusion before it reaches your operational systems.

Continuous monitoring across IT and OT, correlating events across your environment so lateral movement toward building control or baggage systems triggers an alert, not a post-incident report.

Incident Response Planning

Know exactly what to do when it happens.

A cyber incident response plan built for the airport environment, exercised against the scenarios JEA 23-01 and your 1542 contingency program were never tested for.

Business Continuity and COOP

Keep operations running when systems go down.

Business continuity and IT disaster recovery planning that accounts for cyber-triggered operational disruption, closing the gap your 1542 contingency plan leaves open.

GRC-as-a-Service

A security program TSA can audit and you can defend.

Governance, risk, and compliance built around your TSA security program obligations, JEA 23-01 requirements, and the operational reality of running a multi-tenant airport.

Frameworks and regulations Assura addresses for airports:

TSA JEA 23-01 49 CFR Part 1542 NIST CSF 2.0 PCI DSS CJIS HIPAA
Most firms hand you a deliverable and walk away. We stand behind ours. If your audit reveals non-compliant work Assura performed, we fix it at our expense, no matter the cost. That's the AuditArmor® Guarantee.

Zero audit findings. Nearly 9,000 attacks stopped.

An East Coast international airport came to Assura with no cybersecurity policies or protocols in place. We built the program from the ground up: fractional CISO, continuous monitoring, vulnerability management, and audit defense. The airport has not received a single cybersecurity-related audit finding since. TSA, NIST, and PCI DSS compliant.

~9000

Cyberattacks detected and investigated in a single quarter of 2024

0

Breaches or system failures during that period

Ready to close the gap?

Talk to an Assura airport cybersecurity expert about your cybersecurity obligations, and where your contingency plan may be leaving you exposed.

Frequently Asked Questions

What does TSA Joint Emergency Amendment 23-01 require airports to do?

JEA 23-01 requires airports to develop and submit a Cybersecurity Implementation Plan (CIP) to TSA covering five areas: identifying critical systems, network segmentation, access controls, continuous monitoring and detection, and patch management. Beyond the CIP, JEA 23-01 also requires an annual Cybersecurity Assessments Program (CAP): proactive assessments of critical systems, recurring Cybersecurity Architectural Design Reviews, and penetration testing including red and purple team exercises. The CAP must be submitted to TSA within 60 days of CIP approval and updated annually. Together, the CIP and CAP establish the ongoing program airports must maintain and demonstrate.

What is the 49 CFR Part 1542 cyber gap?

49 CFR Part 1542 requires airports to maintain a contingency plan (§1542.301) and an incident management program (§1542.307). Those requirements enumerate physical threats: bomb threats, sabotage, aircraft piracy. Cyber is not in the text. As a result, the annual exercises that satisfy those requirements almost never drill a cyberattack, even as TSA and CISA now push airports to integrate cyber scenarios into their tabletops. You can be fully compliant with both mandates and still be unprepared for the event most likely to test them.

How does Assura help airports meet JEA 23-01 requirements?

Assura maps your environment against JEA 23-01's five performance-based measures and the CAP's assessment requirements, identifies gaps in your current controls, and builds or improves the program elements you need, from network segmentation and access controls to continuous monitoring, patch management, and recurring penetration testing. We also help you develop and document the Cybersecurity Implementation Plan TSA requires.

Why is airport cybersecurity different from other industries?

Airports are not single organizations. They are dozens of entities, airlines, TSA, CBP, concessionaires, ground handlers, and the airport authority itself, operating side by side and depending on systems the airport authority runs. At many airports, common-use passenger processing platforms like CUPPS run on airport-provided equipment used by multiple airlines. Building management, baggage handling, jet bridges, and access control run on operational technology that was never designed to be networked. That combination of dozens of dependent organizations, IT and OT the airport authority must secure on their behalf, and federal oversight creates a cybersecurity environment no other industry quite replicates.

What happens if an airport's cybersecurity program has a finding after working with Assura?

The AuditArmor® Guarantee applies. If an audit reveals non-compliant work Assura performed, we fix it at our expense, no matter the cost. That guarantee covers every engagement, from JEA 23-01 compliance work to security program development.