A dynamic mute config, which is applied to existing and future matching
findings, setting their dynamic mute state to "muted". If the config is
updated or deleted, or a matching finding is updated, such that the
finding doesn't match the config, the config will be removed from the
finding, and the finding's dynamic mute state may become "unmuted"
(unless other configs still match).
Static
A static mute config, which sets the static mute state of future matching
findings to muted. Once the static mute state has been set, finding or
config modifications will not affect the state.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["The `MuteConfig.Types.MuteConfigType` enum in the Security Command Center v2 API defines the type of mute configurations used for findings."],["`Dynamic` mute configurations apply to existing and future matching findings, with their mute state potentially changing if the configuration or finding is modified."],["`Static` mute configurations set the mute state of future matching findings permanently, and this state remains unaffected by subsequent modifications."],["The `Unspecified` field is reserved for internal use and is not utilized in the context of mute configuration types."]]],[]]
