In this section, you can select the Detection rules for the policy and If not already created, you can create detection rules. To learn more about how to configure detection rules, see Configuring Detection Rules.

To select detection rules, select the detection rules from the list of rules that display.

You can also sort the rules that you want to view.

• All Detection Rules: View all detection rules created

• Selected Detection Rules: View detection rules that are selected and mapped to this policy

• Unselected Detection Rules: View detection rules that are neither selected nor mapped to this policy.

1. Click Next.

This section describes the various actions that Nightfall takes automatically when a violation is detected. You must turn on the toggle switch to enable an action. You can also set the timeline as to when an action must be taken (immediately after detecting a violation or after some time).

Currently, Nightfall supports the Delete automated action for the Slack Pro and Business+ editions.

You must first turn on the toggle switch to enable any of the automated actions.

Once you enable the toggle switch, you can configure when the action must be applied.

If you select immediately, the action is implemented automatically after the sensitive data is detected.

If you select After, you must also set the time frame as to when exactly the action must be applied, after detecting the sensitive data.

The action is described as follows.

Delete

The delete action automatically deletes the message or attachment that has sensitive data. This is a permanent action and cannot be reverted.

DLP policies are a set of rules that include specific conditions, actions, and exceptions that monitor and filter data. DLP policies help you to monitor and remediate the flow of sensitive data within your organization. Depending on your Nightfall policy configuration, you can set up policies to monitor data that is sent through some or all applications within your organization. You can configure policies and choose to not apply them all the time.

Before you define a policy, or a set of policies, you must define the objectives of each policy, which can then be fulfilled when you configure the policy. Here are a few important questions to ask before configuring your policies:

• What data do you plan to monitor?

• Where within the organization do you want to monitor?

• What should be the scope of each policy?

• What conditions must apply for the policy to match?

• What exceptions/exclusions can be allowed?

• What remediation actions should the policy take?

You can now set up policies to determine which Slack channels are monitored (and which are excluded) for violations and what actions Nightfall must take. Policies determine the content that will be scanned by Nightfall, and workflows that are followed to manage violations.

Policies for Slack integration allow you to define configurations specific to Slack, such as how to handle messages for particular channels or use automated actions such as Quarantine.

Creating a Nightfall policy involves the following tasks:

1. Create Policies

2. Define the policy scope and exclusions

3. Configure Detection Rule

4. Configure Automated Actions

Refer to Creating Policies and Defining Policy Scope pages for the procedures to configure policies for Nightfall for Slack.

Note: Instructions to configure policies differ for Slack Pro and Slack Enterprise options. Refer to the Slack tier that you are using.

In this stage, you select the Integration for which the policy is created. In this case, Slack integration must be selected.

1. Click Policies from the left menu.

2. Click + New Policy.

3. Select the Slack integration.

This document explains how to set up the Policy Scope for Slack Pro and Slack Business+ editions. If you are using a Slack Enterprise edition, you must refer to .

The Scope stage allows you to select Slack Channels and Connections which must be scanned by the policy.

To configure Policy Scope:

1. Select one of the following options under the Select Channels section. The scope of this policy is limited to only those channels and connections which you select in this section.

• Channels: Select the Select All check box to scan the data in all your Slack channels. Select the Public Channels check box to scan data only in your Public Slack Channels. Select the Private Channels check box to scan data only in your private Slack channels.

• Connections: Select the Select All check box to scan the data in all your Slack connections. Select the Public Connect Channels check box to scan data only in your Public connect Slack Channels. Select the Private Connect Channels check box to scan data only in your private connect Slack channels.

The Exclusion section allows you to exclude users and applications from being scanned by Nightfall.

1. (Optional) Select the name of the users to be excluded, from the Exclude Users drop-down menu.

2. (Optional) Select the name of the applications to be excluded, from the Exclude Apps drop-down menu.

3. Click Next.

Example Scenario

Consider that you wish to scan all the Public and Private Slack channels. However, you wish to exclude messages from the Slackbot user (since it's a bot) and the Nightfall Pro app. You can accomplish this task as shown in the following image.

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.

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 .

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.

{
  "service": "nightfall",
  "test": true,
  "timestamp": "2024-03-07T23:18:39Z"
}

End-User Notification

This section allows you to configure notifications to be sent to the end user whose actions triggered the violation.

Custom Message

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 End user.

• Via Slack: This option sends a Slack notification to the end-user in a pre-configured channel.

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.

• Delete: This option allows the end-user to delete the message that caused the violation.

• 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.

When an end user violates a policy in GitHub, a notification is generated based on the notification settings configured by you in the policy configurations.

This document explains where you can find notifications on policy violations and what actions can be taken.

Nightfall Violations Page

To view the Nightfall violations page:

1. Navigate to the Violations page in Nightfall.

2. Apply filters to view only Slack violations.

3. (Optional) Modify the days filter to view historical violations. You can view violations up to past 180 days.

1. You can also use the search bar to search Slack violations. The difference between search bar and filters is that search bar searches for all the Slack violations. You need not apply time filter after applying the search bar filter.

1. (Optional) Hover over a violation to view the severity of the violation. You can also check how likely is it that the detected violation is an actual violation (Likely, Very Likely).

2. Click the ellipsis menu in the right corner to view the list of actions that you can take to initiate on the violation.

3. Click on any violation to view the exact data that caused the violation (highlighted in red).

Email Notification

• When a data leak occurs, Slack sends an Email to end users, if they have configured Email as a Notification method in their Slack account.

• Additionally, if you have configured Email Notification in Admin Alerting, Nightfall admins receive the Email notification.

• If you have configured Email Notification in the Automation section of End user notification settings, end users receive an email from Nightfall. This Email allows end users to take actions from within the Email.

The Email received from by Nightfall Admins and end-users (if configured), looks as follows.

Viewing Notifications in Slack

If you have configured Slack as a Notification in the Automation section of End User Notification, end users can view the violation notification from within Slack.

In this final stage, you assign a name to the policy, verify your configurations, and create the policy.

1. Enter a name for the policy.

2. (Optional) Enter a description for the policy.

3. Click Next.

4. Verify if all the policy configurations are set up as per your requirements.

5. (Optional) Click back to modify any of the policy configurations.

6. Click Submit.