Daily Docker Hub security digest for your Slack channel
Every morning we scan your Docker Hub activity for risky changes and post a plain-English alert to Slack, staying quiet when nothing needs your attention.
Every morning at 8am, review my Docker Hub audit log and alert my team in Slack about anything security-sensitive. Run this on a daily cron schedule, and only speak up when something noteworthy actually happened.
Pull recent activity with Docker Hub's List Audit Log Events for my namespace or organization. Look only at events from the last 24 hours by filtering on each event's timestamp, so we do not re-report older activity from previous runs.
Use judgement to separate high-signal actions from routine noise. Always flag: a new personal access token being created, a member being added or removed, a repository being deleted, and a repository being switched from private to public. Leave out everyday activity such as ordinary image pushes and pulls unless something looks clearly unusual.
For each flagged event, capture what happened, who did it (the actor), and when it happened. Group related events together and keep the write-up short and scannable.
If there is at least one noteworthy event, post a digest to a Slack channel such as #security using Send a Message, sending it as the workspace bot so the alert is not tied to one person's account. Use Slack mrkdwn formatting with a clear headline and one line per event covering the action, the actor, and the time. If nothing noteworthy happened, do not post anything at all, so any message in the channel always means something worth looking at.
Additional information
What does this prompt do?
- Reviews your Docker Hub account or organization activity every morning for the past day's changes.
- Flags security-sensitive actions like a new access token, a member added or removed, a deleted repository, or a repository switched to public.
- Posts a short summary to your Slack channel with what happened, who did it, and when.
- Stays silent on quiet days, so every alert that lands is worth a look.
What do I need to use this?
- A Docker Hub account or organization you can create an access token for.
- A Slack workspace and a channel for the alerts, such as #security.
How can I customize it?
- Change the time it runs or how often, for example twice a day instead of once each morning.
- Pick which Slack channel or team receives the alerts.
- Adjust which actions count as sensitive enough to flag.
Frequently asked questions
What kinds of Docker Hub changes will it flag?
Will I get a message every single day?
Does this work for a personal account or only an organization?
Which Slack channel do the alerts go to?
How far back does each check look?
Related templates
Catch risky Docker Hub changes before they bite.
Put your container registry on autopilot with a daily security check that only speaks up when it matters.