Discuss your deployment with engineering.

Yes. Our solutions can be purchased independently; the three pillars are not a mandatory bundle. AX-Interlock does not require a separate AX-Box Gatekeeper deployment; it includes its own aXite security software and requires project-specific engineering and validation. AX-Cyberrange is a platform delivered as scoped, customer-specific test environments. We start with the operational problem you need to address.

No. AX-Energy Protect addresses smart meters and energy grid endpoints for grid operators. MDM-PROTECT, powered by aXite, serves commercial inland fleets. Each has its own deployment and service scope.

We assess the controller models, firmware, protocols and network architecture in your environment before confirming compatibility. AX-Box Gatekeeper adds controls around supported assets rather than requiring changes inside the PLC. The assessment identifies what is supported as standard, what needs configuration and what would require additional engineering.

No agent, firmware modification or PLC program change is required. AX-Box Gatekeeper is installed inline during a planned maintenance window.

Yes. Access does not automatically grant permission to make changes. AX-Box Gatekeeper enforces access and write permissions for authorised users and selected PLCs within approved maintenance windows. Access and actions are logged, making maintenance controlled and traceable.

Within Protect, AX-Box Gatekeeper combines control of access and communication with configuration-integrity monitoring around the protected PLC, without changing its firmware or program. Its operational application is documented in the Schiphol case.

AX-Box Gatekeeper adds local controls around protected assets, while your existing security tools and SOC can retain their monitoring and response roles. We assess which events and records need to be shared and which interfaces are available. Integration, monitoring services and operational responsibilities are agreed for your deployment; a SOC service is not automatically included.

Local processing is central to our approach, but data flows depend on the solution and service arrangement. For example, MDM-PROTECT combines onboard controls with monitoring from shore. Processing locations, authorised access, any data shared for monitoring or support, and retention arrangements are defined for your deployment.

Depending on the solution and configuration, evidence can include access logs, change records, configuration status and security-event records. We agree the required outputs and their relationship to your assessment criteria. These records support your assessment; purchasing a product does not by itself establish compliance or certification.

AX-Interlock is designed to translate a validated aXite cyber signal into a predefined, process-specific safe machine state, not simply cut power. The chain is lab-tested; operational validation and certification scope remain to be completed.

Yes. AX-Cyberrange is a platform delivered as a scoped test environment using an isolated, on-premises copy of the relevant OT environment. Attack scenarios and remediation tests run in that copy, not in production. Supported systems, process representation and model limits are assessed for each environment, so results are interpreted within the tested scope.

No. AX-Cyberrange is being developed to combine a representative OT environment, agentic pentesting and analysis of operational consequences. The focus is on testing attack paths and remediation in an isolated, on-premises copy, not on running attacks against production. The solution is delivered as scoped test environments.