Mute
Mute Findings is a volume management feature in Security Command Center that lets you manually or programmatically hide irrelevant findings, and create filters to automatically silence existing and future findings based on criteria you specify. To get more information about MuteConfig, see:
Example Usage
Scc Mute Config
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.securitycenter.MuteConfig;
import com.pulumi.gcp.securitycenter.MuteConfigArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var default_ = new MuteConfig("default", MuteConfigArgs.builder()
.description("My Mute Config")
.filter("category: \"OS_VULNERABILITY\"")
.muteConfigId("my-config")
.parent("organizations/123456789")
.build());
}
}Import
MuteConfig can be imported using any of these accepted formats:
$ pulumi import gcp:securitycenter/muteConfig:MuteConfig default {{name}}Properties
The time at which the mute config was created. This field is set by the server and will be ignored if provided on config creation.
A description of the mute config.
An expression that defines the filter to apply across create/update events of findings. While creating a filter string, be mindful of the scope in which the mute configuration is being created. E.g., If a filter contains project = X but is created under the project = Y scope, it might not match any findings.
Email address of the user who last edited the mute config. This field is set by the server and will be ignored if provided on config creation or update.
Unique identifier provided by the client within the parent scope.
Output only. The most recent time at which the mute config was updated. This field is set by the server and will be ignored if provided on config creation or update.