Skip to content

chrisbeckett/rbk-teams-connector

Repository files navigation

Rubrik Security Cloud Microsoft Teams Connector

TL;DR, got a demo video?

Why yes. Remember to click "like" ;-) https://youtu.be/nF5M47PYZUY

Alt text

What does it do?

This connector runs as an Azure Function and provides a webhook URL for Rubrik Security Cloud (RSC, formerly Polaris) to send alerts to. This provides simple connectivity to Microsoft Teams as it sends alert information as cards into a Teams channel. The serverless function can be quickly and easily deployed using the 'Deploy to Azure' button at the bottom of the page.

How does it work?

Create a new webhook in the RSC "Security Settings" page (can be accessed via the gear icon in the top right hand corner) and filter out the required events and severity. For example, to send backup operations events to Teams, you may wish to select the "Backup", "Diagnostic", "Maintenance" and "System" event types with the "Critical" and "Warning" severities.

Product documentation can be found at https://docs.rubrik.com/en-us/saas/saas/common/webhooks.html.

alt text

alt text

A simple architecture diagram is shown below. In essence, we send a webhook event from RSC to an Azure Function, this then takes the raw JSON event payload and converts it into Teams "card" format and sends it to the Teams channel URL specified in the environment variable.

alt text

What do I need to get started?

Obtaining the code

Run git clone https://github.com/chrisbeckett/rbk-teams-connector.git

Deploying the Azure Function

Click the "Deploy to Azure" button and fill out the deployment form

  • Both the Azure Function name and the Storage Account name must be globally unique or deployment will fail (if a new storage account is created)
  • Once the ARM template deployment is complete, open a command prompt and navigate to the rbk-teams-connector folder
  • Install the Azure Functions command line tools (https://docs.microsoft.com/en-us/azure/azure-functions/functions-run-local?tabs=windows%2Ccsharp%2Cbash)
  • Run az login from a command prompt to establish authentication to Azure
  • Tip To avoid potential deployment issues, it is recommended to pin the Python version in the Function to the version you have installed locally on your staging machine. To do this, run this command from a command prompt - az functionapp config set --name function-name --resource-group resourcegroupname --linux-fx-version "Python|3.9" (change the function name, resource group and Python version as appropriate)
  • Run func init
  • Run func azure functionapp publish functname where the functname is your function name from the "Deploy to Azure" workflow
  • When this is complete, you will need the HTTP trigger URL (Function overview, "Get Function URL" button)

Deploy to Azure

About

MS Teams Connector for Rubrik Security Cloud

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages