Connect Container Image Registries
This is an integration guide for connecting container image registries to Tenable.
- For a how-to guide about viewing and managing container images, see Container Images.
- For a conceptual overview of how Tenable scans registries, see Container Image Registry Scanning.
To enable or disable container registry scanning, perform the following:
-
(AWS only) Grant ECR scanning permissions to Tenable One Cloud Exposure.
Note: For Azure (ACR), GCP (Artifact Registry), OCI (OCIR), and Alibaba Cloud (ACR), no additional permissions need to be granted. The basic, VM scanning permissions suffice. See Connect Workloads for more information about granting VM scanning permissions. -
Add registries to Cloud Exposure:
- Add a JFrog Organization to Cloud Exposure.
-
Add a Cloudsmith Organization to Cloud Exposure.
Note: Cloudsmith can only be added via the organization integration flow. - Add 3rd Party Registries to Cloud Exposure.
- (All registries) Enable or Disable Container Registry Scanning in Tenable.
AWS: Grant ECR Scanning Permissions
Grant Cloud Exposure permissions to scan AWS container registries via a custom, inline policy added to the Tenable IAM role. These permissions are granted as part of the AWS integration process in the Tenable wizard (via the ECR Scanning permission), but, depending on when you connected your account/s, may not have been granted yet.
- If you already connected the AWS account where you want to scan container registries, but haven’t yet added container registry scanning permissions, perform the following procedure.
- If you did not yet connect the AWS account where you want to scan container registries, perform the procedure documented in Connect an AWS Account.
To verify whether or not you have already added container registry scanning permissions, navigate to Settings > Accounts > AWS in the Cloud Exposure Console, and check the status of the account.
- If the status is Connected, the required permissions have already been granted.
- If the status is Connected with issues, and the tooltip indicates that container registry scanning permissions have not been granted, perform the following steps.
To grant permissions:
- In the AWS Management Console of the relevant account, navigate to IAM > Roles and open the role that you created for Tenable during account integration.
- In the Permissions tab, click Add permissions > Create inline policy.
-
Copy the following policy, and paste it into the JSON tab to replace the existing text.
CopyJSON
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ecr:GetAuthorizationToken",
"ecr:GetDownloadUrlForLayer",
"ecr:BatchGetImage"
],
"Resource": "*"
}
]
} - Click Review policy.
- Enter a name for the policy (for example, TenableWorkloadProtection) and then click Create policy.
- In the Cloud Exposure Console, navigate to Settings > Accounts > AWS, and verify that the Status of the account is Connected.
AWS: ECR Scanning Policy
JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ecr:GetAuthorizationToken",
"ecr:GetDownloadUrlForLayer",
"ecr:BatchGetImage"
],
"Resource": "*"
}
]
}
Add a JFrog Organization
Add a JFrog organization to scan all container registries within the organization.
Cloud Exposure supports organizations with both internet-facing and network-isolated servers. See Connect Network-Isolated Servers for more information about working with network-isolated servers.
After you add an organization, Tenable:
- Connects to the registries in the organization.
- Pulls a list of repositories within each registry.
- Scans the repositories for inventory items.
- Scans the images for vulnerabilities.
- Displays the images and repositories as resources in the Inventory.
- Displays the registry as part of the account hierarchy within the Cloud Exposure Console, allowing you to view and configure features in the Console for a specific registry or group of registries.
To add a JFrog organization:
- In the Cloud Exposure Console, navigate to Settings > Integrations and click Add Integration.
- In the Integrations Library, click JFrog Organization. The Add JFrog Organization wizard opens.
- Enter a display Name for your registry, as it will appear in the Accounts and Settings pages.
-
Select how Tenable connects to your server. If your server is network-isolated, use a Tenable Endpoint Connector to establish connection:
- Endpoint (internet-facing registry) — Enter the hostname/IP of your registry.
- Via endpoint connector (network-isolated registry) — Select the relevant connector from the dropdown. If none are available, add one.
Check Accept any server SSL certificates if SSL is enabled for the server.
-
Enter the following information for your organization:
- Username — The username for your registry.
- Password — This can be your password to log in to the registry, or you can set up a specific token within the vendor platform.
- Automatically update folder structure. Mirror your registry's structure as folders within Tenable, preserving its hierarchy and keeping the view synchronized (enabled by default). Learn more about account hierarchy.
- Click Finish.
Add a Cloudsmith Organization
Add a Cloudsmith container registry organization to scan all container registries within the organization.
Cloud Exposure supports organizations with both internet-facing and network-isolated servers. See Connect Network-Isolated Servers for more information about working with network-isolated servers.
After you add an organization, Tenable:
- Connects to the registries in the organization.
- Pulls a list of repositories within each registry.
- Scans the repositories for inventory items.
- Scans the images for vulnerabilities.
- Displays the images and repositories as resources in the Inventory.
- Displays the registry as part of the account hierarchy within the Cloud Exposure Console, allowing you to view and configure features in the Console for a specific registry or group of registries.
To add a Cloudsmith organization:
- In the Cloud Exposure Console, navigate to Settings ** > Integrations and click Add Integration.
- In the Integrations Library, click Cloudsmith Organization. The Cloudsmith Organization wizard opens.
- Enter a display Name for your registry, as it will appear in the Accounts and Settings pages.
-
Select how Tenable connects to your server. If your server is network-isolated, use a Tenable Endpoint Connector to establish connection:
- Cloudsmith default endpoint (docker.cloudsmith.io:443) — Enter the Cloudsmith default endpoint.
- Endpoint (internet-facing) — Enter the hostname/IP of your registry.
- Via endpoint connector (network-isolated registry) — Select the relevant connector from the dropdown. If none are available, add one.
- Check Accept any server SSL certificates if SSL is enabled for the server.
- Enter the API key for your Cloudsmith service account.
- Automatically update folder structure. Mirror your registry's structure as folders within Tenable, preserving its hierarchy and keeping the view synchronized (enabled by default). Learn more about account hierarchy.
- Click Finish.
Add 3rd Party Registries
To work with 3rd party registries that are not hosted natively within cloud provider environments, you need to add the registry to Cloud Exposure. Tenable leverages the Docker Registry HTTP API V2 specification. As a result, you can generally integrate any container registry that supports this protocol.
The following vendors were tested and approved:
-
JFrog
Note: In addition to adding individual registries, you can also add an entire JFrog organization to connect all registries within the organization. - Red Hat Quay
- Sonatype Nexus Repository
- Harbor
Cloud Exposure supports registries with both internet-facing and network-isolated servers. See Connect Network-Isolated Servers for more information about working with network-isolated servers.
After you add a registry, Tenable:
- Connects to the registry.
- Pulls a list of repositories within the registry.
- Scans the repositories for inventory items.
- Scans the images for vulnerabilities.
- Displays the images and repositories as resources in the Inventory.
- Displays the registry as part of the account hierarchy within the Cloud Exposure Console, allowing you to view and configure features in the Console for a specific registry or group of registries.
To add an independent registry:
- In the Cloud Exposure Console, navigate to Settings > Integrations and click Add Integration.
- In the Integrations Library, click Cloudsmith Organization. The Add Cloudsmith Organization wizard opens.
- Enter a display Name for your registry, as it will appear in the Accounts and Settings pages.
-
Select how Tenable connects to your server. If your server is network-isolated, use a Tenable Endpoint Connector to establish connection:
- Direct (internet-facing registry) — Enter the Endpoint of your registry. For a Quay registry, enter quay.io
- Via endpoint connector (network-isolated registry) — Select the relevant connector from the dropdown. If none are available, add one.
Check Accept any server SSL certificates if SSL is enabled for the server.
-
Enter the following information for your registry:
- Username — The username for your registry.
- Password — This can be your password to log in to the registry, or you can set up a specific token within the vendor platform.
- Automatically update folder structure. Mirror your registry's structure as folders within Tenable, preserving its hierarchy and keeping the view synchronized (enabled by default). Learn more about account hierarchy.
- Click Finish.
Enable or Disable Container Registry Scanning in Tenable
By default, registry scanning is disabled in Cloud Exposure for your entire organization. You can enable scanning via Console settings, and can fine-tune to enable/disable the feature on specific accounts or account scopes. You must be a user with the Administrator role in Cloud Exposure to configure this setting.
To enable container registry scanning:
- In the Cloud Exposure Console, click on Settings > Workload > Container Registry.
- Select an account scope in the Organization tree on the left. By default, the entire Organization (all accounts) is selected.
-
In the Container Registry Scanning section, choose whether to:
Inherit the configuration of the parent-level account scope (default).
Note: If you selected the entire Organization as the scope, the Inherit option is not available.- Override the configuration of the parent-level scope with a unique configuration (Enabled/Disabled) for this account scope. The unique configuration remains on the child-level scope, regardless of any changes made in the parent-level scope.