Slack Integration¶
The BoostSecurity Slack integration provides the ability to send notifications of activity to a Slack channel.
Installation¶
- Go to the Integrations page.
- Click on the Slack tile.
- Within the integration drawer, click on the Install button.
- Once redirected to a Slack webpage, select the channel intended for sending notifications to.
Configuration¶
- Go to the Integrations page.
- Click on the Slack tile.
- Within the integration drawer, click the
Configuration
tab.
Elect a default channel¶
Select the default
checkbox to indicate that the channel should be used to receive notifications when a policy is configured to send notifications to the default
channel. To see an example of this, review the Application section of this page.
Remove a channel¶
Click on the trash icon and when the modal appears, click the Yes
option. This severs the connection between the Slack channel and the Boost Slack application.
Send Slack Notifications¶
- Go to the Policy page.
- Edit an existing policy or begin creating a new policy that is to use the Slack integration.
- For either the default action or an action associated with a specific
rule
statement, selectSend a notification
. - In the modal that appears, apply the following to the following fields:
a. Integration
: Slack
b. Name
: The name of the channel that is expected to receive notifications. Use default
to send notifications to the channel that is designated as the default
channel in the configuration settings of the Slack integration on the Integrations page.
c. Notify when
:
-
Notify when it is a new violation being reported
: Select this option to receive notifications on all net-new violations. -
Notify when the violation is resolved
: Select this option to receive notifications when a scan has found a violation to be resolved. -
Notify when the violation is being suppressed
: Select this option to receive notifications when a user has taken action within Boost against an item (e.g. has marked a violation asFalse Positive
) or if a user has suppressed a violation with the#noboost
keyword within source code.