JupiterOne + Okta Integration
Navigate SecOps complexity by connecting Users, Endpoints and Devices with their access to resources in your digital environment by leveraging JupiterOne’s Okta Integration.
The Importance of using Single-Sign On
Securely connecting users with the appropriate technologies and notifying security teams if a new, unexpected relationship occur is critical for maintaining organization security. Employees are expected to maintain an overwhelming list of secure passwords as more tools and technologies are leveraged by companies. SSO streamlines the logging-in process for employees by centralizing it.
By combining JupiterOne’s relationship-based data model with the Okta Identity Cloud, security teams are able to connect all of the digital assets in their environment with the specific users that have access.
Overview of the Okta Integration
JupiterOne provides a managed integration with Okta. The integration connects directly to Okta APIs to obtain account metadata and analyze resource relationships. Customers authorize access by creating an API token in your target Okta account and providing that credential to JupiterOne.
The JupiterOne + Okta Integration works with organizations leveraging Okta’s SAML 2.0 solution. JupiterOne is a part of the Okta Integration Network.
Okta Integrated Services
- Single-Sign On
- SAML 2.0
Okta Ingested Resources
| Okta Entity Resource | _type : _class of the Entity |
|---|---|
| Account | okta_account : Account |
| Application | okta_application : Application |
| Application Group | okta_app_user_group : UserGroup |
| MFA Factor | mfa_device : [Key,AccessKey] |
| Okta Group | okta_user_group : UserGroup |
| User | okta_user : User |
Powering security operations for any SaaS provider or cloud solution
