Integrations overview

Integrations send TrekShield events or tickets to your tools. Platform Administrators configure them once per organization in Settings, Integrations; Engagement Managers can use the API. Client roles cannot.

Integration	Status	What it does
Webhooks	Available through the API	Signed JSON events to your HTTPS endpoint (webhooks)
Slack	Available	Posts state changes and alerts to a channel
Jira	Available	Creates an issue when a finding is triaged
ServiceNow	Available	Creates an incident when a finding is triaged
GitHub	Coming soon	Shown in Settings as Coming Soon

One destination per organization

Each integration has one organization-wide destination. If an organization contains more than one client, TrekShield refuses to create Jira or ServiceNow tickets, so one client’s findings never reach a tracker shared with another. Per-client destinations do not exist yet; Slack and webhooks are organization-wide.

Outbound calls use HTTPS only and refuse private network addresses. Saved secrets are encrypted and never shown again. Jira and Slack have a Test button.

Slack

Create an incoming webhook in Slack and paste its URL, which must start with https://hooks.slack.com/services/. The channel field is only a label. Messages cover engagement, finding, remediation and retest state changes (name, old and new state, severity, actor, link) plus SLA-breach and stale-engagement alerts. Finding titles appear in the channel, so use a private one.

Jira

Enter your Jira Cloud base URL, a default project key (2 to 10 uppercase letters or digits), your Jira email and an API token. When a finding is triaged, TrekShield creates an issue titled [TrekShield] <finding title> with severity, CVSS score, engagement, description and finding ID. Priority follows severity, from Highest for Critical down to Lowest for Info. Issues carry the labels trekshield and severity-<level>, and the link is saved on the finding. The flow is one-way: Jira changes do not update TrekShield.

ServiceNow

Enter the instance URL, a username and password. A triaged finding creates an incident with short description [TrekShield] <finding title>, category Security and subcategory Vulnerability. Urgency and impact are 1 for critical, 2 for high and 3 for medium, low and info. Administrators can also create an incident for one finding through the API.

Tickets are created automatically at triage, before the engagement is delivered.