feed_name

Overview

This feed is managed. You cannot change all aspects of the feed!
Master feed:
master_feed_name
ID:
feed_id
Version:
version
Version history:
version_history
Tenant domain:
tenant_domain
Created At:
created_at
Updated At:
updated_at

Statistics

Last run:
last_run

Attributes

Description:
description
Frequency:
frequency
Color:
color
Cypher:
cypher

Analytic Buckets

bucket_name

cybernality Updates

Bugfix
Fixed bug in new subscription process
An error has occurred on the success page when creating new subscriptions. This has now been fixed.

We identified an issue affecting the success page that appears after creating a new subscription. Specifically, an error was being triggered during the final step of the subscription process, which may have disrupted the user experience or caused confusion. The root cause has been identified and the issue has now been resolved. The success page is functioning as expected again.

Feature
Introducing AI-enhanced Severity Information
Extended severity information including explanations and AI-based risk assessment are now available for ResultItems.

Extended severity information is now available on the detail page for ResultItems of classification Security Advisory, Vulnerability Discovery and Patch Announcement. This is based on the source information and its risk is assessed in detail using AI.

Where to find the severity information?

Click on the icon which opens a new tab for the resultitem details page:

On the details page scroll down to the section “Severity”:

To get details about the CVSS vectors click on the label:

To read an AI-enhanced risk assessment open it by clicking on the arrow icon:

Feature
MS Teams Incoming Webhook Integration
With our brand new integration for MS Teams incoming webhooks you receive notifications easily and quickly directly in MS Teams.

With notifications from cybernality, you can continue working wonderfully in MS Teams. Collaboration during evaluation and analysis is simplified, distribution to different specialist groups is made possible and subsequent further processing of the information in third-party tools such as ITSM etc. is facilitated.

What options are available?

There are different ways to get cybernality notifications in MS Teams:

  • via Teams channel email address (rate limiting can cause problems)
  • via Azure Bot service that posts the messages to your Teams channel (higher implementation effort, but free design options for formatting messages in teams)
  • via incoming webhooks (simple and quick to implement)

We offer a ready-made integration for the latter option, which we will explain in more detail below.

Preparations in MS Teams

To automatically post to a chat or channel when a webhook request is received, create a workflow from scratch using the “When a Teams webhook request is received” trigger. You can read more about it here.

Create API Recipient of type ms_teams_webhook

After you have created the ‘incoming webhook’ in MS Teams, you can create a new API Recipient in cybernality. To do this, proceed as follows:

Navigate to the Recipients section:

Shows the recipients section in cybernality and lists the current available recipients.

Click on the MS Teams icon on the right-hand side of the API sub-area:

Shows the header section of the api recipients sub area with the teams icon to click on.

A popup window opens where you define the name of the new api recipient:

After submitting, you will be redirected to the recipient form where you can add further information:

It is mandatory to fill in the MS Teams webhook URL. After adding, press enter to save the change.

You can also enter a description and an avatar icon for this Api recipient.

In the ‘Triggers’ section, you decide when you want to receive notifications, either for new or updated results or both.

Final todos

To be able to receive notifications in your new MS Teams channel, you still need to connect the recipient to an analytic bucket:

That was it. Now you can receive messages in Teams! That is how it looks like:

List Feeds

Feeds

  • feed_name
No results.