builtin:appsec.code-level-vulnerability-rule-settings)
The global code-level vulnerability detection control defines the default per technology for all process groups. To override the default, define custom monitoring rules here. Note that monitoring rules are ordered; the first matching rule applies.
builtin:appsec.code-level-vulnerability-rule-settings
group:appsec.vulnerability-analytics
group:appsec
environment
GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:appsec.code-level-vulnerability-rule-settings |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:appsec.code-level-vulnerability-rule-settings | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:appsec.code-level-vulnerability-rule-settings |
To execute this request, you need an access token with Read settings (settings.read
) scope. To learn how to obtain and use it, see Tokens and authentication.
enabled
ruleName
vulnerabilityDetectionControl
resourceAttributeConditions
When you add multiple conditions, the rule applies if all conditions apply.
We provide suggestions for resource attribute keys and values based on what we currently see in your environment. You can also enter any value that isn't in the list. Key and value matches are case-sensitive. Resource attributes come out of the box from the OneAgent, and you can set them up from data enrichment.
VulnerabilityDetectionControl
objectmonitoringMode
MONITORING_OFF
MONITORING_ON
ResourceAttributeCondition
objectresourceAttributeKey
matcher
EQUALS
NOT_EQUALS
CONTAINS
DOES_NOT_CONTAIN
STARTS_WITH
DOES_NOT_START_WITH
ENDS_WITH
DOES_NOT_END_WITH
EXISTS
DOES_NOT_EXIST
resourceAttributeValue
Metadata
objectcomment