RedKit alerting
Send RedKit and security monitoring findings to webhooks, GitHub issues or Jira tickets, opened when a finding appears and closed when it is fixed.
Alerting decides where findings go once a scan finishes. Open it from RedKit → Settings → Alerting, next to History and the scheduled scans.
| Channel | What it does |
|---|---|
| Webhooks | Slack, Discord, Teams or a signed endpoint, notified on new findings. Configured once per organization in Organization settings → Webhooks. |
| GitHub Issues | One issue per finding in the repository you pick |
| Jira | One ticket per finding in the Jira Cloud project you pick |
How issue trackers work
Link a verified domain or IP network to a GitHub repository or a Jira project, and the tracker follows the findings:
- A scan that finds something opens an issue or ticket.
- The scan that no longer sees it closes it.
- If the finding comes back, it is reopened.
- Marking a finding false positive or accepted risk closes its issue; removing the tag reopens it.
- A scan that ran only some modules never closes the findings of the others.
- An issue your team closes by hand stays closed while the finding is still there. It can reopen only if the finding goes away and comes back.
Linking catches up right away: the findings already known from past scans are filed at once. Security monitoring findings on the linked domain or network open and close tickets too.
Issues and tickets carry the mlab label, so you can filter on them.
Connect GitHub
Connect Jira
https://<name>.atlassian.net), the account email and the API token.The token is stored encrypted and only ever sent to your atlassian.net site. Tickets
are closed and reopened through your workflow's own transitions, so custom Jira workflows
keep working.
Link a domain or network
Each domain or network can be linked to one tracker. The table of links shows the tracker, the minimum severity, the open issues and the last sync. From it you can:
- Change the minimum severity: issues below the new threshold are closed, the rest are filed.
- Sync now: bring the tracker up to date and see how many issues were opened, reopened and closed.
- Unlink: stop updating the tracker. Existing issues stay where they are.
Public repositories. Issues are filed in private repositories by default. Linking a public repository needs an explicit confirmation: anyone could then read what is exposed, misconfigured or unpatched, and issues stay indexed and archived even after you delete them. Only do this if the findings are already public or harmless.
Who can do what
Owners and Admins connect GitHub and Jira, link and unlink targets, change the severity and sync. Other members see the page.