Skip to content

Vulnerability Management

The standard behind the monthly vulnerability review: what counts as a finding we act on, what is deliberately set aside and why, who owns the decision, and how often it is re-read. This is the ISO 27001 A.8.8 artefact. The Amazon Inspector suppression rules in infra/modules/security/inspector are its implementation; if the two disagree, this page is wrong or the code is, and one of them gets a pull request.

Scope

Amazon Inspector scans every EC2 host and every ECR image in both AWS accounts (prod and stage, eu-central-1 and eu-west-1), plus Lambda functions in prod eu-central-1. Findings flow into Security Hub and from there into Sprinto, which is the compliance record. Dependabot covers application dependencies in GitHub and is reviewed on the same monthly cadence but is not governed by the criteria below.

Owner

The Infrastructure & Security lead (Ástþór Pétursson) owns the criteria, the risk acceptance recorded in VM-05 and the quarterly re-read. Changes to a criterion are a pull request to infra that changes the corresponding filter; the description on the filter is the criterion text an auditor sees in the AWS console.

The criteria

A finding is suppressed, and leaves the Sprinto count, when it matches one of these. Suppression is a filter on the finding, not a dismissal: every rule releases the finding back to active automatically when its condition stops holding.

Rule Criterion Why it is not actionable Releases when
VM-01 ECR image with no running task or container (ecrImageInUseCount = 0) Nothing runs the image; there is nothing to remediate. Superseded images stay under scan for 14 days after last pull. The image is pulled again
VM-02 No fixed package version published by the vendor (fixAvailable = NO) There is no action to take. Accepted pending a vendor fix. A fix ships
VM-03 Severity LOW or INFORMATIONAL Below the remediation threshold; addressed by the normal patch cycle rather than tracked individually. The vendor re-scores it higher
VM-04 Severity UNTRIAGED (no vendor score yet) Cannot be prioritised until scored. A severity is assigned
VM-05 Severity MEDIUM with no publicly known exploit (exploitAvailable = NO) Risk accepted by the owner on 18 September 2026: remediated through the normal patch cycle rather than tracked one by one. An exploit is published

One carve-out. VM-01 excludes the vault-ingest repository. It is pushed as a multi-arch OCI index; ECS reports the index digest while Inspector scans the child manifest, so the in-use count reads 0 for an image that is running and VM-01 would hide real findings. The exclusion is removed when vault-ingest becomes a single-manifest build (IS-85).

The working set

What remains after the criteria is what the monthly review acts on: findings that are critical or high, have a vendor fix, sit on an in-use resource, and are older than the per-severity remediation SLA. Steady state means that set is empty. It does not mean zero findings: a host with a kernel shows two to three hundred high findings for the fortnight after each kernel release, and that is inside SLA and expected.

Remediation SLA and cadence

  • Per-severity remediation SLA: defined by IS-16 (27 August 2026) and recorded on the recurring Sprinto vulnerability review issue in Linear, which is the live definition. It is deliberately not copied here.
  • Monthly review: the recurring Linear issue. Closing it each month is the ISO evidence of periodic review; its Inspector section is a read of the working set, not a triage.
  • How things get fixed: ECS node replacement onto the current AMI (IS-82, fortnightly), scheduled image rebuilds and redeploys (IS-85), ClickHouse host patching as the review's monthly item, and per-image dependency bumps for anything left.
  • Quarterly re-read: in the January, April, July and October reviews, re-read this page and the five filters and record on the review issue that they still describe what we mean. "Review quarterly" is written into every filter description for this reason.

Where it is implemented

Where What
infra/modules/security/inspector Enabler, ECR enhanced scanning, and the five filters VM-01..VM-05
infra/environments/prod/eu-central-1/inspector.tf Module call with the vault-ingest carve-out, plus four older prod-only network-reachability and go/stdlib filters
infra/environments/prod/eu-west-1, stage/* Module call, same five criteria
Sprinto Reads Inspector through Security Hub with the SecurityAudit role; suppressed findings leave ACTIVE and drop out of the count

History

Date Change
2026-09-18 VM-01..VM-05 created in the prod console (IS-11). Active findings 2,402 → 868.
2026-09-18 VM-01 vault-ingest carve-out added after it hid 138 findings on a running image.
2026-09-30 Filters imported into Terraform unchanged; Inspector enabled with the same criteria in prod eu-west-1 and both stage regions (IS-86, IS-112).