Attestkeep
Sign up
Operations

Events reach the channel where people look.

Create an account Configuration
Event admission blocked, critical finding, … Slack Microsoft Teams E-mail, via your SMTP Webhook, JSON POST
Each channel subscribes to the events it wants. Messages name the cluster, never its topology.
What it does

Notifications

A channel is Slack, Microsoft Teams, e-mail through your own SMTP server, or a webhook that receives a JSON POST. Each channel subscribes to the events it wants, and a test message checks it before you rely on it.

Events include a blocked admission, a new critical finding, break-glass enabled, an unverified workload, a remediation window breached, triage expiring, usage at 80% and 100%, a failed scan or database update, a package ready, an update available and a licence expiring. Messages name the cluster, never its topology.

How it works

Step by step.

  1. An event is raised

    By admission, the scanner or the console.

  2. Subscribed channels are picked

    Each channel chooses its events.

  3. The message is sent

    To Slack, Teams, e-mail or your webhook.

  4. A test checks a channel

    Before you rely on it.

What it records

Whether a refusal or a critical finding reaches a person is what the report's incident-response statement looks at.

Configuration

10 clauses across 7 frameworks cite at least one of these statements.

Install it yourself.

Create an account, confirm your e-mail with the code we send, take the free Community key from the Licenses page, and install with Helm.

Create an account