dynatrace.AppsecNotification
Explore with Pulumi AI
Create AppsecNotification Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new AppsecNotification(name: string, args: AppsecNotificationArgs, opts?: CustomResourceOptions);
@overload
def AppsecNotification(resource_name: str,
args: AppsecNotificationArgs,
opts: Optional[ResourceOptions] = None)
@overload
def AppsecNotification(resource_name: str,
opts: Optional[ResourceOptions] = None,
display_name: Optional[str] = None,
type: Optional[str] = None,
trigger: Optional[str] = None,
enabled: Optional[bool] = None,
attack_candidate_based_webhook_payload: Optional[AppsecNotificationAttackCandidateBasedWebhookPayloadArgs] = None,
email_configuration: Optional[AppsecNotificationEmailConfigurationArgs] = None,
attack_candidate_based_alerting_profile: Optional[str] = None,
jira_configuration: Optional[AppsecNotificationJiraConfigurationArgs] = None,
security_problem_based_alerting_profile: Optional[str] = None,
security_problem_based_email_payload: Optional[AppsecNotificationSecurityProblemBasedEmailPayloadArgs] = None,
security_problem_based_jira_payload: Optional[AppsecNotificationSecurityProblemBasedJiraPayloadArgs] = None,
security_problem_based_webhook_payload: Optional[AppsecNotificationSecurityProblemBasedWebhookPayloadArgs] = None,
attack_candidate_based_jira_payload: Optional[AppsecNotificationAttackCandidateBasedJiraPayloadArgs] = None,
attack_candidate_based_email_payload: Optional[AppsecNotificationAttackCandidateBasedEmailPayloadArgs] = None,
webhook_configuration: Optional[AppsecNotificationWebhookConfigurationArgs] = None)
func NewAppsecNotification(ctx *Context, name string, args AppsecNotificationArgs, opts ...ResourceOption) (*AppsecNotification, error)
public AppsecNotification(string name, AppsecNotificationArgs args, CustomResourceOptions? opts = null)
public AppsecNotification(String name, AppsecNotificationArgs args)
public AppsecNotification(String name, AppsecNotificationArgs args, CustomResourceOptions options)
type: dynatrace:AppsecNotification
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args AppsecNotificationArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args AppsecNotificationArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args AppsecNotificationArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args AppsecNotificationArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args AppsecNotificationArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var appsecNotificationResource = new Dynatrace.AppsecNotification("appsecNotificationResource", new()
{
DisplayName = "string",
Type = "string",
Trigger = "string",
Enabled = false,
AttackCandidateBasedWebhookPayload = new Dynatrace.Inputs.AppsecNotificationAttackCandidateBasedWebhookPayloadArgs
{
Payload = "string",
},
EmailConfiguration = new Dynatrace.Inputs.AppsecNotificationEmailConfigurationArgs
{
Recipients = new[]
{
"string",
},
BccRecipients = new[]
{
"string",
},
CcRecipients = new[]
{
"string",
},
},
AttackCandidateBasedAlertingProfile = "string",
JiraConfiguration = new Dynatrace.Inputs.AppsecNotificationJiraConfigurationArgs
{
ApiToken = "string",
IssueType = "string",
ProjectKey = "string",
Url = "string",
Username = "string",
},
SecurityProblemBasedAlertingProfile = "string",
SecurityProblemBasedEmailPayload = new Dynatrace.Inputs.AppsecNotificationSecurityProblemBasedEmailPayloadArgs
{
Body = "string",
Subject = "string",
},
SecurityProblemBasedJiraPayload = new Dynatrace.Inputs.AppsecNotificationSecurityProblemBasedJiraPayloadArgs
{
Description = "string",
Summary = "string",
},
SecurityProblemBasedWebhookPayload = new Dynatrace.Inputs.AppsecNotificationSecurityProblemBasedWebhookPayloadArgs
{
Payload = "string",
},
AttackCandidateBasedJiraPayload = new Dynatrace.Inputs.AppsecNotificationAttackCandidateBasedJiraPayloadArgs
{
Description = "string",
Summary = "string",
},
AttackCandidateBasedEmailPayload = new Dynatrace.Inputs.AppsecNotificationAttackCandidateBasedEmailPayloadArgs
{
Body = "string",
Subject = "string",
},
WebhookConfiguration = new Dynatrace.Inputs.AppsecNotificationWebhookConfigurationArgs
{
AcceptAnyCertificate = false,
Url = "string",
Headers = new Dynatrace.Inputs.AppsecNotificationWebhookConfigurationHeadersArgs
{
Headers = new[]
{
new Dynatrace.Inputs.AppsecNotificationWebhookConfigurationHeadersHeaderArgs
{
Name = "string",
Secret = false,
SecretValue = "string",
Value = "string",
},
},
},
},
});
example, err := dynatrace.NewAppsecNotification(ctx, "appsecNotificationResource", &dynatrace.AppsecNotificationArgs{
DisplayName: pulumi.String("string"),
Type: pulumi.String("string"),
Trigger: pulumi.String("string"),
Enabled: pulumi.Bool(false),
AttackCandidateBasedWebhookPayload: &dynatrace.AppsecNotificationAttackCandidateBasedWebhookPayloadArgs{
Payload: pulumi.String("string"),
},
EmailConfiguration: &dynatrace.AppsecNotificationEmailConfigurationArgs{
Recipients: pulumi.StringArray{
pulumi.String("string"),
},
BccRecipients: pulumi.StringArray{
pulumi.String("string"),
},
CcRecipients: pulumi.StringArray{
pulumi.String("string"),
},
},
AttackCandidateBasedAlertingProfile: pulumi.String("string"),
JiraConfiguration: &dynatrace.AppsecNotificationJiraConfigurationArgs{
ApiToken: pulumi.String("string"),
IssueType: pulumi.String("string"),
ProjectKey: pulumi.String("string"),
Url: pulumi.String("string"),
Username: pulumi.String("string"),
},
SecurityProblemBasedAlertingProfile: pulumi.String("string"),
SecurityProblemBasedEmailPayload: &dynatrace.AppsecNotificationSecurityProblemBasedEmailPayloadArgs{
Body: pulumi.String("string"),
Subject: pulumi.String("string"),
},
SecurityProblemBasedJiraPayload: &dynatrace.AppsecNotificationSecurityProblemBasedJiraPayloadArgs{
Description: pulumi.String("string"),
Summary: pulumi.String("string"),
},
SecurityProblemBasedWebhookPayload: &dynatrace.AppsecNotificationSecurityProblemBasedWebhookPayloadArgs{
Payload: pulumi.String("string"),
},
AttackCandidateBasedJiraPayload: &dynatrace.AppsecNotificationAttackCandidateBasedJiraPayloadArgs{
Description: pulumi.String("string"),
Summary: pulumi.String("string"),
},
AttackCandidateBasedEmailPayload: &dynatrace.AppsecNotificationAttackCandidateBasedEmailPayloadArgs{
Body: pulumi.String("string"),
Subject: pulumi.String("string"),
},
WebhookConfiguration: &dynatrace.AppsecNotificationWebhookConfigurationArgs{
AcceptAnyCertificate: pulumi.Bool(false),
Url: pulumi.String("string"),
Headers: &dynatrace.AppsecNotificationWebhookConfigurationHeadersArgs{
Headers: dynatrace.AppsecNotificationWebhookConfigurationHeadersHeaderArray{
&dynatrace.AppsecNotificationWebhookConfigurationHeadersHeaderArgs{
Name: pulumi.String("string"),
Secret: pulumi.Bool(false),
SecretValue: pulumi.String("string"),
Value: pulumi.String("string"),
},
},
},
},
})
var appsecNotificationResource = new AppsecNotification("appsecNotificationResource", AppsecNotificationArgs.builder()
.displayName("string")
.type("string")
.trigger("string")
.enabled(false)
.attackCandidateBasedWebhookPayload(AppsecNotificationAttackCandidateBasedWebhookPayloadArgs.builder()
.payload("string")
.build())
.emailConfiguration(AppsecNotificationEmailConfigurationArgs.builder()
.recipients("string")
.bccRecipients("string")
.ccRecipients("string")
.build())
.attackCandidateBasedAlertingProfile("string")
.jiraConfiguration(AppsecNotificationJiraConfigurationArgs.builder()
.apiToken("string")
.issueType("string")
.projectKey("string")
.url("string")
.username("string")
.build())
.securityProblemBasedAlertingProfile("string")
.securityProblemBasedEmailPayload(AppsecNotificationSecurityProblemBasedEmailPayloadArgs.builder()
.body("string")
.subject("string")
.build())
.securityProblemBasedJiraPayload(AppsecNotificationSecurityProblemBasedJiraPayloadArgs.builder()
.description("string")
.summary("string")
.build())
.securityProblemBasedWebhookPayload(AppsecNotificationSecurityProblemBasedWebhookPayloadArgs.builder()
.payload("string")
.build())
.attackCandidateBasedJiraPayload(AppsecNotificationAttackCandidateBasedJiraPayloadArgs.builder()
.description("string")
.summary("string")
.build())
.attackCandidateBasedEmailPayload(AppsecNotificationAttackCandidateBasedEmailPayloadArgs.builder()
.body("string")
.subject("string")
.build())
.webhookConfiguration(AppsecNotificationWebhookConfigurationArgs.builder()
.acceptAnyCertificate(false)
.url("string")
.headers(AppsecNotificationWebhookConfigurationHeadersArgs.builder()
.headers(AppsecNotificationWebhookConfigurationHeadersHeaderArgs.builder()
.name("string")
.secret(false)
.secretValue("string")
.value("string")
.build())
.build())
.build())
.build());
appsec_notification_resource = dynatrace.AppsecNotification("appsecNotificationResource",
display_name="string",
type="string",
trigger="string",
enabled=False,
attack_candidate_based_webhook_payload={
"payload": "string",
},
email_configuration={
"recipients": ["string"],
"bcc_recipients": ["string"],
"cc_recipients": ["string"],
},
attack_candidate_based_alerting_profile="string",
jira_configuration={
"api_token": "string",
"issue_type": "string",
"project_key": "string",
"url": "string",
"username": "string",
},
security_problem_based_alerting_profile="string",
security_problem_based_email_payload={
"body": "string",
"subject": "string",
},
security_problem_based_jira_payload={
"description": "string",
"summary": "string",
},
security_problem_based_webhook_payload={
"payload": "string",
},
attack_candidate_based_jira_payload={
"description": "string",
"summary": "string",
},
attack_candidate_based_email_payload={
"body": "string",
"subject": "string",
},
webhook_configuration={
"accept_any_certificate": False,
"url": "string",
"headers": {
"headers": [{
"name": "string",
"secret": False,
"secret_value": "string",
"value": "string",
}],
},
})
const appsecNotificationResource = new dynatrace.AppsecNotification("appsecNotificationResource", {
displayName: "string",
type: "string",
trigger: "string",
enabled: false,
attackCandidateBasedWebhookPayload: {
payload: "string",
},
emailConfiguration: {
recipients: ["string"],
bccRecipients: ["string"],
ccRecipients: ["string"],
},
attackCandidateBasedAlertingProfile: "string",
jiraConfiguration: {
apiToken: "string",
issueType: "string",
projectKey: "string",
url: "string",
username: "string",
},
securityProblemBasedAlertingProfile: "string",
securityProblemBasedEmailPayload: {
body: "string",
subject: "string",
},
securityProblemBasedJiraPayload: {
description: "string",
summary: "string",
},
securityProblemBasedWebhookPayload: {
payload: "string",
},
attackCandidateBasedJiraPayload: {
description: "string",
summary: "string",
},
attackCandidateBasedEmailPayload: {
body: "string",
subject: "string",
},
webhookConfiguration: {
acceptAnyCertificate: false,
url: "string",
headers: {
headers: [{
name: "string",
secret: false,
secretValue: "string",
value: "string",
}],
},
},
});
type: dynatrace:AppsecNotification
properties:
attackCandidateBasedAlertingProfile: string
attackCandidateBasedEmailPayload:
body: string
subject: string
attackCandidateBasedJiraPayload:
description: string
summary: string
attackCandidateBasedWebhookPayload:
payload: string
displayName: string
emailConfiguration:
bccRecipients:
- string
ccRecipients:
- string
recipients:
- string
enabled: false
jiraConfiguration:
apiToken: string
issueType: string
projectKey: string
url: string
username: string
securityProblemBasedAlertingProfile: string
securityProblemBasedEmailPayload:
body: string
subject: string
securityProblemBasedJiraPayload:
description: string
summary: string
securityProblemBasedWebhookPayload:
payload: string
trigger: string
type: string
webhookConfiguration:
acceptAnyCertificate: false
headers:
headers:
- name: string
secret: false
secretValue: string
value: string
url: string
AppsecNotification Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The AppsecNotification resource accepts the following input properties:
- Display
Name string - Display name of the security notification
- Enabled bool
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - Trigger string
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- Type string
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- Attack
Candidate stringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- Attack
Candidate Pulumiverse.Based Email Payload Dynatrace. Inputs. Appsec Notification Attack Candidate Based Email Payload - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- Attack
Candidate Pulumiverse.Based Jira Payload Dynatrace. Inputs. Appsec Notification Attack Candidate Based Jira Payload - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- Attack
Candidate Pulumiverse.Based Webhook Payload Dynatrace. Inputs. Appsec Notification Attack Candidate Based Webhook Payload - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- Email
Configuration Pulumiverse.Dynatrace. Inputs. Appsec Notification Email Configuration - Email configuration, required when
type
equalsEMAIL
- Jira
Configuration Pulumiverse.Dynatrace. Inputs. Appsec Notification Jira Configuration - Jira configuration, required when
type
equalsJIRA
- Security
Problem stringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- Security
Problem Pulumiverse.Based Email Payload Dynatrace. Inputs. Appsec Notification Security Problem Based Email Payload - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- Security
Problem Pulumiverse.Based Jira Payload Dynatrace. Inputs. Appsec Notification Security Problem Based Jira Payload - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- Security
Problem Pulumiverse.Based Webhook Payload Dynatrace. Inputs. Appsec Notification Security Problem Based Webhook Payload - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- Webhook
Configuration Pulumiverse.Dynatrace. Inputs. Appsec Notification Webhook Configuration - Webhook configuration, required when
type
equalsWEBHOOK
- Display
Name string - Display name of the security notification
- Enabled bool
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - Trigger string
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- Type string
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- Attack
Candidate stringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- Attack
Candidate AppsecBased Email Payload Notification Attack Candidate Based Email Payload Args - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- Attack
Candidate AppsecBased Jira Payload Notification Attack Candidate Based Jira Payload Args - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- Attack
Candidate AppsecBased Webhook Payload Notification Attack Candidate Based Webhook Payload Args - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- Email
Configuration AppsecNotification Email Configuration Args - Email configuration, required when
type
equalsEMAIL
- Jira
Configuration AppsecNotification Jira Configuration Args - Jira configuration, required when
type
equalsJIRA
- Security
Problem stringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- Security
Problem AppsecBased Email Payload Notification Security Problem Based Email Payload Args - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- Security
Problem AppsecBased Jira Payload Notification Security Problem Based Jira Payload Args - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- Security
Problem AppsecBased Webhook Payload Notification Security Problem Based Webhook Payload Args - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- Webhook
Configuration AppsecNotification Webhook Configuration Args - Webhook configuration, required when
type
equalsWEBHOOK
- display
Name String - Display name of the security notification
- enabled Boolean
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - trigger String
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- type String
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- attack
Candidate StringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- attack
Candidate AppsecBased Email Payload Notification Attack Candidate Based Email Payload - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- attack
Candidate AppsecBased Jira Payload Notification Attack Candidate Based Jira Payload - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- attack
Candidate AppsecBased Webhook Payload Notification Attack Candidate Based Webhook Payload - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- email
Configuration AppsecNotification Email Configuration - Email configuration, required when
type
equalsEMAIL
- jira
Configuration AppsecNotification Jira Configuration - Jira configuration, required when
type
equalsJIRA
- security
Problem StringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- security
Problem AppsecBased Email Payload Notification Security Problem Based Email Payload - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- security
Problem AppsecBased Jira Payload Notification Security Problem Based Jira Payload - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- security
Problem AppsecBased Webhook Payload Notification Security Problem Based Webhook Payload - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- webhook
Configuration AppsecNotification Webhook Configuration - Webhook configuration, required when
type
equalsWEBHOOK
- display
Name string - Display name of the security notification
- enabled boolean
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - trigger string
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- type string
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- attack
Candidate stringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- attack
Candidate AppsecBased Email Payload Notification Attack Candidate Based Email Payload - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- attack
Candidate AppsecBased Jira Payload Notification Attack Candidate Based Jira Payload - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- attack
Candidate AppsecBased Webhook Payload Notification Attack Candidate Based Webhook Payload - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- email
Configuration AppsecNotification Email Configuration - Email configuration, required when
type
equalsEMAIL
- jira
Configuration AppsecNotification Jira Configuration - Jira configuration, required when
type
equalsJIRA
- security
Problem stringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- security
Problem AppsecBased Email Payload Notification Security Problem Based Email Payload - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- security
Problem AppsecBased Jira Payload Notification Security Problem Based Jira Payload - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- security
Problem AppsecBased Webhook Payload Notification Security Problem Based Webhook Payload - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- webhook
Configuration AppsecNotification Webhook Configuration - Webhook configuration, required when
type
equalsWEBHOOK
- display_
name str - Display name of the security notification
- enabled bool
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - trigger str
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- type str
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- attack_
candidate_ strbased_ alerting_ profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- attack_
candidate_ Appsecbased_ email_ payload Notification Attack Candidate Based Email Payload Args - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- attack_
candidate_ Appsecbased_ jira_ payload Notification Attack Candidate Based Jira Payload Args - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- attack_
candidate_ Appsecbased_ webhook_ payload Notification Attack Candidate Based Webhook Payload Args - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- email_
configuration AppsecNotification Email Configuration Args - Email configuration, required when
type
equalsEMAIL
- jira_
configuration AppsecNotification Jira Configuration Args - Jira configuration, required when
type
equalsJIRA
- security_
problem_ strbased_ alerting_ profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- security_
problem_ Appsecbased_ email_ payload Notification Security Problem Based Email Payload Args - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- security_
problem_ Appsecbased_ jira_ payload Notification Security Problem Based Jira Payload Args - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- security_
problem_ Appsecbased_ webhook_ payload Notification Security Problem Based Webhook Payload Args - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- webhook_
configuration AppsecNotification Webhook Configuration Args - Webhook configuration, required when
type
equalsWEBHOOK
- display
Name String - Display name of the security notification
- enabled Boolean
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - trigger String
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- type String
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- attack
Candidate StringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- attack
Candidate Property MapBased Email Payload - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- attack
Candidate Property MapBased Jira Payload - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- attack
Candidate Property MapBased Webhook Payload - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- email
Configuration Property Map - Email configuration, required when
type
equalsEMAIL
- jira
Configuration Property Map - Jira configuration, required when
type
equalsJIRA
- security
Problem StringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- security
Problem Property MapBased Email Payload - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- security
Problem Property MapBased Jira Payload - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- security
Problem Property MapBased Webhook Payload - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- webhook
Configuration Property Map - Webhook configuration, required when
type
equalsWEBHOOK
Outputs
All input properties are implicitly available as output properties. Additionally, the AppsecNotification resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
- id string
- The provider-assigned unique ID for this managed resource.
- id str
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
Look up Existing AppsecNotification Resource
Get an existing AppsecNotification resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: AppsecNotificationState, opts?: CustomResourceOptions): AppsecNotification
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
attack_candidate_based_alerting_profile: Optional[str] = None,
attack_candidate_based_email_payload: Optional[AppsecNotificationAttackCandidateBasedEmailPayloadArgs] = None,
attack_candidate_based_jira_payload: Optional[AppsecNotificationAttackCandidateBasedJiraPayloadArgs] = None,
attack_candidate_based_webhook_payload: Optional[AppsecNotificationAttackCandidateBasedWebhookPayloadArgs] = None,
display_name: Optional[str] = None,
email_configuration: Optional[AppsecNotificationEmailConfigurationArgs] = None,
enabled: Optional[bool] = None,
jira_configuration: Optional[AppsecNotificationJiraConfigurationArgs] = None,
security_problem_based_alerting_profile: Optional[str] = None,
security_problem_based_email_payload: Optional[AppsecNotificationSecurityProblemBasedEmailPayloadArgs] = None,
security_problem_based_jira_payload: Optional[AppsecNotificationSecurityProblemBasedJiraPayloadArgs] = None,
security_problem_based_webhook_payload: Optional[AppsecNotificationSecurityProblemBasedWebhookPayloadArgs] = None,
trigger: Optional[str] = None,
type: Optional[str] = None,
webhook_configuration: Optional[AppsecNotificationWebhookConfigurationArgs] = None) -> AppsecNotification
func GetAppsecNotification(ctx *Context, name string, id IDInput, state *AppsecNotificationState, opts ...ResourceOption) (*AppsecNotification, error)
public static AppsecNotification Get(string name, Input<string> id, AppsecNotificationState? state, CustomResourceOptions? opts = null)
public static AppsecNotification get(String name, Output<String> id, AppsecNotificationState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Attack
Candidate stringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- Attack
Candidate Pulumiverse.Based Email Payload Dynatrace. Inputs. Appsec Notification Attack Candidate Based Email Payload - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- Attack
Candidate Pulumiverse.Based Jira Payload Dynatrace. Inputs. Appsec Notification Attack Candidate Based Jira Payload - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- Attack
Candidate Pulumiverse.Based Webhook Payload Dynatrace. Inputs. Appsec Notification Attack Candidate Based Webhook Payload - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- Display
Name string - Display name of the security notification
- Email
Configuration Pulumiverse.Dynatrace. Inputs. Appsec Notification Email Configuration - Email configuration, required when
type
equalsEMAIL
- Enabled bool
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - Jira
Configuration Pulumiverse.Dynatrace. Inputs. Appsec Notification Jira Configuration - Jira configuration, required when
type
equalsJIRA
- Security
Problem stringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- Security
Problem Pulumiverse.Based Email Payload Dynatrace. Inputs. Appsec Notification Security Problem Based Email Payload - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- Security
Problem Pulumiverse.Based Jira Payload Dynatrace. Inputs. Appsec Notification Security Problem Based Jira Payload - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- Security
Problem Pulumiverse.Based Webhook Payload Dynatrace. Inputs. Appsec Notification Security Problem Based Webhook Payload - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- Trigger string
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- Type string
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- Webhook
Configuration Pulumiverse.Dynatrace. Inputs. Appsec Notification Webhook Configuration - Webhook configuration, required when
type
equalsWEBHOOK
- Attack
Candidate stringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- Attack
Candidate AppsecBased Email Payload Notification Attack Candidate Based Email Payload Args - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- Attack
Candidate AppsecBased Jira Payload Notification Attack Candidate Based Jira Payload Args - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- Attack
Candidate AppsecBased Webhook Payload Notification Attack Candidate Based Webhook Payload Args - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- Display
Name string - Display name of the security notification
- Email
Configuration AppsecNotification Email Configuration Args - Email configuration, required when
type
equalsEMAIL
- Enabled bool
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - Jira
Configuration AppsecNotification Jira Configuration Args - Jira configuration, required when
type
equalsJIRA
- Security
Problem stringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- Security
Problem AppsecBased Email Payload Notification Security Problem Based Email Payload Args - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- Security
Problem AppsecBased Jira Payload Notification Security Problem Based Jira Payload Args - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- Security
Problem AppsecBased Webhook Payload Notification Security Problem Based Webhook Payload Args - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- Trigger string
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- Type string
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- Webhook
Configuration AppsecNotification Webhook Configuration Args - Webhook configuration, required when
type
equalsWEBHOOK
- attack
Candidate StringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- attack
Candidate AppsecBased Email Payload Notification Attack Candidate Based Email Payload - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- attack
Candidate AppsecBased Jira Payload Notification Attack Candidate Based Jira Payload - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- attack
Candidate AppsecBased Webhook Payload Notification Attack Candidate Based Webhook Payload - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- display
Name String - Display name of the security notification
- email
Configuration AppsecNotification Email Configuration - Email configuration, required when
type
equalsEMAIL
- enabled Boolean
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - jira
Configuration AppsecNotification Jira Configuration - Jira configuration, required when
type
equalsJIRA
- security
Problem StringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- security
Problem AppsecBased Email Payload Notification Security Problem Based Email Payload - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- security
Problem AppsecBased Jira Payload Notification Security Problem Based Jira Payload - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- security
Problem AppsecBased Webhook Payload Notification Security Problem Based Webhook Payload - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- trigger String
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- type String
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- webhook
Configuration AppsecNotification Webhook Configuration - Webhook configuration, required when
type
equalsWEBHOOK
- attack
Candidate stringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- attack
Candidate AppsecBased Email Payload Notification Attack Candidate Based Email Payload - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- attack
Candidate AppsecBased Jira Payload Notification Attack Candidate Based Jira Payload - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- attack
Candidate AppsecBased Webhook Payload Notification Attack Candidate Based Webhook Payload - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- display
Name string - Display name of the security notification
- email
Configuration AppsecNotification Email Configuration - Email configuration, required when
type
equalsEMAIL
- enabled boolean
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - jira
Configuration AppsecNotification Jira Configuration - Jira configuration, required when
type
equalsJIRA
- security
Problem stringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- security
Problem AppsecBased Email Payload Notification Security Problem Based Email Payload - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- security
Problem AppsecBased Jira Payload Notification Security Problem Based Jira Payload - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- security
Problem AppsecBased Webhook Payload Notification Security Problem Based Webhook Payload - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- trigger string
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- type string
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- webhook
Configuration AppsecNotification Webhook Configuration - Webhook configuration, required when
type
equalsWEBHOOK
- attack_
candidate_ strbased_ alerting_ profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- attack_
candidate_ Appsecbased_ email_ payload Notification Attack Candidate Based Email Payload Args - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- attack_
candidate_ Appsecbased_ jira_ payload Notification Attack Candidate Based Jira Payload Args - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- attack_
candidate_ Appsecbased_ webhook_ payload Notification Attack Candidate Based Webhook Payload Args - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- display_
name str - Display name of the security notification
- email_
configuration AppsecNotification Email Configuration Args - Email configuration, required when
type
equalsEMAIL
- enabled bool
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - jira_
configuration AppsecNotification Jira Configuration Args - Jira configuration, required when
type
equalsJIRA
- security_
problem_ strbased_ alerting_ profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- security_
problem_ Appsecbased_ email_ payload Notification Security Problem Based Email Payload Args - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- security_
problem_ Appsecbased_ jira_ payload Notification Security Problem Based Jira Payload Args - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- security_
problem_ Appsecbased_ webhook_ payload Notification Security Problem Based Webhook Payload Args - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- trigger str
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- type str
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- webhook_
configuration AppsecNotification Webhook Configuration Args - Webhook configuration, required when
type
equalsWEBHOOK
- attack
Candidate StringBased Alerting Profile - For attack candidate alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- attack
Candidate Property MapBased Email Payload - Attack candidate based email payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsEMAIL
- attack
Candidate Property MapBased Jira Payload - Attack candidate based Jira payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsJIRA
- attack
Candidate Property MapBased Webhook Payload - Attack candidate based webhook payload, required when
trigger
equalsATTACK_CANDIDATE
andtype
equalsWEBHOOK
- display
Name String - Display name of the security notification
- email
Configuration Property Map - Email configuration, required when
type
equalsEMAIL
- enabled Boolean
- Enable/Disable the security notification, enabled (
true
) or disabled (false
) - jira
Configuration Property Map - Jira configuration, required when
type
equalsJIRA
- security
Problem StringBased Alerting Profile - For security problem alerts, select an alerting profile to control the delivery of security notifications related to this integration.
- security
Problem Property MapBased Email Payload - Security problem based email payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsEMAIL
- security
Problem Property MapBased Jira Payload - Security problem based Jira payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsJIRA
- security
Problem Property MapBased Webhook Payload - Security problem based webhook payload, required when
trigger
equalsSECURITY_PROBLEM
andtype
equalsWEBHOOK
- trigger String
- Security alert type, possible Values:
ATTACK_CANDIDATE
,SECURITY_PROBLEM
- type String
- Notification type, possible Values:
EMAIL
,JIRA
,WEBHOOK
- webhook
Configuration Property Map - Webhook configuration, required when
type
equalsWEBHOOK
Supporting Types
AppsecNotificationAttackCandidateBasedEmailPayload, AppsecNotificationAttackCandidateBasedEmailPayloadArgs
- Body string
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the body might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- Subject string
- The subject of the email notifications.. Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- Body string
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the body might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- Subject string
- The subject of the email notifications.. Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- body String
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the body might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- subject String
- The subject of the email notifications.. Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- body string
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the body might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- subject string
- The subject of the email notifications.. Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- body str
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the body might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- subject str
- The subject of the email notifications.. Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- body String
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the body might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- subject String
- The subject of the email notifications.. Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
AppsecNotificationAttackCandidateBasedJiraPayload, AppsecNotificationAttackCandidateBasedJiraPayloadArgs
- Description string
The description of the Jira issue to be created by this notification.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- Summary string
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- Description string
The description of the Jira issue to be created by this notification.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- Summary string
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- description String
The description of the Jira issue to be created by this notification.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- summary String
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- description string
The description of the Jira issue to be created by this notification.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- summary string
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- description str
The description of the Jira issue to be created by this notification.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- summary str
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- description String
The description of the Jira issue to be created by this notification.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.- summary String
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example, "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
AppsecNotificationAttackCandidateBasedWebhookPayload, AppsecNotificationAttackCandidateBasedWebhookPayloadArgs
- Payload string
This is the content your notification message will include when users view it.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- Payload string
This is the content your notification message will include when users view it.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- payload String
This is the content your notification message will include when users view it.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- payload string
This is the content your notification message will include when users view it.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- payload str
This is the content your notification message will include when users view it.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
- payload String
This is the content your notification message will include when users view it.
In case a value of an attack is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{AttackDisplayId}: The unique identifier assigned by Dynatrace, for example: "A-1234".
{Title}: Location of the attack, for example: "com.dynatrace.Class.method():120"
{Type}: The type of attack, for example: "SQL Injection".
{AttackUrl}: URL of the attack in Dynatrace.
{ProcessGroupId}: Details about the process group attacked.
{EntryPoint}: The entry point of the attack into the process, for example: "/login". Can be empty.
{Status}: The status of the attack, for example: "Exploited"
{Timestamp}: When the attack happened.
{VulnerabilityName}: Name of the associated code-level vulnerability, for example: "InMemoryDatabaseCaller.getAccountInfo():51". Can be empty.
AppsecNotificationEmailConfiguration, AppsecNotificationEmailConfigurationArgs
- Recipients List<string>
- To
- Bcc
Recipients List<string> - BCC
- Cc
Recipients List<string> - CC
- Recipients []string
- To
- Bcc
Recipients []string - BCC
- Cc
Recipients []string - CC
- recipients List<String>
- To
- bcc
Recipients List<String> - BCC
- cc
Recipients List<String> - CC
- recipients string[]
- To
- bcc
Recipients string[] - BCC
- cc
Recipients string[] - CC
- recipients Sequence[str]
- To
- bcc_
recipients Sequence[str] - BCC
- cc_
recipients Sequence[str] - CC
- recipients List<String>
- To
- bcc
Recipients List<String> - BCC
- cc
Recipients List<String> - CC
AppsecNotificationJiraConfiguration, AppsecNotificationJiraConfigurationArgs
- Api
Token string - The API token for the Jira profile. Using password authentication was deprecated by Jira
- Issue
Type string The type of the Jira issue to be created by this notification.
To find all available issue types or create your own, in Jira, go to Project settings > Issue types.
- Project
Key string - The project key of the Jira issue to be created by this notification.
- Url string
- The URL of the Jira API endpoint.
- Username string
- The username of the Jira profile.
- Api
Token string - The API token for the Jira profile. Using password authentication was deprecated by Jira
- Issue
Type string The type of the Jira issue to be created by this notification.
To find all available issue types or create your own, in Jira, go to Project settings > Issue types.
- Project
Key string - The project key of the Jira issue to be created by this notification.
- Url string
- The URL of the Jira API endpoint.
- Username string
- The username of the Jira profile.
- api
Token String - The API token for the Jira profile. Using password authentication was deprecated by Jira
- issue
Type String The type of the Jira issue to be created by this notification.
To find all available issue types or create your own, in Jira, go to Project settings > Issue types.
- project
Key String - The project key of the Jira issue to be created by this notification.
- url String
- The URL of the Jira API endpoint.
- username String
- The username of the Jira profile.
- api
Token string - The API token for the Jira profile. Using password authentication was deprecated by Jira
- issue
Type string The type of the Jira issue to be created by this notification.
To find all available issue types or create your own, in Jira, go to Project settings > Issue types.
- project
Key string - The project key of the Jira issue to be created by this notification.
- url string
- The URL of the Jira API endpoint.
- username string
- The username of the Jira profile.
- api_
token str - The API token for the Jira profile. Using password authentication was deprecated by Jira
- issue_
type str The type of the Jira issue to be created by this notification.
To find all available issue types or create your own, in Jira, go to Project settings > Issue types.
- project_
key str - The project key of the Jira issue to be created by this notification.
- url str
- The URL of the Jira API endpoint.
- username str
- The username of the Jira profile.
- api
Token String - The API token for the Jira profile. Using password authentication was deprecated by Jira
- issue
Type String The type of the Jira issue to be created by this notification.
To find all available issue types or create your own, in Jira, go to Project settings > Issue types.
- project
Key String - The project key of the Jira issue to be created by this notification.
- url String
- The URL of the Jira API endpoint.
- username String
- The username of the Jira profile.
AppsecNotificationSecurityProblemBasedEmailPayload, AppsecNotificationSecurityProblemBasedEmailPayloadArgs
- Body string
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- Subject string
- The subject of the email notifications.. Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- Body string
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- Subject string
- The subject of the email notifications.. Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- body String
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- subject String
- The subject of the email notifications.. Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- body string
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- subject string
- The subject of the email notifications.. Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- body str
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- subject str
- The subject of the email notifications.. Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- body String
The template of the email notifications.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- subject String
- The subject of the email notifications.. Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
AppsecNotificationSecurityProblemBasedJiraPayload, AppsecNotificationSecurityProblemBasedJiraPayloadArgs
- Description string
The description of the Jira issue to be created by this notification.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- Summary string
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- Description string
The description of the Jira issue to be created by this notification.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- Summary string
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- description String
The description of the Jira issue to be created by this notification.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- summary String
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- description string
The description of the Jira issue to be created by this notification.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- summary string
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- description str
The description of the Jira issue to be created by this notification.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- summary str
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- description String
The description of the Jira issue to be created by this notification.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the description might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".- summary String
The summary of the Jira issue to be created by this notification.. Note: The Jira summary field must contain less than 255 characters. Any content exceeding this limit after evaluating the placeholders will be discarded.
Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
AppsecNotificationSecurityProblemBasedWebhookPayload, AppsecNotificationSecurityProblemBasedWebhookPayloadArgs
- Payload string
This is the content your notification message will include when users view it.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- Payload string
This is the content your notification message will include when users view it.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- payload String
This is the content your notification message will include when users view it.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- payload string
This is the content your notification message will include when users view it.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- payload str
This is the content your notification message will include when users view it.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
- payload String
This is the content your notification message will include when users view it.
In case a value of a security problem is not set, the placeholder will be replaced by an empty string.. Note: Security notifications contain sensitive information. Excessive usage of placeholders in the custom payload might leak information to untrusted parties.Available placeholders:
{SecurityProblemId}: The unique identifier assigned by Dynatrace, for example, "S-1234".
{Title}: A short summary of the type of vulnerability that was found, for example, "Remote Code Execution".
{Description}: A more detailed description of the vulnerability.
{CvssScore}: CVSS score of the identified vulnerability, for example, "10.0". Can be empty. {DavisSecurityScore}: Davis Security Score is an enhanced risk-calculation score based on the CVSS, for example, "10.0".
{Severity}: The security problem severity, for example, "Critical" or "Medium".
{SecurityProblemUrl}: URL of the security problem in Dynatrace.
{AffectedEntities}: Details about the entities affected by the security problem in a json array.
{ManagementZones}: Comma-separated list of all management zones affected by the vulnerability at the time of detection.
{Tags}: Comma-separated list of tags that are defined for a vulnerability's affected entities. For example: "PROD, owner:John". Assign the tag's key in square brackets: {Tags[key]} to get all associated values. For example: "{Tags[owner]}" will be resolved as "John". Tags without an assigned value will be resolved as empty string.
{Exposed}: Describes whether one or more affected process is exposed to the public Internet. Can be "true" or "false".
{DataAssetsReachable}: Describes whether one or more affected process can reach data assets. Can be "true" or "false".
{ExploitAvailable}: Describes whether there's an exploit available for the vulnerability. Can be "true" or "false".
AppsecNotificationWebhookConfiguration, AppsecNotificationWebhookConfigurationArgs
- Accept
Any boolCertificate - Accept any SSL certificate (including self-signed and invalid certificates)
- Url string
- Webhook endpoint URL
- Headers
Pulumiverse.
Dynatrace. Inputs. Appsec Notification Webhook Configuration Headers Use additional HTTP headers to attach any additional information, for example, configuration, authorization, or metadata.
Note that JSON-based webhook endpoints require the addition of the Content-Type: application/json header to enable escaping of special characters and to avoid malformed JSON content.
- Accept
Any boolCertificate - Accept any SSL certificate (including self-signed and invalid certificates)
- Url string
- Webhook endpoint URL
- Headers
Appsec
Notification Webhook Configuration Headers Use additional HTTP headers to attach any additional information, for example, configuration, authorization, or metadata.
Note that JSON-based webhook endpoints require the addition of the Content-Type: application/json header to enable escaping of special characters and to avoid malformed JSON content.
- accept
Any BooleanCertificate - Accept any SSL certificate (including self-signed and invalid certificates)
- url String
- Webhook endpoint URL
- headers
Appsec
Notification Webhook Configuration Headers Use additional HTTP headers to attach any additional information, for example, configuration, authorization, or metadata.
Note that JSON-based webhook endpoints require the addition of the Content-Type: application/json header to enable escaping of special characters and to avoid malformed JSON content.
- accept
Any booleanCertificate - Accept any SSL certificate (including self-signed and invalid certificates)
- url string
- Webhook endpoint URL
- headers
Appsec
Notification Webhook Configuration Headers Use additional HTTP headers to attach any additional information, for example, configuration, authorization, or metadata.
Note that JSON-based webhook endpoints require the addition of the Content-Type: application/json header to enable escaping of special characters and to avoid malformed JSON content.
- accept_
any_ boolcertificate - Accept any SSL certificate (including self-signed and invalid certificates)
- url str
- Webhook endpoint URL
- headers
Appsec
Notification Webhook Configuration Headers Use additional HTTP headers to attach any additional information, for example, configuration, authorization, or metadata.
Note that JSON-based webhook endpoints require the addition of the Content-Type: application/json header to enable escaping of special characters and to avoid malformed JSON content.
- accept
Any BooleanCertificate - Accept any SSL certificate (including self-signed and invalid certificates)
- url String
- Webhook endpoint URL
- headers Property Map
Use additional HTTP headers to attach any additional information, for example, configuration, authorization, or metadata.
Note that JSON-based webhook endpoints require the addition of the Content-Type: application/json header to enable escaping of special characters and to avoid malformed JSON content.
AppsecNotificationWebhookConfigurationHeaders, AppsecNotificationWebhookConfigurationHeadersArgs
AppsecNotificationWebhookConfigurationHeadersHeader, AppsecNotificationWebhookConfigurationHeadersHeaderArgs
- Name string
- no documentation available
- Secret bool
- Secret HTTP header value
- Secret
Value string - The secret value of the HTTP header. May contain an empty value.
- Value string
- The value of the HTTP header. May contain an empty value.
- Name string
- no documentation available
- Secret bool
- Secret HTTP header value
- Secret
Value string - The secret value of the HTTP header. May contain an empty value.
- Value string
- The value of the HTTP header. May contain an empty value.
- name String
- no documentation available
- secret Boolean
- Secret HTTP header value
- secret
Value String - The secret value of the HTTP header. May contain an empty value.
- value String
- The value of the HTTP header. May contain an empty value.
- name string
- no documentation available
- secret boolean
- Secret HTTP header value
- secret
Value string - The secret value of the HTTP header. May contain an empty value.
- value string
- The value of the HTTP header. May contain an empty value.
- name str
- no documentation available
- secret bool
- Secret HTTP header value
- secret_
value str - The secret value of the HTTP header. May contain an empty value.
- value str
- The value of the HTTP header. May contain an empty value.
- name String
- no documentation available
- secret Boolean
- Secret HTTP header value
- secret
Value String - The secret value of the HTTP header. May contain an empty value.
- value String
- The value of the HTTP header. May contain an empty value.
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dynatrace
Terraform Provider.