Attestkeep
Sign up
Operations

A critical finding opens one issue, and the issue says how it ended.

Create an account Issue trackers
Critical finding image digest + CVE One issue GitHub GitLab Jira in your own tracker closed · fixed closed · triaged closed · image retired the reason is written on the issue
Only "fixed" counts as remediation in an evidence package.
What it does

Issue tracker sync

When a critical vulnerability appears in an image your cluster runs, Attestkeep opens one issue in GitHub, GitLab or Jira. A second scan, namespace or cluster adds itself to the same issue rather than opening another.

Open issues are re-checked every ten minutes and closed with a comment naming the reason: fixed, triaged, or image retired after a day unseen. Only fixed counts as remediation in a report. The token is encrypted at rest and never returned by the API.

How it works

Step by step.

  1. A critical finding appears

    On an image the cluster is running.

  2. One issue is opened

    Per image digest and CVE, up to 20 a day per channel by default.

  3. It is re-checked

    Every ten minutes.

  4. It is closed with the reason

    Fixed, triaged or image retired.

  5. The history is kept

    When it opened, when it closed, and why.

What it records

Each finding's opened and closed times let a report count critical findings fixed inside the declared window.

Issue trackers

23 clauses across 10 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