Skip to main content

Artifactory

Visualize JFrog Artifactory repository groups, code repositories, builds, keys, permissions, user groups, and users, and monitor changes through queries and alerts.

Installation​

For this integration, JupiterOne requires the namespace of your Artifactory account. It also requires are a Client Access Token, Client Pipeline Access Token, and the Client Administrator Name that granted the access tokens.

Configuration in Artifactory​

Configure API access tokens in Artifactory using the instructions in the Access Tokens guide.

Data Volume Configuration​

Control how much data is ingested from Artifactory to manage storage and processing.

Ingestion Windows (Time Ranges)​

FieldDescriptionDefaultOptions
Artifacts Ingestion WindowIngest artifacts created within the last X days3030, 60, 90, 365

How it affects data volume: A longer ingestion window retrieves more artifacts from Artifactory, increasing the number of artifact entities stored in JupiterOne.

Data Filtering Options​

FieldTypeDescriptionDefault
Included Vulnerability SeveritiesMulti-selectSelect vulnerability severities to ingestMedium, High, Critical
Include Repository ArtifactsArrayComma-separated list of repositories from which artifacts will be ingested. Excludes all others.None (all repositories)

How it affects data volume:

  • Severity filtering reduces vulnerability entities by excluding low-severity findings. By default, only Medium, High, and Critical vulnerabilities are ingested.
  • Repository filtering limits artifact ingestion to specified repositories, significantly reducing data when only specific repositories are needed.

Configuration in JupiterOne​

To install the JFrog Artifactory integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Artifactory. Click New Instance to begin configuring your integration, providing the following:

  • Account Name used to identify the JFrog Artifactory account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName option 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.

  • Client Namespace of your Artifactory account.

  • Client Access Token configured in your Artifactory account.

  • Client Pipeline Access Token configured in your Artifactory account.

  • Client Administrator Name, or username of the administrator who granted the Artifactory access tokens.

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.