Schedule icon
Webhook icon
Request icon
Script icon
If icon
SlackIncomingWebhook icon
Log icon

GitHub Dependabot Vulnerability SLA Escalation Sentinel

Track GitHub Dependabot alerts against security SLA deadlines and escalate overdue vulnerabilities to Slack.

Categories
BusinessInfrastructure

Unpatched dependencies represent a major attack vector in modern applications. While Dependabot detects vulnerable libraries, security compliance frameworks (such as SOC 2, FedRAMP, and ISO 27001) require strict remediation service-level agreements (SLAs) based on vulnerability severity.

This blueprint automatically audits open Dependabot alerts for any GitHub repository, calculates vulnerability age against configured SLA thresholds (e.g., 7 days for Critical, 14 days for High, 30 days for Medium), and escalates overdue CVEs directly to your SecOps or engineering team via Slack.

How it works

  1. fetch_dependabot_alerts queries the GitHub REST API for open Dependabot alerts.
  2. audit_sla_breaches runs an automated Python script that computes alert age, compares against severity SLAs, aggregates severity metrics, and compiles a remediation digest.
  3. evaluate_sla_breaches uses an If condition to check whether any alerts breached the configured SLA window.
  4. If breaches exist, alert_security_slack sends a structured Slack notification with direct links to the affected alerts for rapid triage.
  5. If all alerts are within SLA, log_sla_compliant logs clean compliance telemetry.
  6. The errors block alerts Slack if token authorization or network connectivity fails.
  7. Scheduled triggers run the audit automatically on weekdays, while a Webhook trigger enables on-demand audits.

Prerequisites

  • A GitHub Personal Access Token or fine-grained token with security_events (read) or repo permission.
  • A Slack Incoming Webhook URL for alerting.

Secrets

  • GITHUB_TOKEN: GitHub token used to authenticate against the Dependabot alerts API.
  • SLACK_WEBHOOK_URL: Slack Incoming Webhook URL to receive SLA escalation and failure alerts.

Quick start

  1. Add GITHUB_TOKEN and SLACK_WEBHOOK_URL to your Kestra namespace secrets.
  2. Adjust repository to your target repository (e.g. your-org/your-repo).
  3. (Optional) Customize the SLA days for critical, high, medium, and low severities.
  4. Run the workflow manually to inspect the audit_summary output.
  5. Keep the weekday schedule active to maintain ongoing security compliance.

How to extend

  • Add automatic GitHub issue creation or assignment for teams when an SLA is breached.
  • Integrate with Jira or PagerDuty to page on-call engineers for critical SLA violations.
  • Export vulnerability SLA metrics to ClickHouse, BigQuery, or PostgreSQL for compliance dashboards.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.