AI Agents Coming Soon— AXGNT and AXUMIS are almost here. Autonomous AI pentesting that thinks, reasons, and adapts like human experts. Operating 24/7 at machine speed.AI Agents Coming Soon— AXGNT and AXUMIS are almost here. Autonomous AI pentesting that thinks, reasons, and adapts like human experts. Operating 24/7 at machine speed.
Axum SEC Logo
Integrations

Findings into your delivery tooling

Fixes land where your team already works

Findings that never reach engineering do not get fixed. Connect the platform to your issue tracker and collaboration tools so remediation happens in the systems your teams use every day.

Talk to usRead the integrations doc

Field-mapping depth and bidirectional state sync are Professional-tier and above.

Platform viewLive
  • Jiralinked
  • GitHublinked
  • Slacknotified
  • Teamsnotified

Supported systems

Where findings can go

Two categories of integration: systems of record for remediation work, and notification channels that keep people informed without polling a dashboard.

Issue trackers and source control

Remediation work is created where engineering plans and ships.

  • Jira

    Issues in the project that owns the fix, with severity mapped to priority.

  • GitHub

    Issues and pull requests, so fixes and findings reference each other.

  • GitLab

    Issues and merge requests in GitLab-managed delivery.

  • Azure DevOps

    Work items in Azure Boards, with state flowing back to the finding.

Collaboration and notifications

Channel notifications per program and per severity, so noise stays proportionate.

  • Slack

    New findings, state changes and SLA warnings routed to the right channel.

  • Microsoft Teams

    Channel and chat notifications where Teams is the collaboration layer.

What syncs, and what stays

Integrations carry the finding — not the whole program. Some things deliberately do not travel.

Finding summary
Title, severity, affected asset and current state sync to the destination.
Evidence
Referenced by link rather than copied, so access rules stay enforced in one place.
Ownership and deadlines
Pushed into the tracker so engineering plans the work where planning happens.
State changes
Bidirectional where configured: a resolved ticket can move the finding to remediation-complete.
Researcher identity
Can be withheld from engineering-facing tickets, depending on program configuration.
Rewards and disclosure
Never sent to engineering systems; kept on the platform under program policy.

Documentation

Integration detail

Integrations

Behaviour, auth scopes, sync semantics and setup steps.

Read the doc

Remediation and verification

The lifecycle the integrations feed into.

Read the doc

Identity and access

How integration credentials and access are governed.

Read the doc

Common questions

Integration questions we hear most

Do we have to change how engineering works?
No. Findings are created in the tracker your team already uses, and evidence is linked rather than duplicated. The security record stays on the platform; the work stays in your delivery tooling.
Can a ticket status change close a finding?
A state change can move a finding to remediation-complete where the mapping is configured, but closure still depends on verification. Ticket status is not proof of fix.
Do engineers see researcher details?
Only if the program allows it. Reporter identity can be withheld from engineering-facing tickets while remaining visible to the program owner.
What access does the integration need?
The minimum scopes required to create items and read state — not repository or project administration. Credentials are stored as secrets and are not returned by the API.

Connect the platform to your delivery stack.

We will map severity to priority, agree which state changes flow back, and test the integration on a single finding before enabling it across a live program.

Talk to usTriage and remediation