Security alert integrations: Slack, Teams, APIWhen a critical flaw lands, your team sees it in the channel.Alerts to chat, data to your own systems.
Noroxi alerts go to Slack, Microsoft Teams, Discord, email and RSS; CVE data reaches your own tools through the REST API and MCP. From an issue in the panel you open a ticket in GitHub, GitLab, Jira or Linear.
All of it works with a free account. Pro ($29/month) raises the daily API quota and the number of keys, and sends channel alerts every 10 minutes.
- Paste a webhook address. Only Slack, Teams and Discord addresses are accepted; requests go nowhere else.
- Only what matters reaches the channel: a record added to KEV or weaponized, an urgent issue, a dangling record, a site outage.
- Every 60 minutes on Free, 10 on Pro; site outages right away.
What are Noroxi integrations?
Noroxi integrations send CVE and site outage alerts to Slack, Microsoft Teams, Discord, email and RSS, and hand CVE data to your own systems through a REST API and an MCP server. From an issue in the panel you can open a ticket in GitHub, GitLab, Jira or Linear.
Where it connects
Every connection works with a free account; setup is one address or one key.
Slack, Teams, Discord
Paste a webhook address; critical vulnerability and outage alerts land in the channel. Each platform gets its own message format.
Slack · Teams · Discord
Email
Unread notifications in one email a day; site outages right away.
1 digest a day · outages at once
RSS
A personal feed for your stack, vendor feeds and national advisories.
personal · vendor · nationalNational advisories
REST API
CVE search, stack matching, SBOM and domain scans; JSON, with an API key.
GET /api/v1/cve/{id}API docs
MCP server
MCP clients query the CVE database directly over JSON-RPC; it works without a key, and an API key raises the quota.
POST /api/mcpSetup
Issue trackers
From a CVE page and from every issue in the panel, open a pre-filled ticket form. Connect the tracker in Settings and the ticket is created in one click; the token is stored encrypted.
GitHub · GitLab · Jira · Linear
Each platform gets its own message format
Block Kit for Slack, a card for Teams, an embed for Discord. No bot to write; the button opens the record.
// Sample body · the KEV message above
{
"text": "CVE-2024-23897 · Added to CISA KEV — actively exploited in the wild — Arbitrary file read vulnerability through the CLI can lead to RCE · Action score: 98 · CISA KEV · stack: jenkins",
"blocks": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "*CVE-2024-23897 · Added to CISA KEV — actively exploited in the wild*\nArbitrary file read vulnerability through the CLI can lead to RCE · Action score: 98 · CISA KEV · stack: jenkins"
}
},
{
"type": "actions",
"elements": [
{
"type": "button",
"text": {
"type": "plain_text",
"text": "Open record"
},
"url": "https://noroxi.com/en/cve/CVE-2024-23897"
}
]
}
]
}// Sample body · the KEV message above
{
"type": "message",
"attachments": [
{
"contentType": "application/vnd.microsoft.card.adaptive",
"content": {
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.4",
"body": [
{
"type": "TextBlock",
"text": "CVE-2024-23897 · Added to CISA KEV — actively exploited in the wild",
"weight": "Bolder",
"size": "Medium",
"wrap": true,
"color": "Attention"
},
{
"type": "TextBlock",
"text": "Arbitrary file read vulnerability through the CLI can lead to RCE · Action score: 98 · CISA KEV · stack: jenkins",
"wrap": true
}
],
"actions": [
{
"type": "Action.OpenUrl",
"title": "Open record",
"url": "https://noroxi.com/en/cve/CVE-2024-23897"
}
]
}
}
]
}// Sample body · the KEV message above
{
"content": "CVE-2024-23897 · Added to CISA KEV — actively exploited in the wild",
"embeds": [
{
"title": "CVE-2024-23897 · Added to CISA KEV — actively exploited in the wild",
"description": "Arbitrary file read vulnerability through the CLI can lead to RCE · Action score: 98 · CISA KEV · stack: jenkins",
"url": "https://noroxi.com/en/cve/CVE-2024-23897",
"color": 16737129
}
]
}An agency account connects a separate channel per client; each message starts with [client name].
From an issue to a ticket in one click
With Jira connected the button creates the ticket directly; without it a pre-filled form opens and you confirm it.
The ticket carries the domain, severity, evidence line, fix and a panel link; evidence attachments, notes and the assignee are left out. Closing the Jira ticket does not close the issue.
How to connect an integration
- Create a free account.
- Paste your webhook on the Notification channels page in Settings; get an API key on the API page in Settings.
- Press “Send test message”; it shows up in your channel.
Integrations: Free and Pro
| Free | Pro · $29/mo | |
|---|---|---|
| API calls / day / key | Free250 | Pro · $29/mo5,000 |
| API keys | Free1 | Pro · $29/mo5 |
| Slack / Teams / Discord alert | Freeevery 60 minutes | Pro · $29/moevery 10 minutes |
| Site outage notification | FreeRight away | Pro · $29/moRight away |
No auto-renewal. See the plans
Questions
Does it create the Jira ticket by itself?
Which webhook addresses are accepted?
Is the API free?
Connect your first channel in a minute
Paste the webhook address and send the test message.