HashiCorp Boundary Target Session Exhaustion Sentinel
Audits HashiCorp Boundary targets for active session concurrency saturation and worker capacity limits.
Monitor HashiCorp Vault AppRole secret-id expiration with Kestra. Query accessor metadata, track GitHub rotation issues, and alert SecOps on Slack.
Modern cloud architectures use HashiCorp Vault's AppRole authentication engine to authenticate automated machine workloads, Kubernetes pods, and CI/CD runners. While role-id identifiers are static, secret-id tokens carry a finite time-to-live (TTL). When secret-ids expire unnoticed, automated services fail authentication, causing critical application downtime and broken deployment pipelines. This blueprint queries HashiCorp Vault's AppRole accessor metadata API daily, identifies secret-ids approaching expiration thresholds, logs a prioritized GitHub rotation ticket, and alerts SecOps teams via Slack.
daily_approle_hygiene_check (io.kestra.plugin.core.trigger.Schedule) initiates the audit daily at 08:00 UTC (shipped disabled for safe verification).probe_approle_secret_id (io.kestra.plugin.scripts.python.Script) interrogates the Vault REST API (POST /v1/auth/approle/role/{role}/secret-id-accessor/lookup) and inspects the remaining secret_id_ttl in seconds.branch_on_expiring_secret_id (io.kestra.plugin.core.flow.If) evaluates whether remaining hours are below the alert threshold (is_expiring == true):then: Automatically files a GitHub tracking issue via create_security_rotation_issue (io.kestra.plugin.github.issues.Create) and alerts the Slack channel via alert_secops_slack (io.kestra.plugin.slack.notifications.SlackIncomingWebhook).else: Emits an informational log entry (log_secret_id_healthy) confirming ample TTL remaining.log_audit_complete (io.kestra.plugin.core.log.Log) records the audit outcome.errors block alerts Slack if Vault tokens expire or the cluster endpoint is unreachable.Kestra coordinates external security API inspection, mathematical TTL conversion, conditional escalation, and chat alerting inside a unified, declarative pipeline. It injects Vault tokens securely, handles transient network retries, and maintains full execution audit logs without requiring custom scripts or cron daemons.
approle auth method enabled.read / update permissions on auth/approle/role/+/secret-id-accessor/lookup.VAULT_TOKEN: Authentication token for querying HashiCorp Vault.GITHUB_TOKEN: GitHub token used to open rotation issues.SLACK_WEBHOOK: Incoming Webhook URL for security alerts.vault_address (STRING, default https://vault.internal.company.com:8200): HashiCorp Vault cluster URL.role_name (STRING, default backend-api-production): Name of the audited Vault AppRole.secret_id_accessor (STRING, default a1b2c3d4-e5f6-7890-abcd-ef1234567890): Non-sensitive accessor ID corresponding to the target secret-id.ttl_hours_threshold (INT, default 72): Hours remaining threshold below which alerts are triggered.github_repository (STRING, default my-org/security-operations): Target GitHub repository for logging incident issues.outputs.probe_approle_secret_id.vars.role_name: AppRole name audited.outputs.probe_approle_secret_id.vars.hours_remaining: Calculated hours before secret-id expiration.outputs.probe_approle_secret_id.vars.is_expiring: Boolean indicating whether TTL breached threshold.VAULT_TOKEN, GITHUB_TOKEN, and SLACK_WEBHOOK in your Kestra namespace.vault_address, role_name, and secret_id_accessor to match a real AppRole credential.daily_approle_hygiene_check trigger for continuous credential hygiene monitoring.POST /v1/auth/approle/role/{role}/secret-id) gated behind operator approval.io.kestra.plugin.core.flow.Loop.