Integrations
Connect Sectora to your source control, ticket tracker, CI, cloud accounts, AI providers, and notification channels. Org-scoped — set once, every team member benefits.
Source control
For SAST / SCA / Secrets scans. Settings → Integrations → Connect. We use OAuth where possible — gets the narrowest scopes (read repo content + write PR comments + check runs). GitHub App install is also available for orgs that prefer App-based access.
Ticket trackers
Auto-create tickets from findings + bi-directional status sync. Closing the ticket in Linear marks the finding resolved in Sectora; verify-fix re-opens the ticket if it returns Still-exploitable.
Notification channels
See Alerts for the routing-rule logic.
Cloud accounts (for ASM)
Read-only. Used by ASM to discover your public surface. We never write to your cloud account — the IAM role/scope is locked to read-only resource enumeration.
AI providers (BYO key)
For AI Smart Triage on your scans. The bundled Gemini fallback ships with the trial; bring your own key once you outgrow the included quota or want different model preferences. See AI Integrations.
SSO / Identity Providers
Enterprise plan. See Authentication.
SIEM / Observability
Stream audit log + Shield decision log + finding events into your SIEM. Real-time push or 5-minute batched.
Disconnecting
Settings → Integrations → Disconnect on any integration. Sectora deletes the access token immediately and stops polling within 30 seconds. Existing findings + scan data stay; they just don't update further.
What's next
- Authentication — API keys for automating what integrations don't cover.
- Alerts — wire integrations into notification rules.