Topic starter
06/09/2026 9:34 am
TL;DR: Air-gapped and network-restricted enterprises can run full-stack, automated device testing entirely on-premises while preserving compliance, observability, and scale, according to Arxan Technologies. The practical shift is to treat the lab as part of the controlled environment, not a compromise, because governance, auditability, and toolchain integration matter more than remote convenience.
Editorial analysis by NHI Mgmt Group, based on content published by Arxan Technologies: “Air-Gapped Testing Without Tradeoffs: Secure & Scalable”.
Key questions
Q: How should regulated teams design air-gapped device testing so it stays auditable?
A: Design the device lab as a controlled part of the security boundary, not as a separate QA convenience.
Q: Why do remote device clouds often fail for regulated testing programmes?
A: They depend on external infrastructure and shared services that can conflict with on-premises data handling, audit, and hardware-reach requirements.
Q: What are the biggest governance mistakes in on-premise device labs?
A: The main mistakes are treating the lab as a standalone tool, failing to retain audit evidence, and leaving scheduling or access decisions ad hoc.
Practitioner guidance
- Define the lab as part of the controlled environment Write policy that keeps test execution, logs, screenshots, and session data inside the enterprise boundary and subjects them to the same access rules as other sensitive records.
- Centralise device scheduling and evidence capture Use a single scheduler to allocate devices, run suites in parallel, and retain structured artefacts such as crash reports, network captures, and video traces.
- Integrate the lab with CI/CD and observability stacks Connect test triggers to your build pipeline and forward execution telemetry into existing platforms so flakiness, regressions, and device-specific failures are visible alongside application health.
Bottom line: Air-gapped testing is not a compromise when the lab is designed as part of the controlled environment rather than as an external convenience layer.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/09/2026 9:34 am
Air-gapped testing is really an evidence-governance problem. The article is not just about testing speed, but about whether regulated engineering teams can preserve auditability while keeping execution inside the enterprise boundary. That shifts the discussion from tooling convenience to controlled evidence, where the device lab becomes part of the compliance surface. Practitioners should govern the lab like any other controlled environment.
A question worth separating out:
Q: Should device testing architecture prioritise auditability or test speed?
A: The two should be designed together, but auditability comes first in regulated environments. Speed is only valuable if every run is reproducible, attributable, and reviewable, because a fast test that cannot be evidenced does not satisfy compliance or operational assurance needs.
👉 Read our full editorial: Air-gapped testing can scale without sacrificing auditability