Slack

Send Aegis notifications to a Slack channel, and let people look up the compliance overview, open risks and active incidents from Slack with the /aegis command.

The Slack connector links Aegis to one Slack workspace through a Slack app that your organisation creates and owns. Once it is authorised, Aegis posts notifications to a channel you choose, and anyone in the workspace can type /aegis to see a short summary from Aegis without leaving Slack. Each organisation has one Slack configuration.

At a glance

Direction Out of Aegis (notifications) and into Aegis (the /aegis command).
What it sends Notifications to the Default Channel set on the connector page or, when that field is blank, to the channel picked while installing the app in Slack.
What the command returns /aegis status, /aegis risks, /aegis incidents and /aegis help read from Aegis; they do not change anything. Risks stay in Risks and incidents in Incidents.
Credentials and permissions A Slack app (client ID, client secret and signing secret) with the scopes listed on the connector page, the redirect, slash-command and interactivity addresses from the connector page, then Authorize with Slack.
When it runs At the moment a notification is sent or the command is used. It does not sync on a schedule.
Set it up /connectors/slack, by an Admin or Manager, where the Slack connector module is switched on for your organisation.

Who uses it

What’s on this screen

Open Connectors and choose Slack. The page reads from top to bottom:

No screenshot in this chapter

The screenshots for this guide were taken with a role that cannot open the Slack connector page (it shows the access-denied screen), so this chapter describes the screen in words. The labels above are the ones the page shows.

Prepare the Slack app

Do this in Slack first, with the Aegis page open beside it so you can copy the addresses.

  1. Create a Slack app at api.slack.com/apps. Slack opens the app’s Basic Information page.
  2. Under OAuth & Permissions, add the scopes the Aegis page lists: chat:write, commands, incoming-webhook and channels:read. Set the redirect URL to the /api/connectors/slack/callback address shown in Setup Instructions.
  3. Create a slash command named /aegis whose request URL is the /api/connectors/slack/commands address from the Slash Command Setup box.
  4. Turn on Interactivity and set its request URL to the /api/connectors/slack/events address from the same box.
  5. Copy the Client ID, Client Secret and Signing Secret from the app’s Basic Information page. You enter them in Aegis next.

Save the configuration

  1. Paste the client ID into Client ID. Save Configuration stays unavailable until this field has a value.
  2. Paste the client secret and the signing secret into Client Secret and Signing Secret. Both fields hide what you type. After a save they show ********; leave them blank later to keep the stored secrets.
  3. Optionally type a channel in Default Channel:, for example #security-alerts. Leave it blank to use the channel you pick when installing the app.
  4. Select Save Configuration. The Connection Status changes to Authorization Required, an orange note says OAuth authorisation is required to connect to Slack, and an Authorize with Slack button appears.

Authorise and test the connection

  1. Select Authorize with Slack. Slack’s install screen opens; choose the workspace and the channel for notifications, then allow the app.
  2. Slack sends you back to /connectors/slack. The connector is now marked Connected, and the status panel offers Test Connection and Re-authorize. If anything goes wrong on the way back, Aegis returns you to the Connectors overview instead.
  3. Select Test Connection. The dot shows Testing..., then either Connected with a green Connected to Slack box naming the team and channel, or Connection Failed with the reason. When Slack no longer accepts the stored token, the status returns to Authorization Required; authorise again.
  4. With the status Connected, select Send Test Message under Test Notifications. Aegis posts “Test message from Aegis” to the channel picked during the install and shows a confirmation.
Check the channel, not only the confirmation

The test message goes to the channel chosen during the Slack install, not to Default Channel:. If no install channel was recorded, Aegis can still show the success confirmation without posting anything. Look in Slack to be sure the message arrived.

Use the /aegis command

Once the app is installed, anyone in the workspace can type these in any channel the app can see. Aegis answers in Slack.

Command What it shows
/aegis status The compliance overview and key metrics.
/aegis risks Top open risks by severity.
/aegis incidents Active incidents.
/aegis help The list of commands. Any other word after /aegis also shows this list.

Disconnect Slack

  1. In Disconnect connector, select Disconnect. A confirmation asks whether to disconnect Slack and explains that the configuration and credentials are deleted.
  2. Confirm with Disconnect. Aegis deletes the stored configuration and credentials and returns you to the Connectors overview. Records already in Aegis stay where they are, and you can configure the connector again later.

Good to know

Tips and limits

Where this connects

Each person chooses Slack in their preferences — see Notifications and Settings. The Connectors overview lists every connector and its status. For Microsoft Teams, see Teams; for other destinations, see Webhooks. The /aegis command reads from Risks and Incidents, and connector tests appear in the Audit log.