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.
You inherited JEA 23-01. We have done this before.
You are building it right. We build to the standards.
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.
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-ServiceKnow 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/XDRDetect 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 PlanningKnow 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 COOPKeep 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-ServiceA 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:
Zero audit findings. Nearly 9,000 attacks stopped.
~9000
Cyberattacks detected and investigated in a single quarter of 2024
0
Breaches or system failures during that period
Ready to close the gap?
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.