Pages
Integrations v9Integrations — Ideas v9
Source: qdash /integrations - c61 scalable capability cards, 2026-08-13
Separate sources that enrich qdash from four outbound capabilities, then reveal the complete destination category only when the operator asks for it.
Integrations
Connect context into qdash and route findings to the systems your team already uses.
1 source · 0 destinations
Sources & enrichment
Bring event, identity, and ownership context into qdash.
qcontrol stream
Local events · connected on loopback
Okta
Match observed agents and users to Okta identities.
Microsoft Entra ID
Match observed agents and users to Entra identities.
Sources add context to qdash; destination capabilities move selected data out.Nothing leaves until a destination is enabled.
Available capabilities
Common destinations are shown first.
Security monitoring
6Send qdash activity to SIEM and observability tools for investigation.
Splunk
Send findings and agent events to Splunk.
Microsoft Sentinel
Send findings and agent events to Microsoft Sentinel.
Notifications & response
5Alert teams or open incidents where people already respond.
Slack
Post selected findings to a Slack channel.
PagerDuty
Open PagerDuty incidents for urgent findings.
Remediation tracking
5Turn findings into owned, trackable work for remediation.
Jira
Create Jira issues with evidence and owner context.
Linear
Create Linear issues with evidence and owner context.
Evidence & compliance
5Retain evidence for audit, analysis, and reporting.
Amazon S3
Archive evidence and findings in Amazon S3.
Google Cloud Storage
Archive evidence and findings in Google Cloud Storage.
Direction stays explicit
Sources enrich qdash; destination capabilities move selected data out.
Four outcomes stay stable
The overview does not change as each destination catalog grows.
View all carries the long tail
Search and comparison appear only when the operator asks for breadth.