Mutes multiple remediation tracking process groups or, in the case of Kubernetes vulnerabilities, multiple remediation tracking Kubernetes nodes.
The request consumes an application/json
payload.
POST | SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/securityProblems/{id}/remediationItems/mute |
Environment ActiveGateCluster ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/v2/securityProblems/{id}/remediationItems/mute |
To execute this request, you need an access token with securityProblems.write
scope.
To learn how to obtain and use it, see Tokens and authentication.
The ID of the requested third-party security problem.
The JSON body of the request. Contains the muting information.
RemediationItemsBulkMute
objectInformation on muting several remediation items.
A comment about the muting reason.
The reason for muting the remediation items.
CONFIGURATION_NOT_AFFECTED
FALSE_POSITIVE
IGNORE
OTHER
VULNERABLE_CODE_NOT_IN_USE
The ids of the remediation items to be muted.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"comment": "string","reason": "CONFIGURATION_NOT_AFFECTED","remediationItemIds": ["string"]}
RemediationItemsBulkMuteResponse
objectResponse of muting several remediation items.
The summary of which remediation items were muted and which already were muted previously.
RemediationItemMutingSummary
objectSummary of (un-)muting a remediation item.
Whether a mute state change for the given remediation item was triggered by this request.
Contains a reason, in case the requested operation was not executed.
ALREADY_MUTED
ALREADY_UNMUTED
REMEDIATION_ITEM_NOT_AFFECTED_BY_GIVEN_SECURITY_PROBLEM
The id of the remediation item that will be (un-)muted.
{"summary": [{"muteStateChangeTriggered": true,"reason": "ALREADY_MUTED","remediationItemId": "string"}]}
Mute two remediation items, PROCESS_GROUP-46C0E12D9B0EF2D9
and PROCESS_GROUP-549E6AD75BD598EC
as the configuration isn't affected.
curl -X 'POST' 'https://mySampleEnv.live.dynatrace.com/api/v2/securityProblems/2919200225913269102/remediationItems/mute' \-H 'accept: application/json; charset=utf-8' \-H 'Authorization: Api-Token [your_token]' \-H 'Content-Type: application/json; charset=utf-8' \-d '{"comment": "Example muting multiple entities","reason": "CONFIGURATION_NOT_AFFECTED","remediationItemIds": ["PROCESS_GROUP-46C0E12D9B0EF2D9", "PROCESS_GROUP-549E6AD75BD598EC"]}'
https://mySampleEnv.live.dynatrace.com/api/v2/securityProblems/2919200225913269102/remediationItems/mute
{"comment": "Example muting multiple entities","reason": "CONFIGURATION_NOT_AFFECTED","remediationItemIds": ["PROCESS_GROUP-46C0E12D9B0EF2D9", "PROCESS_GROUP-549E6AD75BD598EC"]}
{"summary": [{"remediationItemId": "PROCESS_GROUP-549E6AD75BD598EC","muteStateChangeTriggered": true},{"remediationItemId": "PROCESS_GROUP-46C0E12D9B0EF2D9","muteStateChangeTriggered": true}]}
If the request was successful, you'll see muteStateChangeTriggered
per entity.