Integrations
Configure AYAsec integrations for Slack, Jira, Linear, GitHub, API tokens, and MCP-based security workflows.
AYAsec plugs into the tools your team already works in. Post scan results and grade-regression alerts to Slack, open and resolve Jira and Linear issues with true two-way sync, fan out notifications to your own destinations, and connect GitHub or GitLab so your repositories sit alongside your scanned domains.
Connecting an app
Slack, Jira, and Linear, where enabled for your account, connect the same way: open Settings → Connected Apps , pick the workspace you want to wire up, and click Connect on its row. You authorize AYAsec in the provider's own OAuth screen and land back on the page connected. Every connection is scoped to a single workspace, so if you run a workspace per client or business unit, each one points at its own Slack team, Jira site, or Linear workspace, and notifications and tickets never cross a workspace boundary. Connecting an app and editing its routing is a workspace-admin action.
Slack
Send completed scans and grade-regression alerts to any number of Slack channels, formatted as native Block Kit messages: a headline, the grade and score, the size of the drop, and a View report button that deep-links straight into AYAsec, not a wall of plain text.
Add as many channel routes as you like and give each its own subscription. A route can carry completed scans, alerts, or both:
- Completed scans - a grade and score for every scan that finishes, with the scan type and a link to its report.
- Alerts - a grade regression on one of your targets, showing the before and after grade and the score delta.
For alerts, set a minimum severity per channel, so a leadership channel only hears about critical regressions while your team's working channel sees everything. (Completed-scan messages aren't filtered by severity - a finished scan has a grade, not a severity.)
Every route has a Send test message button and shows its own live delivery health - when it last delivered, or a count of failed deliveries if Slack has started rejecting posts - so a channel the bot was removed from is obvious at a glance. Flip a route off to pause it without losing its configuration. Public and private channels both work; invite the AYAsec bot to a private channel before routing to it.
Jira
The Jira integration is genuinely two-way. Most tools only push a notification into your tracker; AYAsec opens real Jira issues and keeps their status and your AYAsec alerts in lock-step, in both directions.
Point a workspace at a single Jira Cloud project and issue type , add any labels you want on the issues AYAsec files (they default to ayasec ), and choose which regression severities should open a ticket automatically. Leave the severities empty to keep it manual-only. Issues are created two ways:
- Automatically - when a grade regression matches a severity you selected, the ticket is filed the moment the alert opens.
- On demand - use Create Jira issue on any alert to file it yourself.
Either way the issue is written in Atlassian Document Format - proper Jira rich text with a summary, a bulleted grade-and-score breakdown, a priority mapped from the regression's severity, and a link back to the full report, not a raw dump. From there the two systems stay in sync:
- Resolve in AYAsec (by hand, or automatically when the target's grade recovers) and the linked Jira issue moves to a Done status with an explanatory comment. AYAsec reads your project's own workflow to find that transition, so it fits custom Jira workflows rather than assuming a fixed one.
- Close the issue in Jira and the matching AYAsec alert resolves itself.
Linear
Like Jira, Linear is a two-way integration: AYAsec opens issues and tracks them back to resolution. It also brings a security edge - Linear signs every webhook it sends, so the status updates AYAsec acts on are cryptographically verified, not trusted on faith.
Point a workspace at a single Linear team , optionally pick default labels, and choose which regression severities open an issue automatically - or leave it manual-only and use Create Linear issue on an alert. Issues are filed with a Markdown description (the same grade-and-score breakdown and report link) and a priority set from the regression's severity.
When you complete the linked issue in Linear, AYAsec resolves the matching alert on its own, so closing the work in your tracker closes the loop in AYAsec automatically.
GitHub
Install the AYAsec GitHub App from Settings → Connected Apps to grant access to specific repositories in your GitHub organization. AYAsec keeps its record of those repositories in sync with what the installation is granted access to, so they show up alongside your scanned domains without a manual import step.
API tokens
Settings → API Access lets you generate personal tokens and service keys, scoped to the actions they're allowed to perform (read-only scan access, target management, webhook management, and so on). See Authentication for the token model - programmatic API coverage is actively expanding, so check that page for what's currently supported before building against it.
Notification destinations
A destination is a named notification target - an e-mail address (or several, comma-separated), a webhook URL, or both. Create one under Settings → Notifications , then select it for scan alerts, digests, or schedules.
Scheduled tasks
Schedules run on a cron-style interval and can trigger a scan, a batch of scans, a report digest, a certificate-expiry check, or a score-regression check - each routed to a destination. A score-regression schedule is what powers the alert banner you see on a report when a scan comes back worse than the previous run for that target.