Skip to main content
When a scanner finds a vulnerability in an image your own application builds, and a fixed version of the package exists, Ankra can open the fix for you: one pull request per repository that moves the Dockerfile base image to the fixed version. This guide takes one finding from the list to a rescan that proves it is gone. When there is no fix, it ends with recording a decision instead. You end up with a merged pull request, a rebuilt image, and the finding under Resolved in Security → Vulnerabilities.

Before you start

  • A scanner on the cluster that runs the image. A cluster with no report is not counted anywhere. See Turn on scanning.
  • The security.manage permission to open fix pull requests or accept a risk; built-in admins and owners have it. Without it the button stays disabled and the page says “A security manager can start a remediation.” See Roles and access.
  • An application in Ankra that builds the image, with its repository and a GitHub credential set. Ankra writes through that application’s own credential. An image no application of yours builds (an add-on’s, or a third-party image in a manifest) cannot get a pull request: see What can go wrong.
  • A Dockerfile whose FROM line pins the version the scanner found. Ankra changes only FROM lines.

Fix the finding

1

Find the finding

Open Security → Vulnerabilities. The list opens on Open issues, with the ones used by attackers first. Narrow it with All clusters, the severity choice and A fix is published under the next-step choice, or search by issue, package or title.Select the issue’s title. Its page opens with the CVE and package above the title, its severity, and Read the advisory.
2

Read the fix Ankra offers

The first card on the issue’s page says what can be done:How an issue like this gets fixed, further down, lists every route and any pull requests Ankra already opened, under Pull requests opened by Ankra.
3

Open the pull request

On a card that reads A fix is published and is in no plan yet., select Open or reuse fix pull requests. The button reads Starting… while Ankra works, and a row appears for each repository with the status Fix in progress.From a fix plan instead, Review the fix plan opens the review: The exact change shows the FROM lines it changes, and Rollout and proof shows the risk and how the fix is verified. Select Open 1 pull request (or Open n pull requests for several repositories).Each pull request is on a new branch whose name starts with ankra/security/. Only FROM lines change, and the repository’s own CI runs on it. Where an Ankra pull request for the same finding and repository is already open, Ankra reuses it.
4

Merge it

Select Review the fix pull request to open it on GitHub. Review and merge it as you would any change.Ankra merges it for you only when the application’s Keep it safe setting is Ankra runs it, and only once its checks and its Ankra AI review pass.
5

Follow it in Fix activity

Open Security → Fix activity. Every fix someone started is listed under Needs you, In progress or Earlier, each with its one status word:Open What happened on a row to read every step Ankra recorded: the pull request it opened or reused, the pipeline run it started, and each rescan check with how many affected clusters were rescanned and how many occurrences are still active. Open the pipeline run opens the build in the application.

Verify

  1. In Security → Fix activity, the fix reads Fixed, and its row says Rescan verified with the time.
  2. In Security → Vulnerabilities, select Resolved. The issue is listed there, and its page says “Resolved. No cluster’s newest scan finds it any more: it was fixed, or its workload is gone.”
From the CLI, ankra security remediations get <run-id> shows the status verified.

Accept the risk when there is no fix

When no fixed version is published, or the issue does not affect you, record a decision so your team knows it was looked at.
1

Choose the decision

On the issue’s page, select Accept the risk to take it off the open count until a review date, or Acknowledge to record that your team has seen it while it stays open and counted. Where a fix exists, both are under Not fixing it now?
2

Say what it covers and why

Under What this decision covers, choose the scope: the add-on on every cluster, everything in one namespace, one workload, or one exact image. For your own application the namespace is usually right, because it survives every deploy and rebuild. Write the Reason, and for an accepted risk pick the Review date: from tomorrow, and never more than a year out.An issue used by attackers warns: “Attackers use this issue somewhere. Accepting takes it off the open count without fixing it.”
3

Save it

Select Accept the risk (or Acknowledge). The issue’s page now reads Risk accepted with what it covers, and the issue moves to the Accepted tab in Security → Vulnerabilities.
An accepted risk comes back for review on its date. Security → Accepted risks lists it under Needs review as the date approaches; keeping it needs a new reason, and Reopen for fixing puts it back on the open count.

What can go wrong

The issue’s page and ankra security finding rebuild-plan give the reason per image, the CLI in slightly different words. The ones you are most likely to meet, as the portal words them: A fix that ends Your turn or used up its attempts says what to do on its row: “Review the fix pull request and the last pipeline failure. Correct the change or build issue before starting another attempt.” An Uncertain fix says “Check the deployed image and restore scan coverage before declaring this fix complete.”, with Check rescan coverage.

Where to go next

Cluster security

Every Security view, fix kind and decision explained.

Get started with Ankra CI

The pipeline that builds and scans the rebuilt image.