Vendors

A vendor refers to a 3rd party that operates within your cloud environment—typically through AWS IAM roles, Microsoft Entra ID Application, GCP service accounts, or integrations. These entities require access to your environment to deliver their services. Accurately mapping vendors improves visibility into external access and strengthens your overall security posture.

The vendor feature allows you to manage 3rd party vendor mappings, providing enhanced visibility and control over external access to your cloud environments.

Note: Vendor settings are available only under the Organization scope. Currently, only AWS accounts and Microsoft Entra ID applications are supported in this feature.

Manage Vendors

You can add, edit, or delete vendor mappings to maintain an accurate view of external access to your environments.

Add a New Vendor

The vendors list consists of Built-in vendors (mapped by Tenable) and Custom vendors (added manually by the user).

To add a new vendor:

  1. In the Tenable One Cloud Exposure Console, Navigate to Console > Settings > Cloud Exposure > Vendors.
  2. Click the + Add Vendor button (top right).
  3. Configure the following:
    1. Enter the vendor's name.
    2. Click + Add to add the relevant AWS account/Microsoft Entra ID application/Microsoft Entra ID application owner/GCP service account.

      Note: You can map multiple values to the same vendor.
  4. (Optional) Select Mark as trusted if the vendor is trusted.
    For more information, see Trusted Vendors.
  5. Click Add.

Edit a Vendor

To edit a vendor:

  1. In the Cloud Exposure Console, navigate to Console > Settings > Cloud Exposure > Vendors.
  2. On the right side of the vendor entry, click on the three dots menu, and then click Edit.

Delete a Vendor

To delete a vendor:

  1. In the Cloud Exposure Console, navigate to Console > Settings > Cloud Exposure > Vendors.
  2. On the right side of the vendor entry, click on the three-dots menu, and then click Delete.
Note: Only custom vendors can be deleted.

Trusted Vendors

The trusted vendor feature allows you to differentiate between types of external access to your environment:

  • Unknown external access may require investigation or removal.
  • Known external access refers to vendors that are mapped to a 3rd party vendor by Tenable or by you.

You can explicitly mark vendors as trusted, which can help you focus on monitoring the external access that truly matters. By default, no vendor is preconfigured as trusted. Trusted status can be assigned manually in the vendor's settings and is clearly indicated in the Console. When you configure a vendor as trusted, Tenable applies the changes after the next data sync.

Configuring a vendor as trusted has the following effects:

Feature Effect
Findings
  • Automatically reduces the severity of findings1 related to that vendor by one level. For example, a Critical severity finding will change to High.
  • Setting the external AWS account ID as a trusted vendor prevents any External IAM Role findings from being generated.
Toxic Combinations Any Toxic Combinations associated with the configured vendor are automatically closed when the vendor is set as trusted. Relevant for the 3rd party identities with access to sensitive data policy.
Enhanced Monitoring Improves monitoring of external access across the product, including in the IAM dashboard, Inventory, and IAM pages.1

1 This impacts the following policies:

  • AWS
    • Overpermissive ECR Repository
    • Overpermissive S3 Bucket
    • Overpermissive Secrets Manager secret
    • Overprivileged IAM role
    • Systems Manager Parameter is exposing a secret
    • EC2 Instance is exposing secrets
    • Inactive IAM role
  • Azure
    • Overprivileged Microsoft Entra ID Application in subscription
    • Logic App is exposing secrets
  • GCP
    • Overprivileged Service Account in project
    • Service Account can impersonate all service accounts in project
    • Service Account is privileged in project

Vendor Visibility across the Console

Vendor mappings impact several features throughout Tenable. Only 3rd party vendors that exist in your environment, and are defined in the vendor settings (either built-in or custom), are reflected across the Console. These vendors appear in key areas, enhancing visibility, simplifying 3rd party tracking, and improving the accuracy of findings.

  • IAM Dashboard — All identified vendors are grouped under a widget titled 3rd Party Vendors. For more information see the documentation.
  • Identity Intelligence — Vendors are displayed in the Explore > Identity Intelligence > Vendor column accompanied by icons. This occurs when a vendor, defined in the vendor settings (built-in or custom), has access to the environment through Service Identities.
  • Permission Query — For external AWS accounts, mapping an additional Account ID to a vendor will associate that account with the vendor’s name, enabling investigation of external access to your environment. When a vendor is added, the vendor’s name that is currently marked as “unknown” in the Permissions Query view is replaced with the vendor’s name.
  • Inventory — Identities operating within your cloud environment as 3rd party vendors are automatically identified and marked in the relevant Inventory tables. These entries appear with a vendor name and identifying icon in the Vendor column. You can use the Vendor filter to easily identify 3rd parties with access to your environment.

Vendor Table Columns

Column Description
Name Displays the vendor logo and name for built-in vendors, or a placeholder logo for custom vendors
Scope Always shown as Organization
Modified Displays Yes for custom or modified built-in vendors, and "–" for all others
Trusted Displays Yes/No if the vendor is trusted/not trusted
Linked Service Identity Indicates if an identity is linked to the vendor