Attaxion can send notifications about newly discovered vulnerabilities to Slack. To enable notifications, you’ll need to configure an integration between Slack and Attaxion.
To integrate Attaxion with Slack, in Attaxion, select “Integrations” in the menu on the left, and click “Configure” next to Slack in the list of the available integrations.
You will be prompted to enter your Slack workspace.
Enter the URL of your Slack workspace (you can find it in Slack by clicking on the name of the workspace at the top left corner) and click “Continue.”
Then, Slack will prompt you to log in to your workspace.
Enter the email address that you use to log in into this Slack workspace. Slack will send a 6-digit code to this email, which you’ll need to copy and paste on the login page.
Once you’re done with this, you’ll see a page saying that Attaxion is requesting permission to access the workspace. Choose a channel that you want notifications to appear in and click “Allow.” If you want to use a new channel, create one in Slack first.
Attaxion will inform you that the integration with Slack has been successfully set up and will suggest posting a test message to the channel.
The test message looks like this:
Configuring Slack Notifications
Attaxion allows you to choose if you want to receive notifications about all vulnerabilities or only about ones of certain severity and above.
To adjust these settings, go to "Account" in the menu on the left. There, you will see notifications settings both for email and for Slack.
Make sure that the radio buttons for "Slack notifications" and "Issue notifications" are enabled if you want to receive Slack notifications.
Choose the minimum severity to receive notifications about. You can choose between Info, Low, Medium, High, and Critical. If you choose Medium, for example, you'll only be getting Slack notifications about vulnerabilities with Medium, High, or Critical severity.
Using Slack Notifications
Once Attaxion discovers a new vulnerability, it’ll post a message to the selected channel, providing the name of the issue, the vulnerable asset, and the vulnerability severity.
