Skip to main content

Asset Panda

Visualize Asset Panda users and assets, and monitor changes through queries and alerts.

Installation​

For this integration, you will need to acquire and provide the following within JupiterOne:

  1. An Asset Panda Email and Password: You need to enter the e-mail and password you would use to log into your account when going to the asset panda web application on the website. It is recommended to create a service account used for creating your token.
  2. The Asset Mapping Configuration JSON File: A JSON file that defines the mapping between Asset Panda assets and JupiterOne entities. It specifies the Group ID of the asset to be ingested and the Entity Class used to classify the corresponding JupiterOne entity. The entity classes can be found here

The Asset Mapping Configuration JSON file should adhere to the following structure:​

{
  "groups": [
    {
      "groupId": 123,
      "_class": "Host",
      "propertyToFieldMap": {
        "hostname": "field_12",
        "model": "field_24",
        "os": null
      }
    },
    {
      "groupId": 456,
      "_class": "Site",
      "propertyToFieldMap": {
        "displayName": "field_1",
        "officeCode": "field_2",
        "address": "field_3",
        "region": "field_4"
      }
    },
  ],
  "relationships": [
    {
      "_class": "HAS",
      "sourceGroupId": 123,
      "sourceField": "field_48",
      "targetGroupId": 456,
      "targetField": "id"
    }
  ]
}

Key descriptions:​

groups: An array of objects that define the mapping between Asset Panda groups and JupiterOne entities.​
  1. groupId (Required):
  • Type: number
  • Description: A unique identifier for the group. This ID must exist and be valid in Asset Panda.
  1. _class (Required):
  • Type: string
  • Description: The name of the class representing the schema. This must correspond to a valid class name in JupiterOne's data model schema repository.
  1. propertyToFieldMap (Required):
  • Type: object
  • Description: A mapping of property names to field names. Each property represents an entity property in the JupiterOne schema, and its value is the field to which it maps in the Asset Panda asset.
    • Keys: Property names (string)
    • Values: Field names (string) or null if no mapping is provided.
  • For the specified _class, all required properties from the schema must be included in propertyToFieldMap. Missing properties will cause validation to fail. You can find the required properties in the data model schema.
  • Fields not found in the JupiterOne schema can be added as additional properties.
relationships: Relationships define how entities in Asset Panda relate to one another in JupiterOne. The _class field must be a valid relationship type in the JupiterOne data model.​
  1. _class (Required):
  • Type: string
  • Description: The name of the class representing the relationship. Examples of possible relationship classes can be found in the JupiterOne documentation here.
  1. sourceGroupId (required):
  • Type: number
  • Description: A unique identifier for the source group. This ID must exist and be valid in Asset Panda.
  1. sourceField (required):
  • Type: string
  • Description: The field in the source group that contains the identifier for the target entity. This field must exist and hold valid values.
  1. targetGroupId (required):
  • Type: number
  • Description: A unique identifier for the target group. This ID must exist and be valid in Asset Panda.
  1. targetField (optional, default: id):
  • Type: string
  • Description: The field in the target group that corresponds to the source entity's reference field. This field must exist and hold valid values. When this field is id, the sourceField must be of type EntityListField in Asset Panda.

How to find the group ID in Asset Panda:​

  1. Open Group Settings:
- Log in to the Asset Panda web application.
- Click on the Cog icon in the top-right corner.
- Select Group Settings from the dropdown menu.
  1. Select the Desired Group:
- In the Group Settings, locate and click on the group you want to ingest.
  1. Copy the Group ID:
- Once the group is selected, look at the URL in your browser's address bar.
- The Group ID will be part of the URL. Copy this ID for your use.

How to find the field keys in Asset Panda:​

  1. Open Developer Tools:
- Go to the Asset Panda web application in your browser.
- Right-click anywhere on the page and select Inspect or Inspect Element to open the developer tools.
  1. Access the Network Tab:
- In the developer tools, click on the Network tab.
- Reload the page to capture all network requests.
  1. Filter Requests:
- Use the search bar or filter options to search for requests containing the term "fields".
  1. View the Request Details:
- Select the relevant network request.
- Go to the Preview tab in the request details.
  1. Locate the Field Keys:
- In the list of field objects displayed under the Preview tab, look for the property labeled "key". This is the field key you need.

Configuration in JupiterOne​

To install the Asset Panda integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Asset Panda. Click New Instance to begin configuring your integration.

Creating a configuration requires the following:

  • The Account Name used to identify the Asset Panda account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Your Asset Panda Email and Password.

  • The Asset Mapping Configuration JSON File that defines the mapping between Asset Panda assets and JupiterOne entities.

Click Create once all values are provided to finalize the integration.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.