Enable the Assured Open Source Software free tier

This page describes how to enable the Assured Open Source Software free tier. To use the Assured OSS premium tier with Security Command Center, see Integrate Assured OSS with Security Command Center.

Before you begin

To use the free tier of Assured Open Source Software (Assured OSS), you must submit the customer enablement form. Complete the steps in this section before you fill out the form.

Create accounts

You require at least one service account or Amazon Web Services (AWS) account to access the following:

  • Google-managed Artifact Registry for the Assured OSS curated packages.
  • Google-managed Artifact Analysis APIs for the enriched package metadata.
  • Secured Cloud Storage bucket with corresponding SPDX, VEX, package health and license files.
  • Pub/Sub topic for notification on package status and vulnerability updates.
  • Scripts for performing signature verification, downloading metadata, and generating Python requirements.txt files.
  • The Assured OSS APIs.

In total, you can provide up to ten identities across both Google Cloud service accounts or AWS account IDs. Though you can use existing accounts, we recommend that you create new accounts to use exclusively for Assured OSS.

To use Assured OSS directly with Artifact Registry (without enabling a proxy), one of the service accounts that you must provide is the Artifact Registry Service Agent for the project you want to use Assured OSS with.

To create service accounts, see Create service accounts. To see the existing service accounts in a project, see List and edit service accounts.

To obtain your Amazon Web Services (AWS) account ID, see Your AWS account ID and its alias.

Set up Pub/Sub notifications

You can receive notifications when images are uploaded, new tags are added, or images are deleted.

To set up Pub/Sub so that you can receive notifications, see Configuring Pub/Sub notifications.

Complete the enrollment form

  1. Go to the customer enablement form.

  2. Set Choose one of the actions to perform to Enable access.

  3. Enter your company name and your contact information, including a valid corporate email address to share enablement confirmation and any opted-in notification emails. Google uses your company name to verify the match with your email address.

  4. Enter the service account and AWS account information.

  5. Add the Pub/Sub endpoint.

  6. Review the terms of service.

  7. Click Submit.

After the request is submitted, you receive a confirmation email indicating the enablement success. In rare cases, the enablement process can take an hour or more.

The Assured OSS system grants the required permissions to access and download software packages and security metadata to the service accounts.

Other enrollment website capabilities

In addition to enabling your initial access to the Assured OSS service, the enrollment website lets you perform several configuration and management actions.

Add additional service accounts or AWS account IDs to be enabled for Assured OSS access

Complete and submit additional instances of the customer enablement form with your corporate email ID if you need to add additional service accounts or AWS account IDs that need access to Assured OSS. The corporate email address can be same or different from previous form submissions. The corporate email must belong to the same company domain. After the request is submitted, you receive a confirmation email indicating the enablement success. In rare cases, the enablement process can take an hour or more.

Update your notification preferences

If you want to modify notification preferences for specific registered corporate email identities, complete and submit the access form with Update notification preferences selected. Note that updating notification preferences requires approval and confirmation from the registered administrator. This process happens offline. You receive a confirmation email after the process is completed.

Disable one or more enabled service accounts or AWS account IDs from access

If you want to disable access from specific registered service accounts or AWS account IDs, complete and submit the access form with Disable access selected. Note that disabling access requires approval and confirmation from the registered administrator and is an offline process. You receive a confirmation email after the process is completed.

Halt usage and access and disconnect from the service completely

If you want to halt all access and usage and disconnect from the service completely, complete and submit the access form with Close all access selected. Note that halting all access and usage and disconnecting from the service requires approval and confirmation from the registered administrator and is an offline process. You receive a confirmation email after the process is completed.

What's next