Setting up trusted image policies

By default, users in your project can create persistent disks or copy images using any of the public images and any images that principals can access through IAM roles. However, in some situations you might want to restrict principals so that they can create boot disks only from images that contain approved software that meets your policy or security requirements.

Use the Trusted image feature to define an organization policy that allows principals to create persistent disks only from images in specific projects.

To restrict the locations where your images can be used, read restricting use of your shared images, disks, and snapshots.

Before you begin

  • Read the Using constraints page to learn about managing policies at organization level.
  • Read the Understanding hierarchy evaluation page to learn how organization policies propagate.
  • If you haven't already, set up authentication. Authentication is the process by which your identity is verified for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine as follows.

    Select the tab for how you plan to use the samples on this page:


    When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.


    1. Install the Google Cloud CLI, then initialize it by running the following command:

      gcloud init
    2. Set a default region and zone.


    To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.

      Install the Google Cloud CLI, then initialize it by running the following command:

      gcloud init

    For more information, see Authenticate for using REST in the Google Cloud authentication documentation.


  • Trusted image policies do not restrict access to the following images:

    • Custom images in your local project.

    • Image files in Cloud Storage buckets.

  • Trusted image policies do not prevent users from creating image resources in their local projects.

Set image access constraints

Enact an image access policy by setting a compute.trustedImageProjects constraint on your project, your folder, or your organization. You must have permission to modify organization policies to set these constraints. For example, roles/orgpolicy.policyAdmin has permission to set these constraints. For more information about managing policies at the project, folder, or organization level, see Using constraints.

You can set constraints on all public images available on Compute Engine. For a list of image project names, see Operating systems details. You can also restrict the Machine Learning (ML) images that are available on Compute Engine by using the ml-images project. If you are using Serverless VPC Access, grant your project permission to use Compute Engine VM images from the serverless-vpc-access-images project.

Use the Google Cloud console or Google Cloud CLI to set constraints on image access.


For example, to set a constraint at the project level, do the following:

  1. Go to the Organization policies page.

    Go to Organization policies

  2. From the policies list, click Define trusted image projects. The Policy details page displays.

  3. On the Policy details page, click Manage Policy. The Edit policy page displays.

  4. On the Edit policy page, select Customize.

  5. For Policy enforcement, select an enforcement option. For information about inheritance and the resource hierarchy, see Understanding Hierarchy Evaluation.

  6. Click Add rule.

  7. In the Policy values list, you can select whether this organization policy should allow access to all image projects, deny access to all image projects, or you can specify a custom set of projects to allow or deny access to.

    To set the policy rule, complete one of the following options:

    • To allow users to create boot disks from all public images, select Allow All.
    • To restrict users from creating boot disk from all public images, select Deny All.
    • To specify a select set of public images that users can create boot disks from, select Custom. A Policy type and Custom values field displays.

      1. In the Policy type list, select Allow or Deny.
      2. In the Custom values field, enter the name of the image project using the projects/IMAGE_PROJECT format.

        Replace IMAGE_PROJECT with the image project you want to set the constraint on.

        You can add multiple image projects. For each image project that you want to add, click Add and enter the image project name.

  8. To save the rule, click Done.

  9. To save and apply the organization policy, click Save.

For more information about creating organization policies, see Creating and managing organization policies.


For example, to set a constraint at the project level, do the following:

  1. Get the existing policy settings for your project by using the resource-manager org-policies describe command.

    gcloud resource-manager org-policies describe \
       compute.trustedImageProjects --project=PROJECT_ID \
       --effective > policy.yaml

    Replace PROJECT_ID with your project ID.

  2. Open the policy.yaml file in a text editor and modify the compute.trustedImageProjects constraint. Add the restrictions that you need and remove the restrictions that you no longer require. When you have finished editing the file, save your changes. For example, you might set the following constraint entry in your policy file:

    constraint: constraints/compute.trustedImageProjects
        - projects/debian-cloud
        - projects/cos-cloud
        - projects/IMAGE_PROJECT

    Replace IMAGE_PROJECT with the name of the image project that you want to restrict in your project.

    Optionally, you might want to deny access to all images outside of the custom images in your project. For that situation, use the following example:

    constraint: constraints/compute.trustedImageProjects
     allValues: DENY

  3. Apply the policy.yaml file to your project. If your organization or folder has existing constraints, those constraints might conflict with project-level constraints that you set. To apply the constraint, use the resource-manager org-policies set-policy command.

    gcloud resource-manager org-policies set-policy \
       policy.yaml --project=PROJECT_ID

    Replace PROJECT_ID with your project ID.

When you have finished configuring the constraints, test those constraints to ensure that they create the restrictions that you need.

What's next