iac_latest_tagIac Latest Tag — a PullGuard finding type. Findings of this type appear in the PR comment, Step Summary, SARIF (GitHub Security tab / IDE viewers), and the HTML report, each with severity, location, and the remediation guidance below.
# Bad: FROM node:latest
# Good: FROM node:20-alpine
# Best: FROM node:20-alpine@sha256:<digest>
The image is read from the Dockerfile as written. A FROM that names a build argument (FROM $BASE,
FROM ${BASE:-node:20}) is judged by the default of an ARG declared before the first
FROM, or by the inline fallback, and the finding names the argument it came from. An argument with no default is
reported as iac_latest_tag, because the tag is then whatever the build passes.
What a static scan cannot see: a value passed at build time (--build-arg BASE=node,
a CI variable, a compose args: entry) replaces the default, so a pinned default does not prove what a
pipeline builds. Pin the value where the build passes it as well.
Suppress a confirmed non-issue with a committed .pullguardignore
entry (pullguard ignore locally, or comment
/pullguard ignore <fingerprint> <reason> on the PR — the
fingerprint is printed in the PR comment’s Triage section). Entries support
expiresAt for time-boxed snoozes.
Security findings at major or critical severity — and any critical finding —
always surface: .pullguardignore cannot hide them. The reviewed
paths that keep them visible are acknowledged (reviewed, stays in reports)
and, for a confirmed false positive, a reasoned false_positive entry —
visible and audited, excluded only from the merge block.