Connect code.
Deliver findings.

Test with GitHub context. Send findings to Slack and Jira. Automate through CI and the API.

Open AISEC
Selected GitHub repositories
  • Routes
  • Dependency manifests
  • Package versions
Linked AISEC projectContext alongside discovered assets

Find what browsing misses.

Read routes and dependency versions from selected GitHub repositories.

Connect
Select repositories in GitHub, then link one to your AISEC project.
Verify
Check the analyzed commit and sync state in Perimeter.

Put findings where
your team works.

Owners and Admins connect channels in the team’s Integrations screen.

Slack

Critical and High alerts.

One alert after a completed pentest with Critical or High findings.

Choose a channel.

Send a test message to confirm delivery.

Jira

Findings become tickets.

One ticket per confirmed Critical or High issue, linked to AISEC evidence.

Select a project and issue type.

The connection test creates and closes a ticket. Check any cleanup notice.

Does Jira Done verify a fix?

No. Where Done monitoring is enabled, AISEC retests the issue before resolving it.

Make it part of your pipeline.

CI webhooks

GitHubGitLabBitbucket

Queue discovery from push and pull-request events. Webhooks do not import code or launch a full pentest on every commit.

Project → Integrations

CLI & CI jobs

PythonNode.js

Start scans and check results from your pipeline. The Node.js CLI supports a severity threshold for the job result.

REST API

Custom automation

Connect project and scan data to your own tools.

Cloudflare for Sentinel

Block reviewed hostile sources at the edge.

Explore Sentinel

Connect your tools.

Integration availability depends on your plan.

Open AISECCompare plans Access and data controls