Skip to main content

Integrating Invicti Enterprise with Microsoft Teams

This document is for:
Invicti Enterprise On-Demand, Invicti Enterprise On-Premises

Microsoft Teams is a unified communications platform that combines team messaging and calling, video scheduling and meetings, file storage and collaboration, and an education forum. It integrates with Office 365 and has extensions to integrate with non-Microsoft products too.

This topic explains how to configure Invicti Enterprise to send a detected vulnerability to Microsoft Teams.

For further information, see What Systems Does Invicti Integrate With?.

Microsoft Teams Fields

This table lists and explains the Microsoft Teams fields in the New Microsoft Integration window.

Button/Section/FieldDescription
NameThis is the name of the configuration that will be shown elsewhere.
MandatoryThis section contains fields that must be completed.
WebHook URLThis is the webhook URL to which issues are sent.
Title FormatThis is the string format that is used to create the vulnerability title.
OptionalThis section contains optional fields.
Theme ColorThis is the color of the message card.
Create Sample IssueOnce all relevant fields have been configured, click to create a sample issue.

Prerequisite

Create a webhook URL on Microsoft. For further information, see Create an Incoming Webhook.

How to Integrate Invicti Enterprise with Microsoft Teams

  1. Log in to Invicti Enterprise.
  2. From the main menu, select Integrations > New Integration.
  3. From the Communication section, select Microsoft Teams.
Microsoft Teams integration in Invicti Enterprise
  1. In the Name field, enter a name for the integration.

  2. In the Mandatory section, complete the connection details:

    • WebHook URL
    • Title Format
  3. In the Optional section, you can specify:

    • Theme Color
  4. Click Create Sample Issue to confirm that Invicti Enterprise can connect to the configured system. A confirmation message is displayed to confirm that the sample issue has been successfully created.

  5. If the Microsoft Teams integration is not configured correctly, Invicti Enterprise will correctly route the following descriptive error messages to you.

  6. Select Save.

tip

Test the integration by creating a sample issue to ensure that the webhook URL is correctly configured and that messages can be sent to your Microsoft Teams channel.

How to export reported vulnerabilities to projects in Microsoft Teams

There are several ways to send issues to Microsoft Teams with Invicti Enterprise:

Automatic Notifications

Once notifications have been configured, you can configure Invicti Enterprise to automatically send vulnerabilities after scanning has been completed (see How to Configure a Notification to Report Vulnerabilities to an Issue Tracking System).

From the Issues Window

You can send one or more issues from the Issues window:

  • You must have Manage Issue permission.
  • From the main menu, select Issues then All Issues.
  • From the Issues page, select one or more issues you want to send.
  • Select Send To > Microsoft Teams.
Sending issues to Microsoft Teams from Issues window

A pop-up is displayed, with a message to the issue you have sent to Microsoft Teams. If there is an error, this information will be displayed instead.

From the Recent Scans Window

You can send an issue from the Recent Scans window:

  • From the main menu, select Scans > Recent Scans.
  • Next to the relevant scan, select Report.
  • Scroll down to the Technical Report section.
  • From the list of detected vulnerabilities, select an issue and display its details.
  • Select Send To > Microsoft Teams.
Sending issues to Microsoft Teams from Recent Scans
important

If you have previously submitted this vulnerability to Microsoft Teams, it will already be accessible. You cannot submit the same issue twice.

If you view opened problem logs in Microsoft Teams, they look like this:

Example of Microsoft Teams notification from Invicti

Need help?

Invicti Support team is ready to provide you with technical help. Go to Help Center

Was this page useful?