An Integration is a way to organize Targets.
Integrations come in two flavors:
Symbolic type Integration do not need credentials or any connection information. The Targets associated with the symbolic type Integrations act as buckets for the findings.
- Artifact - represents an application build bundle such as in a CI/CD pipeline.
- Custom - represents a host, an IP address, a URL, etc.
Repository type Integrations are connecting to a customer’s source code management system, container repository, etc. and will need connection information like credentials to connect to those systems. The Targets associated with the repository type Integrations represent each repository.
- JFrog Artifactory Docker - see Add Integration - JFrog Artifactory Docker .
- AWS - see Integration Guide - AWS .
- Azure Repo - represents a repository in Azure code repository.
- AWS Direct - represents a resource in an AWS account/VPC.
- AWS ECR - represents a repository in ECR.
- BitBucket - represents a repository in bitbucket.org or BitBucket server.
- AWS Account - represents access to an AWS account. Used for Prowler - AWS Environment Scan .
- Docker - represents a Docker image.
- GitHub - represents a repository in github.com or a GitHub server.
- Gitlab - represents a repository in gitlab.com or a GitLab server.
- Virtual Target (beta) - see the article Virtual Targets .
Additionally, only one Integration is needed per Target type.
See our Integration name recommendations here.