JupiterOne's asset inventory, search and visualization supports any data imported that follows the reference data model, not limited to data ingested by managed integrations.
This is easily done via the API or CLI. Each entity object can be represented in a few lines of JSON or YAML code. The J1 API Client or CLI can create/update them to your JupiterOne account. You can also develop a script to run on a schedule (e.g. via a cron job) or integrate into your DevOps automation.
The Person entities are “mapped” from
User entities. They are considered
"shared" entities that multiple integrations can map to and contribute
properties to. For example, a
Person can be created by a Google integration
google_user). Or from a Github User, AWS IAM User, etc.
Person entities represent actual individuals in the organizations, whereas
User entities are the logical user accounts within each digital
environment/account (i.e. from an integration).
Person entity is created by the "mapper" process -- when a
User entity is
ingested/updated from an identity provider integration (e.g. Okta, OneLogin,
Person entity is "mapped" with the user's information (first and
last name, email address, etc.).
Certain properties are used to determine if the user is a system user or an actual individual. This depends on the integration.
For Okta, you can set the
userType property for the user to one of the
following to avoid it being mapped to a
On this page:Integrations and Mapping Related Questions How do I get my custom / on-premise data into JupiterOne? Where do these
Personentities come from? Why are they not tagged with an integration? How are
employees) created? How can I avoid creating a
Personentity for a generic/system user account?