Advanced Settings
This stage allows you to select notification channels if a policy violation occurs. The notification alerts are sent at two levels.
Admin Alerting
This section allows you to send notifications to Nightfall users. The various alert methods are as follows. You must first turn on the toggle switch to use an alert method.
The alert configurations configured in this section describe the process of creating alerts at the policy level. Policy-level alerts are applicable only to the policy on which they are configured. To configure an alert on all the GitHub policies, you must configure alerts at the integration level. To learn more about how to configure integration-level policies for Github integration, read this document.
Slack Alert: Select a Slack channel to which the violation alerts must be sent. To configure this alert method, Slack must be enabled as an Alert method. To learn more about configuring Slack as an alert channel, refer to this document.
Jira Alert: Select the JIRA project and other parameters. A JIRA ticket is created in the selected JIRA project for each policy violation.
Email Alert: Enter the Email address of the recipient who needs to be notified about policy violations.
Webhook Alert: Configure webhook URL and headers.
When you configure alerts to a Webhook, Nightfall AI sends occasional posts to:
To validate that the Webhook is properly configured before the policy is saved.
Periodically thereafter to ensure that the Webhook is still valid.
The response to the test Webhooks is 200 status code if successful.
An example of Webhook request is as follows.
This is part of alert event consumption and can be ignored.
End-User Notification
This section allows you to configure notifications to be sent to the end user whose actions triggered the violation.
Custom Message
Enter a custom message to be sent to the end user. This message is sent in an Email. You can modify the default message provided by Nightfall and draft your message. The total character length allowed is 1000 characters. You can also add hyperlinks in the custom message. The syntax is <link | text >. For example, to hyperlink www.nightfall.ai with the text Nightfall website, you must write <www.nightfall.ai|Nightfall website>.
Automation
You can select one of the following methods. You must turn the toggle switch to use this option.
Via Email: This option sends an Email to the GitHub developer. If Nightfall cannot detect the Email ID of the developer, the Email ID provided in the Fallback Email field is used.
Via GitHub: This option tags the developer in the Pull Request / Commit with the details on the violation. This will also generate a notification that the developer can view in their GitHub profile account.
To learn more about how you can view Notifications in GitHub, see this document.
End-User Remediation
End-user remediation (also known as Human Firewall) allows you to configure remediation measures that end users can take, when a violation is detected on their GitHub operations. You must turn on the toggle switch to use this option. The various available options are as follows.
Report as False Positive with Business Justification: This option allows end users to report false positive alerts and provide a business justification as to why the alert is considered to be false positive.
Report as False Positive: This option allows end users to report false positive alerts.
When a Violation is Reported as False Positive: You can use this option to set actions to be taken when a violation is reported as false positive by the end-user. You can either set the remediation to be automatic or manual.
Remind Every (until Violation expires): You can use this option to set a reminder for the end-user to take action on the violation. You can choose to remind the end user every 24, 48, or 72 hours.
To understand where end users can see these options, see GitHub Notifications
Last updated
