Define and manage your high-value resource set

Note: This feature is available for both Security Command Center Enterprise and Premium tiers, though some functionality may be limited in the Premium tier.

This page shows you how to create, edit, delete, and view resource value configurations.

Use resource value configurations to create your high-value resource set. Your high-value resource set determines which of your resource instances (referred to as resources) the attack path simulations consider high-value resources.

You can define resource value configurations for the resources on Google Cloud or, if you have the Enterprise tier of Security Command Center, for resources on the other cloud service providers that Security Command Center is connected to.

When attack path simulations run, they identify attack paths and calculate attack exposure scores for resources that are designated as high-value resources and for Vulnerability class and Misconfiguration class findings.

Attack path simulations can run up to four times a day (every six hours). As your organization grows, simulations take longer, but they will always run at least once a day. Simulation runs are not triggered by the creation, modification, or deletion of resources or resource value configurations.

For an introduction to high-value resource sets and resource value configurations, see High-value resource sets.

Before you begin

To get the permissions that you need to view and work with resource value configurations, ask your administrator to grant you the following IAM roles on your organization:

• Resource value config editor (roles/securitycenter.resourceValueConfigEditor)
• Resource value config viewer (roles/securitycenter.resourceValueConfigsViewer)
• Security Center Settings Editor (roles/securitycenter.settingsEditor)

For more information about granting roles, see Manage access.

You might also be able to get the required permissions through custom roles or other predefined roles.

Create a resource value configuration

You create resource value configurations by using the Attack path simulation tab on the Security Command Center Settings page in the Google Cloud console.

To create a resource value configuration, click the tab for your cloud service provider and follow the steps:

Google Cloud

1. Go to the Attack path simulation page in Security Command Center Settings:

   Go to Settings

2. Select your organization. The Attack path simulation page opens.

3. Click Create new configuration. The Create resource value configuration panel opens.

4. In the Name field, specify a name for this resource value configuration.

5. Optional: Enter a description of the configuration.

6. Under Cloud provider, select Google Cloud.

7. In the Select scope field, click Select and use the project browser to select a project, folder, or the organization. This configuration applies only to resource instances in the specified scope.

8. In the Select resource type field, click in the field to display the drop-down menu and select a resource type or Any. The configuration applies to instances of the specified resource type or, if you select Any, to instances of all supported resource types. Any is the default.

9. Optional: In the Label section, click Add label to specify one or more labels. When a label is specified, the configuration only applies to resources that include the label in their metadata.

   If you apply a new label to any resources, it can take several hours before the label is available for matching by a configuration.

10. Optional: In the Tag section, click Add tag to specify one or more tags. When a tag is specified, the configuration only applies to resources that include the tag in their metadata.

    If you define a new tag for any resources, it can take several hours before the tag is available for matching by a configuration.

11. Set the priority value for the matching resources by specifying one of the following options:

    • Optional: If you use Sensitive Data Protection, enable Security Command Center to automatically set the priority value of supported data resources based on data-sensitivity classifications from Sensitive Data Protection by following these steps:

      1. Click the slider next to Include discovery insights from Sensitive Data Protection.
      2. In the first Assign resource value field, select the priority value to assign to matching resources that contain high-sensitivity data.
      3. In the second Assign resource value field, select the priority value to assign to matching resources that contain medium-sensitivity data.

    • In the Select resource value field, select a value to assign to the resource instances. This value is relative to the other resource instances in your high-value resource set. The value is used during the calculation of attack exposure scores.

12. Click Save.

AWS

Enterprise tier only: This feature is available only with the Security Command Center Enterprise tier.

Before Security Command Center can return attack exposure scores and attack paths for the resources that you specify in a resource value configuration, Security Command Center must be connected to AWS. For more information, see Multicloud support.

1. Go to the Attack path simulation page in Security Command Center Settings:

   Go to Settings

2. Select your organization. The Attack path simulation page opens.

3. Click Create new configuration. The Create resource value configuration panel opens.

4. In the Name field, specify a name for this resource value configuration.

5. Optional: Enter a description of the configuration.

6. Under Cloud provider, select AWS.

7. Optional: In the Account ID field, enter a 12-digit AWS account ID. If unspecified, the resource value configuration applies to all AWS accounts that are specified in the AWS connection configuration.

8. Optional: In the Region field, enter an AWS region. For example, us-east-1. If unspecified, the resource value configuration applies to all AWS regions.

9. In the Select resource type field, click in the field to display the drop-down menu and select a resource type or Any. The configuration applies to instances of the specified resource type or, if you select Any, to instances of all supported resource types. Any is the default.

10. Optional: In the Tag section, click Add tag to specify one or more tags. When a tag is specified, the configuration only applies to resources that include the tag in their metadata.

    If you define a new tag for any resources, it can take several hours before the tag is available for matching by a configuration.

11. In the Select resource value field, select a priority value to assign to the resource instances. This value is relative to the other resource instances in your high-value resource set. The value is used during the calculation of attack exposure scores.

12. Click Save.

The new configuration is reflected in the attack exposure scores and attack paths only after the next attack path simulation runs.

Edit a configuration

Except for the name, you can update any specification in a resource value configuration.

To update an existing resource value configuration, follow these steps:

1. Go to the Attack path simulation page in Security Command Center Settings:

   Go to Settings

2. Select your organization. The Attack path simulation page opens with the existing configurations displayed.

3. In the Configuration name column, click the name of the configuration that you need to update. The Edit resource value configuration page opens.

4. Update the specifications in the configuration as needed.

5. Optional: Click Preview matching resources to see how many resources match the updated configuration matches and a list of the individual matching resource instances.

6. Click Save.

The changes are reflected in the attack exposure scores and attack paths only after the next attack path simulation runs.

Delete a configuration

To delete a resource value configuration, follow these steps:

1. Go to the Attack path simulation page in Security Command Center Settings:

   Go to Settings

2. Select your organization. The Attack path simulation page opens.

3. Under Resource value configurations on the right side of row for the configuration you need to delete, display the actions menu by clicking the vertical dots. If you don't see the vertical dots, scroll to the right.

4. From the displayed action menu, select Delete.

5. In the confirmation dialog, select Confirm.

   The configuration is deleted.

View a configuration

You can view all existing resource value configurations on the Attack path simulation page in Security Command Center Settings.

1. To view a particular resource value configuration, go to the Attack path simulation page

   Go to Settings

2. Select you organization. The Attack path simulation page opens.

3. Under Resource value configurations on the Attack path simulation page, scroll the list of resource value configurations until you find the configuration that you need.

4. To see the configuration properties, click the name of the configuration. The properties are displayed on the Edit resource value config page.

Troubleshooting

If you receive errors after creating, editing, or deleting resource value configurations, check for SCC Error class findings in the Google Cloud console by following these steps:

1. Go to the Findings page in the Google Cloud console:

   Go to Findings

2. In the Quick filters panel, scroll to the Finding class section and select SCC Error.

3. In the Findings query results panel, scan the findings for the following SCC Error findings and click on the category name:

   • APS no resource value configs match any resources
   • APS resource value assignment limit exceeded

   The finding details panel opens.

4. In the finding details panel, review the information in the Next steps section.

To review the remediation instructions for the attack path simulation SCC Error findings in the documentation, see:

• APS no resource value configs match any resources
• APS resource value assignment limit exceeded

What's next

For information about working with Security Command Center findings, see Work with findings in the Google Cloud console.