-
Entity and Relationship Metadata
The following metadata is assigned by JupiterOne internally to entities and relationships. All internal metadata has _ prefix to the property name. Class, Type, Key and ID Property Type Description_class string | string[] The abstract class label(s) assigned to an entity/relationship. An entity can have multiple class…
-
Global Mappings
jupiterone_account <-OWNS- <ROOT> security_policy <-HAS- <ROOT> (Service|Control|Team) -IMPLEMENTS-> security_procedure employee <-EMPLOYS- <ROOT> Domain <-OWNS- <ROOT> Organization -HAS-> Person Team -HAS-> Person Team <-MANAGES- Person Team <-HAS- Organization Team <-HAS- <ROOT> Document <-APPROVED- Person Document…
-
Integrations Mappings
pingidentity Mappings pingidentity_account <-OWNS- <ROOT> pingidentity_account <-HOSTS- Vendor signal-sciences Mappings signal_sciences_account <-OWNS- <ROOT> signal_sciences_account <-HOSTS- Vendor godaddy Mappings godaddy_account <-OWNS- <ROOT> bitbucket Mappings bitbucket_workspace <-HOSTS- Vendor bitbucket_workspace…
-
JupiterOne Data Model
The JupiterOne Data Model is a reference model used to describe digital resources and the complex interconnections among all the resources in a technology organization as an entity-relationship graph. The data model is defined by a set of Entities and their Relationships. It represents a reference model, not a strict or…
-
JupiterOne Data Model for AWS IAM Access and Trusts
The Identity and Access Model for the JupiterOne AWS integration shows which assets are ingested and the relationships that are created. A graph view of this model is available in your JupiterOne account after you turn on the AWS integration and starting ingesting data to your account.
-
JupiterOne Data Model for Governance, Risk, and Compliance (GRC)
As we build integrations for Governance, Risk and Compliance (GRC) products we start with a reference model like this and attempt to collect these types of entities and map these kinds of relationships so that customers using GRC products will be able to use similar queries for any GRC product integrated with JupiterOne.…
-
JupiterOne Data Model for Network and Endpoint Infrastructure
As we build integrations for network and endpoint protection products we start with this reference model and attempt to collect these types of entities and map these kinds of relationships so that customers using these products will be able to use the same queries for any network or endpoint product integrated with…
-
JupiterOne Data Model for Organization, Account, and Vendor Management
As we build integrations for products that have organization, account, or vendor management features we start with this reference model and attempt to collect these types of entities and map these kinds of relationships so that customers using these products will be able to use the same queries for any product integrated…
-
JupiterOne Data Model for People and Access
As we build integrations for products that include user or people account along with different access levels or permissions we start with this reference model and attempt to collect these types of entities and map these kinds of relationships so that customers using these products will be able to use the same queries for…
-
JupiterOne Data Model for Vulnerability Management
As we build integrations for products that identify findings and vulnerabilities we start with this reference model and attempt to collect these types of entities and map these kinds of relationships so that customers using these products will be able to use the same queries for any integration they have enabled. Based on…
.png)