Skip to content
Integrations

One scanner.
Every system
of record.

Forward HarborGuard's container vulnerability findings into the tools your security, compliance, and engineering teams already use — on a continuous schedule, with credentials encrypted at rest and zero per-scan plumbing.

2 live 12+ on roadmap
HarborGuardharborguard
Vanta
Live

Vanta

GitHub Code Scanning
Live

GitHub Code Scanning

Slack

Slack

PagerDuty

PagerDuty

Jira

Jira

Datadog

Datadog

Snyk

Snyk

Sentry

Sentry

Opsgenie

Opsgenie

GitLab

GitLab

Live now

Shipped and syncing.

Two integrations are live in production today. Both run on the same 15-minute state-of-world replace pattern, so the operational shape — credentials, audit events, failure handling — is identical across providers.

Compliance evidence, continuously synced

Vanta

Vanta logo

Push HarborGuard's open vulnerability findings into a Vanta Private API source. State-of-world replace every 15 minutes — remediated findings disappear automatically, no manual reconciliation.

  • Private API token + integration/source ID
  • 15-minute sweep, state-of-world replace per source
  • Failures fire integration_sync_failed notifications
  • Pause without disconnecting (Enabled toggle)

Findings inside the GitHub Security tab

GitHub Code Scanning

GitHub Code Scanning logo

Upload per-image SARIF analyses to a repository's Security → Code scanning tab. Each image gets its own SARIF category, so multiple images can share a repo without overwriting each other.

  • Classic PAT, fine-grained PAT, or GitHub App token
  • GitHub Enterprise Server supported (https only)
  • Up to 100 image → (repo, ref) mappings per org
  • Orphan cleanup closes alerts when mappings are removed
How it works

Every integration, the same shape.

Pull, not push

A single cron worker walks every org every 15 minutes and pushes the complete current state. No per-scan webhooks to wire up; a missed run self-heals on the next sweep.

State-of-world replace

Each sync uploads the full set of findings scoped to the integration. Anything no longer present is removed on the target side — there's no append/delete drift to reconcile.

Credentials encrypted at rest

Tokens are AES-256-GCM envelope-encrypted before they touch Postgres and are never returned to the browser. The settings UI only ever shows the last four characters.

Pluggable framework

Each provider lives in src/lib/integrations/<provider>/ with five files: adapter, HTTP client, Zod schema, mappers, and a React config card. New providers ship in the same shape.

Roadmap

What we're building next.

The integrations framework is pluggable — each provider is a five-file folder. These are queued up next. If one is blocking your team, let your account contact know and we'll prioritize.

Slack logo

Slack

Native channel-aware alerting beyond webhooks

Planned
PagerDuty logo

PagerDuty

Service-aware incidents with auto-resolve

Planned
Jira logo

Jira

Per-finding tickets with SLA fields

Planned
Datadog logo

Datadog

Vulnerability metrics + dashboards

Planned
Snyk logo

Snyk

Cross-import for app-layer projects

Planned
Sentry logo

Sentry

Release health correlated with CVEs

Planned
AWS logo

AWS

Security Hub finding ingest

Planned
Azure logo

Azure

Defender for Cloud sync

Planned
Google Cloud logo

Google Cloud

Security Command Center sync

Planned
GitLab logo

GitLab

Container scanning report uploads

Planned
Opsgenie logo

Opsgenie

On-call routing for SLA breaches

Planned
Okta logo

Okta

SCIM + automated role provisioning

Planned
Get started

Connect an integration in under five minutes.

Generate a token in the destination tool, paste it into HarborGuard, hit save. The first sync runs within the next sweep — or trigger it on demand.