Address audit gaps around legacy and new airport controllers.
AX-Box Gatekeeper adds access control, configuration-integrity monitoring and policy enforcement around the controllers your airport relies on. Add the controls you need without changing PLC code or firmware.
AX-Box Gatekeeper. Security around the controller, without changing its control logic.
Installed inline, AX-Box Gatekeeper mediates supported communication and enforces configured security policies close to the protected controller. It works alongside your existing network security and maintenance processes.
An airport deployment consists of the AX-Box Gatekeeper hardware and software, implementation and configuration, AX-Manage for configuration and event management, and monitoring. A managed SOC or advisory service is a separate scope that is agreed with you.
Explore AX-Box Gatekeeper
The PLC still works. The security controls need attention.
- 01
The audit finding
Audit findings often concern access, allowed changes and configuration integrity around legacy PLCs. Replacing working controllers requires applications, integration and testing, and may not solve every gap.
- 02
The incident or advisory
Following an incident or vulnerability alert, review who can access your controllers and which changes they are authorised to make. AX-Box Gatekeeper enforces these permissions on supported controllers and logs access and configuration changes to support your investigation.
Control maintenance access. Track what changes.
- 01
Authorise access to the right controller
Access is assigned to the user, PLC, work order and window, with actions logged.
- 02
Monitor configuration integrity
Track uploads and downloads, keep local backups and support controlled recovery to a validated known-good configuration under an agreed procedure.
- 03
Enforce policies close to the asset
Configured rules apply at the field boundary. Supported controller, protocol and command scope are confirmed during fit assessment.
- 04
Give engineering and security a shared record
AX-Manage supports event and configuration review. Reporting and any OT/SOC integrations are agreed for the deployment.
Keep the PLC configuration. Plan the installation.
No agent is installed on the PLC, and its firmware, code and operational application remain unchanged. Inline installation does require a planned maintenance window, followed by configuration, learning and policy setup.
Scope assets, missing controls and protocols with Asset Management, security and engineering. Processing can remain on premises.
Access, change and event records support the evidence you need for NIS2 and Cbw obligations and for IEC 62443 programmes. They do not certify your installation or guarantee compliance.
Where it fits
- Significant legacy estates
- Operational reliance on active control
- Missing access, change or evidence controls
- Operational systems (supported airport installations)
Where it does not
- Controls already present
- Passive monitoring is sufficient
- Pure IT scope without OT engagement
Operational experience. Application approval.
Schiphol
AX-Box Gatekeeper is used in Schiphol's baggage-handling environment.
TSA · 450+ US airports
Separately, the TSA has tested and approved AX-Box Gatekeeper for application at more than 450 US airports.
Start here · 07 / 07
Bring the audit finding. Start with the controller.
Tell us the operational system, control gap and engineering constraints. We can assess the relevant scope with your airport team.
Discuss your airport's control gaps