This article provides answers to frequently asked questions about Okta Device Access.
- For more information about Desktop MFA, refer to Frequently Asked Questions About Desktop MFA
- For more information about Desktop Password Sync, refer to Frequently Asked Questions About Desktop Password Sync
Table of Contents
What is Okta Device Access?
What is available today from Okta Device Access?
Will a customer be able to deprecate their legacy environment?
Will Okta become an MDM?
Is Okta Device Access compliant with HIPAA and FedRAMP?
What is Okta Device Access?
At Okta, we believe identity security should be a natural extension of work rather than a roadblock. That’s why we’ve invested deeply in device integrations with major platforms so that every login, from desktop to cloud, can strengthen trust without slowing teams down.
Okta Device Access extends the simplicity and security you know from Okta to the very first moment of your workday: signing in to your computer. By joining managed Windows and macOS devices to Okta, organizations enable their workforce to turn on their computers, sign in with their Okta credentials, and then—with that single device login—access their device account, apps, and resources.
While fragmented systems create gaps between device identities and user identities, and with too many logins in between, Okta Device Access closes those gaps, supporting a connected identity security fabric that strengthens security while reducing login friction.
With Okta Device Access, organizations can:
- Secure the first vulnerable touchpoint - the device login
- Bring passwordless MFA to the device login experience and apply consistent access policies across login touchpoints, with Okta Universal Directory providing central visibility and control over user and device identities
- Enable hardware-protected sessions that power workforce productivity
- Replace repeated sign-in prompts with one secure device login backed by trusted Okta-joined devices for seamless access to downstream apps that minimize the risk of session replay
- Support simplified, secure device onboarding and account management
- Streamline IT operations with a robust solution that integrates effortlessly with your device fleet and reduces the onus of device setup, account creation, and password management
- Acquire freedom from legacy systems
- Simplify your tech stack with a more agile, modern architecture that works in partnership with your MDM solution and ecosystem of tools
What is available today from Okta Device Access?
The roadmap for Okta Device Access is robust, and Okta has plans to deliver new and improved features for Okta Device Access at a steady pace. Currently, Okta Device Access offers a number of capabilities. Please check out the Okta Device Access webpage and datasheet to learn more.
Will a customer be able to deprecate their legacy environment?
Okta Device Access is designed to work with the customer’s existing deployment models. As Okta Device Access matures, the goal is to help customers move away from on-premises infrastructure. However, if the customer still relies on certain aspects of their legacy environment, such as their Active Directory, Okta Device Access will continue to work with their current legacy setup.
Will Okta become an MDM?
No, Okta will continue to partner closely with MDM partners to light up more comprehensive provisioning and compliance use cases. Okta depends on customers providing a 3rd party MDM in order to deploy and configure the features of Okta Device Access.
Is Okta Device Access compliant with HIPAA and FedRAMP?
Okta Device Access is authorized for Okta for Government Moderate (FedRAMP Moderate), Okta for Government High (FedRAMP High), and Okta for US Military (DoD Impact Level (IL) 4 approved for certain IL5 applications and workloads) – Okta's three dedicated, regulated environments of the Okta Identity Cloud.
Okta’s FedRAMP Moderate cell is designed to meet HIPAA requirements, and Okta Device Access is available in this environment.
