This page explains how to reduce the volume of findings that you receive in Security Command Center by muting findings.
Overview
Muting a finding hides it from the default view of your findings in the Google Cloud console. You can manually or programmatically mute findings and create filters to automatically silence existing and future findings based on criteria you specify.
Finding providers in Security Command Center supply broad security assessments of your Google Cloud deployment, but you might find that certain findings are not appropriate or relevant for your organization or projects. A high volume of findings also can make it difficult for your security analysts to effectively identify and remediate the most critical risks. Mute findings saves you time from reviewing or responding to security findings for assets that are isolated or fall within acceptable business parameters.
Mute findings versus allowlists
Muting findings works differently than existing volume management solutions. Security Health Analytics lets you use dedicated security marks to add assets to allowlists, which stops detectors from creating security findings for specific assets. Security Command Center also lets you disable detectors.
However, muting findings has several advantages over allowlists and disabling detectors:
- You can mute findings without locating their underlying assets.
- Findings that aren't attached to any resources can be muted.
- You can create custom filters to fine-tune mute functionality.
- Muting findings doesn't stop underlying assets from being scanned. Findings are still generated but remain hidden until you decide to view them.
Permissions
To mute findings, you need one of the following Identity and Access Management (IAM) roles at the organization, folder, or project level:
- View mute rules:
- Security Center Admin Viewer (
roles/securitycenter.adminViewer
) - Security Center Settings Viewer (
roles/securitycenter.settingsViewer
) - Security Center Mute Configurations Viewer
(
roles/securitycenter.muteConfigsViewer
)
- Security Center Admin Viewer (
- View, create, update, and delete mute rules:
- Security Center Admin (
roles/securitycenter.admin
) - Security Center Admin Editor (
roles/securitycenter.adminEditor
) - Security Center Settings Editor
(
roles/securitycenter.settingsEditor
) - Security Center Mute Configurations Editor
(
roles/securitycenter.muteConfigsEditor
)
- Security Center Admin (
- Manually mute findings:
- Security Center Findings Editor
(
roles/securitycenter.findingsEditor
)
- Security Center Findings Editor
(
You can also create and grant custom roles with some or all of the following permissions:
- Mute rule read permissions
securitycenter.muteconfigs.get
securitycenter.muteconfigs.list
- Mute rule write permissions
securitycenter.muteconfigs.create
securitycenter.muteconfigs.update
securitycenter.muteconfigs.delete
- Finding write permissions
securitycenter.findings.setMute
securitycenter.findings.bulkMuteUpdate
Your ability to mute findings adheres to roles granted at the organization, folder, or project level. You can mute findings in specific folders or projects, and restrict the ability of others to mute findings based on the access they are granted. For example, if you have access to a single project, you can only mute findings in that project. If you have access to a folder, you can mute findings in any subfolder or project inside that folder.
To learn more about Security Command Center roles, see Access control.
Mute findings
You can manually mute individual findings, silence multiple findings at once with bulk mute filters, or create mute rules that automatically suppress future findings based on filters you define.
Findings contain a mute
attribute that can be set to MUTED
or UNMUTED
.
When you mute and unmute findings, you change the value of the attribute. For
more information, see Mute finding properties.
Muting findings is relevant for many use cases, including the following:
- Assets within non-production environments where some stricter requirements might not be applicable.
- Recommendations to use customer-managed encryption keys in projects that don't contain critical data.
- When granting broad access on a datastore, which intentionally is open to the public and disseminates public information.
- Findings that aren't relevant to your organization or project based on your company's policies.
Muted findings continue to be logged for audit and compliance purposes, and can
be viewed if needed. However, by default, they don't appear in the
Google Cloud console. You also can filter muted findings from
Pub/Sub notifications and Security Command Center API calls using the finding's mute
attribute.
Mute an individual finding
To mute an individual finding, click the tab for the procedure that you want to use.
Console
In the Google Cloud console, go to the Security Command Center Findings page.
If necessary, select your Google Cloud project or organization.
If you don't see the finding that you need to mute in the Findings query results panel, select the category of the finding in the Category section of the Quick filters panel.
Select the checkbox next to the finding that you need to mute. You can select one or more findings.
On the Findings query results action bar, click Mute options, and then select Mute.
The
mute
attribute for the selected findings is set toMUTED
and the finding is removed from the Findings query results panel.
Alternatively, you can mute a finding from its details panel:
- In the Finding query results panel of the Findings page, in the Category column, click the name of an individual finding. The details panel of the finding opens.
- Click Take action.
From the Take action menu, select Mute.
If you select Mute findings like this instead, the Create mute rule page opens where you can create a mute rule for findings of the same type or that include the same
Indicator
attribute.
gcloud
-
In the Google Cloud console, activate Cloud Shell.
At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.
To set a finding's mute state to
MUTED
, use theset-mute
command in the gcloud CLI:gcloud scc findings set-mute FINDING_ID \ --RESOURCE=RESOURCE_ID \ --source=SOURCE_ID \ --mute=MUTED
Replace the following:
FINDING_ID: the ID for the finding you want to mute
To retrieve finding IDs, use the Security Command Center API to list findings. The finding ID is the last part of the
canonicalName
attribute, for example,projects/123456789012/sources/1234567890123456789/findings
/5ee30aa342e799e4e1700826de053aa9.RESOURCE: the parent resource (
project
,folder
, ororganization
), case-sensitiveRESOURCE_ID: the resource ID (project ID, folder ID, or organization ID)
SOURCE_ID: the source ID
For instructions on retrieving a source ID, see Getting the source ID.
Go
Java
Python
REST API
In the API, use the setMute
method to execute
the following request. The request body is an enum that indicates the desired
mute state.
POST https://securitycenter.googleapis.com/v1/RESOURCE/RESOURCE_ID/sources/SOURCE_ID/findings/FINDING_ID:setMute { "mute": "MUTED" }
Replace the following:
- RESOURCE: the parent resource
(
organizations
,folders
, orprojects
) - RESOURCE_ID: the numeric ID for the selected resource
SOURCE_ID: the numeric ID for the source
For instructions on retrieving a source ID, see Getting the source ID.
FINDING_ID: the ID for the finding you want to mute
To retrieve finding IDs, use the Security Command Center API to list findings. The finding ID is the last part of the
canonicalName
attribute, for example,projects/123456789012/sources/1234567890123456789/findings
/5ee30aa342e799e4e1700826de053aa9.
After you mute a finding, its mute
attribute is set to MUTED
.
Muting a finding doesn't affect whether it is active or
not. If an active finding is muted, the state
attribute remains unchanged:
state="ACTIVE"
. The finding is hidden, but remains active until the
underlying vulnerability, misconfiguration, or threat is resolved.
For more information about mute rules, see Create mute rules.
View muted findings in the Google Cloud console
You can view muted findings in the Google Cloud console by editing the finding
query to select findings that include the property value mute="MUTED"
.
For example, the following findings query displays only active findings that are muted:
state="ACTIVE"
AND mute="MUTED"
To display all active findings, both muted and unmuted, omit the
mute
attribute from the query entirely:
state="ACTIVE"
By default, the finding query in the Google Cloud console displays only findings that are not muted.
For more information about editing finding queries, see Create or edit a findings query in the dashboard.
Unmute individual findings
To unmute an individual finding, click the tab for the procedure that you want to use.
Console
In the Google Cloud console, go to the Security Command Center Findings page.
If necessary, select your Google Cloud project or organization.
The Findings page opens with the default query displayed in the Query preview section. The default query filters out muted findings, so you need to edit the query before muted findings appear in the Findings query results panel.
To the right of the Query preview section, click Edit query to open the Query editor.
In the Query editor field, replace the existing mute statement with the following:
mute="MUTED"
Click Apply. The findings in the Findings query results panel are updated to include only muted findings.
If necessary, filter out other muted findings. For example, in the Quick filters panel under Category, select the name of the finding that you need to unmute to filter out all other categories of finding.
Select the checkbox next to the finding that you want to unmute. You can select one or more findings.
On the Findings query results action bar, click Mute Options, and then select Unmute.
The
mute
attribute for the selected findings is set toUNMUTED
and the finding is removed from the Findings query results panel.
Alternatively, you can unmute a finding from its details panel:
- In the Finding query results panel of the Findings page, in the Category column, click the name of an individual finding. The details panel of the finding opens.
- Click Take action.
- From the Take action menu, select Unmute.
gcloud
-
In the Google Cloud console, activate Cloud Shell.
At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.
To set a finding's mute state to
UNMUTED
, use theset-mute
command in the gcloud CLI:gcloud scc findings set-mute FINDING_ID \ --RESOURCE=RESOURCE_ID \ --source=SOURCE_ID \ --mute=UNMUTED
Replace the following:
FINDING_ID: the ID for the finding you want to mute
To retrieve finding IDs, use the Security Command Center API to list findings. The finding ID is the last part of the
canonicalName
attribute, for example,projects/123456789012/sources/1234567890123456789/findings
/5ee30aa342e799e4e1700826de053aa9.RESOURCE: the parent resource (
project
,folder
, ororganization
), case-sensitiveRESOURCE_ID: the resource ID (project ID, folder ID, or organization ID)
SOURCE_ID: the source ID
For instructions on retrieving a source ID, see Getting the source ID
Go
Java
Python
REST API
In the API, use the setMute
method to execute
the following request. The request body is an enum that indicates the desired
mute state.
POST https://securitycenter.googleapis.com/v1/RESOURCE/RESOURCE_ID/sources/SOURCE_ID/findings/FINDING_ID:setMute { "mute": "UNMUTED" }
Replace the following:
- RESOURCE: the parent resource
(
organizations
,folders
, orprojects
) - RESOURCE_ID: the numeric ID for the selected resource
SOURCE_ID: the numeric ID for the source
For instructions on retrieving a source ID, see Getting the source ID
FINDING_ID: the ID for the finding you want to mute.
To retrieve finding IDs, use the Security Command Center API to list findings. The finding ID is the last part of the
canonicalName
attribute, for example,projects/123456789012/sources/1234567890123456789/findings
/5ee30aa342e799e4e1700826de053aa9.
Selected findings are no longer hidden, and the mute
attribute for the
findings is set to UNMUTED
.
Unmuted findings override mute rules
If a user unmutes findings, they remain unmuted even if existing mute rules still match the findings. In effect, unmute actions by users override mute rules.
Unmuted findings are muted again only if a user manually mutes the findings or creates a new matching mute rule in the Google Cloud console. Mute rules created with the gcloud CLI or Security Command Center API won't affect findings unmuted by users.
Bulk mute findings
You can use the Security Command Center API to bulk mute existing findings based on filters you specify. If you also want to mute similar future findings, use the same filters to create mute rules.
Bulk mute filters don't support all finding properties. For a list of unsupported properties, see Unsupported finding properties for mute rules.
To bulk mute findings, perform the following steps, or run any of the code samples:
Console
In the Google Cloud console, you can only bulk mute findings by creating mute rules. In the Google Cloud console, creating mute rules silences existing and future findings.
gcloud
-
In the Google Cloud console, activate Cloud Shell.
At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.
To bulk mute findings, run the
gcloud scc findings bulk-mute
command:gcloud scc findings bulk-mute \ --RESOURCE=RESOURCE_ID \ --filter="FILTER"
Replace the following:
- RESOURCE: the parent resource for your mute rule
(
organization
,folder
, orproject
) - RESOURCE_ID: the numeric ID for the selected resource
FILTER: the expression you define to filter findings
For example, to mute all existing low-severity
OPEN_FIREWALL
andPUBLIC_IP_ADDRESS
findings in theinternal-test
project, your filter can be"category=\"OPEN_FIREWALL\" OR category=\"PUBLIC_IP_ADDRESS\" AND severity=\"LOW\" AND resource.project_display_name=\"internal-test\""
.
- RESOURCE: the parent resource for your mute rule
(
Go
Java
Python
REST API
In the API, use the bulkMute
method to execute the
following request. The request body contains the expression used to filter findings.
POST https://securitycenter.googleapis.com/v1/RESOURCE/RESOURCE_ID/findings:bulkMute -d { "filter": "FILTER" }
Replace the following:
- RESOURCE: the parent resource
(
organizations
,folders
, orprojects
) - RESOURCE_ID: the numeric ID for the selected resource
FILTER: the expression you define to filter findings
For example, to mute all existing low-severity
OPEN_FIREWALL
andPUBLIC_IP_ADDRESS
findings in theinternal-test
project, your filter can be"category=\"OPEN_FIREWALL\" OR category=\"PUBLIC_IP_ADDRESS\" AND severity=\"LOW\" AND resource.project_display_name=\"internal-test\""
.
All existing findings in the resource you select, and which exactly match the
filter, are hidden. The mute
attribute for the findings is set to MUTED
.
Muting findings doesn't change their state. If active findings are muted, they are hidden but remain active until the underlying vulnerabilities, misconfigurations, or threats are resolved.
Create mute rules
Mute rules are Security Command Center configurations that use filters you create to automatically mute future findings based on criteria you specify. New findings that match mute filters are automatically muted on an ongoing basis. If you also want to mute similar existing findings, use the same filters to bulk mute findings.
For more information on creating filters, see Filtering notifications.
Mute rules don't support all finding properties. For a list of properties that mute rules do not support, see Unsupported finding properties for mute rules.
Your organization can create a maximum of 1,000 mute rules.
To create a mute rule, perform the following steps, or run any of the code samples:
Console
In the Google Cloud console, go to the Security Command Center Findings page.
If necessary, select your Google Cloud project or organization.
Click Mute options, and then select Create mute rule.
Enter a Mute rule ID. This value is required.
Enter a Mute rule description that provides context for why findings are muted. This value is optional but recommended.
Parent resource indicates the scope at which the mute rule will be created and applied.
In the Findings query field, build your query statements by clicking Add filter. Alternatively, you can type in the query statements manually.
The Select filter dialog lets you choose supported finding attributes and values.
- Select a finding attribute or type its name in the Search finding attributes box. A list of the available sub-attributes displays.
- Select a sub-attribute. A selection field for your evaluation options displays above a list of the sub-attribute values found in the findings in the Findings query results panel.
- Select an evaluation option for the values of the selected sub-attribute. For more information about the evaluation options and the operators and functions that they use, see Query operators in the Add filters menu.
- Select Apply.
The dialog closes and your query is updated.
- Repeat until the findings query contains all the attributes you want.
Review the filter for accuracy. To make changes, delete or add properties and filter values as needed.
Click Preview matching findings.
A table displays findings that match your query.
Click Save.
gcloud
-
In the Google Cloud console, activate Cloud Shell.
At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.
To create mute rules, run the
gcloud scc muteconfigs create
command:gcloud scc muteconfigs create RULE_NAME \ --RESOURCE=RESOURCE_ID \ --description=RULE_DESCRIPTION \ --filter=FILTER
Replace the following:
- RULE_NAME: the name of the mute rule (between 1 and 63 characters)
- RESOURCE: the parent resource for your mute rule
(
organization
,folder
, orproject
) - RESOURCE_ID: the numeric ID for the selected resource
- RULE_DESCRIPTION: a description of the mute rule (max: 1,024 characters)
FILTER: the expression you define to filter findings
For example, to mute
OPEN_FIREWALL
findings, your filter can beFILTER="category=\"OPEN_FIREWALL\""
.
The response includes the mute config ID, which you can use to view, update, and delete mute rules, as described in Manage mute rules.
Go
Java
Python
REST API
In the API, use the muteConfigs create
method to execute the
following request. The request body is an instance of MuteConfig.
POST https://securitycenter.googleapis.com/v1/RESOURCE/RESOURCE_ID/muteConfigs?muteConfigId=MUTE_RULE_ID -d { "description": "RULE_DESCRIPTION", "filter": FILTER }
Replace the following:
- RESOURCE: the parent resource for your mute rule
(
organizations
,folders
, orprojects
) - RESOURCE_ID: the numeric ID for the selected resource
- MUTE_RULE_ID: the name of the mute rule (between 1 and 63 characters)
- RULE_DESCRIPTION: a description of the mute rule (max: 1,024 characters)
FILTER: the expression you define to filter findings
For example, to mute
OPEN_FIREWALL
findings, your filter can be"category=\"OPEN_FIREWALL\""
.
The response includes the mute config ID, which you can use to view, update, and delete mute rules, as described in Manage mute rules.
New findings that exactly match the filter are hidden, and the mute
attribute for the findings is set to MUTED
.
Unsupported finding properties for mute rules
Mute rules don't support all finding properties in filters. The following properties are not supported in mute rule filters.
createTime
eventTime
mute
mute_initiator
mute_update_time
name
parent
security_marks
source_properties
state
Mute finding properties
This section lists mute finding properties, and describes how they are impacted by mute operations:
mute
: set toUNDEFINED
when findings are created and changes in the following scenarios:MUTED
: a finding is muted manually or by a mute rule.UNMUTED
: a user unmutes a finding.
mute_update_time
: the time that a finding gets muted or unmutedmute_initiator
: the identifier for the principal or mute rule that muted a finding
Stop notifications for muted findings
If you enable finding notifications, muted findings that match your notification filters still trigger notifications in Pub/Sub.
To stop notifications for muted findings, use the mute
attribute to exclude
muted findings in your NotificationConfig
filter. For example, the following
filter only sends notifications for active findings that are not muted or where
the mute attribute hasn't been set:
FILTER="state=\"ACTIVE\" AND -mute=\"MUTED\""
Manage mute rules
You can view, update, and delete mute rules based on the scope of your IAM roles. With organization-level roles, you see mute rules for all folders and projects within the organization. If you have folder-level roles, you can access and manage mute rules for specific folders and all subfolders and projects within those folders. Project-level roles let you manage mute rules in specific projects.
Security Command Center Premium supports granting roles at the organization, folder, and project levels. Security Command Center Standard only supports granting roles at the organization level. For more information, see Access control.
List mute rules
To see a list of mute rules, for your organizations, folders, or projects—depending on the scope of your IAM roles—perform the following steps, or run any of the code samples:
Console
- In the Google Cloud console, go to the Mute rules tab in the Security Command Center Settings page.
- If necessary, select your Google Cloud project or organization.
- In the Mute rules section, you see details for active mute rules,
including the following:
- Name: mute rule ID
- Parent resource: the resource where the mute rule lives
- Description: the mute rule description, if available
- Last updated by: the principal who last updated the rule
- Last updated: the date and time the rule was last updated
gcloud
-
In the Google Cloud console, activate Cloud Shell.
At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.
To list mute rules, run the
gcloud scc muteconfigs list
command:gcloud scc muteconfigs list --RESOURCE=RESOURCE_ID
Replace the following:
- RESOURCE: the parent resource for your mute rule
(
organization
,folder
, orproject
) - RESOURCE_ID: the numeric ID for the selected resource
- RESOURCE: the parent resource for your mute rule
(
Go
Java
Python
REST API
In the API, use the muteConfigs list
method to make the
following request. The request body is empty.
GET https://securitycenter.googleapis.com/v1/RESOURCE/RESOURCE_ID/muteConfigs
Replace the following:
- RESOURCE: the parent resource for your mute rule
(
organizations
,folders
, orprojects
) - RESOURCE_ID: the numeric ID for the selected resource
The response includes the names, descriptions, and mute config IDs for your mute rules.
View mute rules
Console
- In the Google Cloud console, go to the Mute rules tab in the Security Command Center Settings page.
- If necessary, select your Google Cloud project or organization.
- In the Mute rules section, you see a list of mute rules.
Click the name of the rule you want to view.
A page opens with the mute rule's configuration.
gcloud
-
In the Google Cloud console, activate Cloud Shell.
At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.
To view mute rules, run the
gcloud scc muteconfigs get
command:gcloud scc muteconfigs get MUTE_CONFIG_ID \ --RESOURCE=RESOURCE_ID
Replace the following:
- MUTE_CONFIG_ID: the ID for the mute config
- RESOURCE: the parent resource for your mute rule
(
organization
,folder
, orproject
) - RESOURCE_ID: the numeric ID for the selected resource
Go
Java
Python
REST API
In the API, use the muteConfigs get
method to make the
following request. The request body is empty.
To get the CONFIG_ID
for mute rules, first execute an API call to List mute
rules.
The response includes config IDs for returned mute rules.
GET https://securitycenter.googleapis.com/v1/RESOURCE/RESOURCE_ID/muteConfigs/CONFIG_ID
Replace the following:
- RESOURCE: the parent resource for your mute rule
(
organizations
,folders
, orprojects
) - RESOURCE_ID: the numeric ID for the selected resource
- CONFIG_ID: the numeric ID of the mute rule
Update mute rules
You can update mute rules by changing their descriptions and filters. However, you can't change mute rule IDs or parent resources. To change a mute rule ID, you must create a new mute rule.
If you previously unmuted findings, they will be muted again if they are matched by a mute rule updated in the Google Cloud console. For more information, see Unmuted findings override mute rules.
To update a mute rule, perform the following steps, or run any of the code samples.
Console
In the Google Cloud console, go to the Mute rules tab in the Security Command Center Settings page.
Select the Google Cloud project or organization that is the parent resource for the mute rule you want to modify.
Click the name of the mute rule you want to modify.
If you didn't select the appropriate project or organization, you might see a note informing you that you don't have permission to modify the mute rule.
Enter a new description, and then click Save.
Update or change the filter.
For instructions, see Create mute rules.
To view findings that match the updated filter, click Preview Matching Findings.
A table loads with findings that match the new query.
Click Save.
gcloud
-
In the Google Cloud console, activate Cloud Shell.
At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.
To update mute rules, run the
gcloud scc muteconfigs update
command:gcloud scc muteconfigs update MUTE_CONFIG_ID \ --RESOURCE=RESOURCE_ID \ --description=RULE_DESCRIPTION \ --filter=FILTER
Replace the following:
- MUTE_CONFIG_ID: the ID for the mute config
- RESOURCE: the parent resource for your mute rule
(
organization
,folder
, orproject
) - RESOURCE_ID: the numeric ID for the selected resource
- RULE_DESCRIPTION: a description of the mute rule (max: 1,024 characters)
FILTER: the expression you define to filter findings
For example, to mute
OPEN_FIREWALL
findings, your filter could beFILTER="category=\"OPEN_FIREWALL\""
.
Go
Java
Python
REST API
In the API, use the muteConfigs patch
method to make the
following request. The request body is an instance of MuteConfig.
To get the CONFIG_ID
for mute rules, first execute an API call to list mute
rules.
The response includes config IDs for returned mute rules.
PATCH https://securitycenter.googleapis.com/v1/RESOURCE/RESOURCE_ID/muteConfigs/CONFIG_ID { "description": "RULE_DESCRIPTION", "filter": "FILTER", }
Replace the following:
- RESOURCE: the parent resource for your mute rule
(
organizations
,folders
, orprojects
) - RESOURCE_ID: the numeric ID for the selected resource
- CONFIG_ID: the numeric ID of the mute rule
- RULE_DESCRIPTION: a description of the mute rule (max: 1,024 characters)
FILTER: the expression you define to filter findings
For example, to mute
OPEN_FIREWALL
findings, your filter can be"category=\"OPEN_FIREWALL\""
.
New findings that exactly match the filter are hidden, and the mute
attribute
for the findings is set to MUTED
.
Updating mute rules doesn't automatically unmute any findings that were muted by previous rules. You must manually unmute findings.
Delete mute rules
Before deleting mute rules, understand the following:
- You can't recover deleted mute rules.
- Deleting mute rules doesn't automatically unmute any findings that are currently muted. You must manually or programmatically unmute findings.
- Future findings that match filters in deleted mute rules aren't muted.
To delete a mute rule, perform the following steps, or run any of the code samples:
Console
In the Google Cloud console, go to the Mute rules tab in the Security Command Center Settings page.
If necessary, select your Google Cloud project or organization.
Click the name of the mute rule you want to delete.
Click delete Delete.
Read the dialog and, if satisfied, click Delete.
gcloud
-
In the Google Cloud console, activate Cloud Shell.
At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.
To delete mute rules, run the
gcloud scc muteconfigs delete
command:gcloud scc muteconfigs delete MUTE_CONFIG_ID \ --RESOURCE=RESOURCE_ID
Replace the following:
- MUTE_CONFIG_ID: the ID for the mute config
- RESOURCE: the parent resource for your mute rule
(
organization
,folder
, orproject
) - RESOURCE_ID: the numeric ID for the selected resource
Confirm your request to delete the mute rule.
Go
Java
Python
REST API
In the API, use the muteConfigs delete
method to make the
following request. The request body is empty.
To get the CONFIG_ID
for mute rules, execute an API call to list mute
rules.
The response includes config IDs for returned mute rules.
DELETE https://securitycenter.googleapis.com/v1/RESOURCE/RESOURCE_ID/muteConfigs/CONFIG_ID
Replace the following:
- RESOURCE: the parent resource for your mute rule (
organizations
,folders
, orprojects
) - RESOURCE_ID: the numeric ID for the selected resource
- CONFIG_ID: the numeric ID of the mute rule
What's next
Learn more about filtering finding notifications.
Look through more examples of filters you can use.