Skip to content

Device checks without enrolling in Okta Verify

XFA checks each device when someone signs in through Okta. Nothing is enrolled and no MDM is needed. People fix what it finds from the XFA app, and their device stays theirs.

What is Okta Device Assurance?

Device Assurance is part of Okta Identity Engine. An admin sets rules for a device, such as a minimum operating system version, disk encryption, or a screen lock, and adds them to Okta's app sign-in policies.

The device is checked through Okta Verify, Chrome Enterprise or both. Custom checks need devices enrolled in an MDM and an Okta Device Access subscription.

What XFA does

  • XFA connects to Google Workspace, Microsoft Entra ID (Microsoft 365), Okta, OneLogin, Ping Identity, or Keycloak. It checks the device every time someone signs in.
  • If something is off, the person fixes it from the XFA app.
  • New people install the app themselves at their first sign-in, without admin rights.

XFA vs Okta, feature by feature

XFAOkta Device Assurance
Security checks
OS version, disk encryption, and screen lock checksYesYes
Jailbreak and root detectionYesYes
Browser kept up to dateYesNo
Active antimalware verifiedYesNoOkta can read antimalware status on Windows through an endpoint security integration, which you deploy and maintain separately
Last reboot checkYesNo
BYOD
Works for company-owned devicesYesYes
People install it themselvesYesNoThe device has to be enrolled in Okta Verify before Okta can check it
Finds devices through SSO sign-ins, before anything is installedYesNo
Setup and admin
Admin dashboardYesYes
Self-serve setup, no IT rolloutYesNo
Known vulnerabilities (CVEs) per device, from OS and browser versionsYesNo
Warns users before they are blocked at sign-inYesNo
Ecosystem
Works with your identity provider (SSO)YesOnly Okta
No identity provider migration neededYesNoDevice Assurance is part of Okta, so it needs Okta as your identity provider

Okta details from Okta's help centre and developer documentation, checked October 2026. Sources: Add a device assurance policy (opens in a new tab); Okta posture checks and remediation (opens in a new tab).

“It's user-friendly and straightforward for onboarding.”
Roel Buyzen, Chief Delivery Officer, BytefliesRoel BuyzenChief Delivery Officer, BytefliesRead the Byteflies story

Questions about XFA and Okta

A phone in one hand and a laptop in a busy coworking space
Do we have to leave Okta to use XFA?

No. XFA connects to Okta and checks the device on the sign-ins that go through it. Your users, groups, and apps stay in Okta.

Can we keep Okta Device Assurance and add XFA?

Yes. Both work on Okta sign-ins and neither depends on the other. If you keep both, set each rule in one place only, so people are never asked to fix the same thing twice.

Does XFA block people from the first day?

Only if you set it to. Each check warns or blocks, and you choose after how many days. With a warning, people see what is wrong at sign-in and still get in while they fix it.

Which checks does XFA run?

Four to start with: the operating system version, disk encryption, screen lock, and antimalware protection. You can add more as you grow, up to 34.

Do people need admin rights to install the XFA app?

No. People install it themselves on macOS, Windows, Linux, iOS, or Android, and the app takes no control of the device.

What does it cost to start?

Nothing. XFA is free to start, with no cap on people. Connect Okta, and at their next sign-in people see what to fix and fix it from the XFA app. More checks and blocking come with the paid plans.

Compare plans

Try it on your next Okta sign-in.

Start for free, connect Okta, and check your own laptop first.

Two people working on laptops at a shared table