TL;DR: 300,000 devices show how IIJ Flex Mobility Service/ZTNA is being used to pair remote access scale with device verification, in Absolute Security's case work. Remote access must still fail safely and recover without widening trust when endpoints or controls degrade.
Editorial analysis by NHI Mgmt Group, based on content published by Absolute Security: “IIJ Flex Mobility Service/ZTNA Now Protecting Over 300,000 devices”.
Key questions
Q: When does ZTNA become a resilience control rather than just a connectivity control?
A: ZTNA becomes a resilience control when the organisation depends on it to keep access safe during control failure, degraded endpoints, or incident response.
Q: What are the signs that permissive remote-access policies have become a hidden risk?
A: A clear sign is when temporary remote-access exceptions remain in place long after the reason for them has passed.
Q: How should security teams govern third-party remote access in practice?
A: Treat third-party remote access as a governed identity path, not a networking exception.
Practitioner guidance
- Map remote access paths to explicit trust decisions Inventory every remote access entry point, the identity signals it consumes, and the policy conditions required before access is granted.
- Add device health checks to access policy Require current endpoint status, not just user authentication, before granting access to sensitive applications and admin functions.
- Test fallback access when controls fail Run resilience exercises that simulate degraded security controls, then verify whether business users can restore access without weakening policy.
Bottom line: Remote access is increasingly governed as a resilience and identity problem, not only as a networking problem.
Glossary terms: Zero Trust Network, Remote Access Assurance, Device Posture
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Remote access is now a resilience control, not just an access control. The article shows that the value of ZTNA is no longer limited to blocking unauthorised connectivity. It is increasingly judged by whether access can remain policy-driven and recoverable when endpoint signals degrade or security controls fail. Practitioners should treat remote access governance as part of business continuity, not a separate networking decision.
A question worth separating out:
Q: What should teams check before expanding remote access to more users and devices?
A: Teams should verify that identity verification, device health monitoring, logging, and recovery procedures all scale together. Expanding remote access without those controls usually creates hidden resilience debt, because the organisation gains more access paths without gaining better control over failure, misuse, or restoration.
👉 Read our full editorial: Remote access resilience now defines ZTNA adoption in Japan