JupiterOne + OneLogin Integration
Navigate SecOps complexity by connecting Users, Endpoints and Devices with their access to resources in your digital environment by leveraging JupiterOne’s OneLogin 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 data from OneLogin, security teams are able to connect all of the digital assets in their environment with the specific users that have access.
Overview of the OneLogin Integration
JupiterOne provides a managed integration with OneLogin. The integration connects directly to OneLogin APIs to obtain account metadata and analyze resource relationships. Customers authorize access by creating an API token in your target OneLogin account and providing that credential to JupiterOne.
Instructions on creating an API token within your OneLogin account can be found here.
OneLogin Ingested Resources
The following entity resources are ingested when the integration runs:
| OneLogin Entity Resource | _type : _class of the Entity |
|---|---|
| Account | onelogin_account : Account |
| Group | onelogin_group : UserGroup |
| OneLogin Role | onelogin_role : AccessRole |
| User | onelogin_user : User |
| App | onelogin_app : Application |
| Personal App | onelogin_personal_app : Application |
Powering Security Operations for
