Restrict Access by Device and Location
“A trusted member on an unfit device is still a risk.”
The Challenge
Authenticating a person tells you who is at the keyboard. It says nothing about the machine they are on, whether the security tooling you deployed is still running on it, or which country the session is coming from today.
A VPN makes that judgement once, at the moment the tunnel comes up, and then holds it open for hours. Anything that changes afterwards — an outdated client, a stopped process, a session that moves country — changes nothing about the access already granted.
The Solution
SXAccess provides five device requirements that can be made a condition of access, alongside the member and the resource: Operating System, Process, SXAccess Client Version, Country & Region, and Device Network Range.
Each check is switched on per access rule rather than applied across the whole network, so a contractor access rule can require a supported Operating System and an approved Country & Region while an internal read-only application requires none of them.
And because the checks are re-evaluated while the session is open, a device that falls out of compliance loses the access it no longer qualifies for — rather than keeping it until the next sign-in.
Device Checks
Operating System, Process, SXAccess Client Version.
Connection Checks
Country & Region, Device Network Range
In-Session Re-Evaluation
Re-checked on a recurring basis, not once.
Continuous Device Verification
Switch On the Requirements You Need
Operating System and SXAccess Client Version keep unsupported and outdated machines out. Process restricts access based on the running processes of a device, and is available on desktop operating systems. Country & Region and Device Network Range govern where a connection may originate.
Attach Them to the Access Rules That Need Them
Each check is configured per access rule, so requirements can be strict for production and contractor access without imposing the same friction on everything else.
Let SXAccess Keep Re-Checking
The checks are re-evaluated on a recurring basis for the life of the session. Access depends on the device and the connection still satisfying the access rule — not on what was true at sign-in.
Security & Business Value
A tunnel authenticates a credential and then stops asking questions. SXAccess keeps asking, and access follows the answer.
Practically, it means unsupported operating systems and outdated clients are kept off production, contractor access is confined to the countries and network ranges where the work is expected, and on desktop a required process can be a precondition of access rather than a hope.
- Device Network Range
- SXAccess Client Version
- Process
- Country & Region
- Operating System
Back to Solutions Overview
Connect What Matters. Limit Everything Else.
Give members secure access to the applications, systems, and networks they need — without handing them the rest of your infrastructure.
Secure connectivity. Precise access. One private network.