1. Images & Charts
  2. external-dns
external-dns

external-dns

Utils
Updated 2 days ago

Compliance

Understand the compliance standards and security best practices supported by this image.

NIST-800-190

NIST Compliance

100%
Passed

Scan Date

Jul 26, 2026

Image Tag

Latest

Checks

Analyzed
5
Passed
5
Failed
0

NIST-800-190 - Section 3.1 (Image Risks)

View NIST-800-190
Image vulnerabilities
NIST ID
3.1.1

Status
Passed

Notes
Minimus continuously rebuilds images with the latest patched components to support a smooth update process for containers. Vulnerability fixes are applied daily to deliver the most secure versions of each image.
Image configuration defects
NIST ID
3.1.2

Status
Passed

Notes
Minimus images are configured to comply with multiple industry standards. Minimus images undergo automated configuration checks as part of the build pipeline and the results are delivered in a dedicated compliance report per image. Minimus validates least-privilege user settings and other security configurations. Minimus images are also minimal and distroless to ensure that unnecessary packages are not installed in the container, further reducing potential configuration risks.
Embedded malware
NIST ID
3.1.3

Status
Passed

Notes
Minimus builds its images from MinimOS packages built directly from source and manages its own internal CI/CD pipelines to protect against embedded malware. The provenance of all image components are validated and verified according to SLSA L3 requirements.
Embedded clear text secrets
NIST ID
3.1.4

Status
Passed

Notes
Minimus images are built directly from source and include no secrets of any kind. No passwords, GitHub tokens, x.509 keys, or any other secrets are stored in Minimus images.
Use of untrusted images
NIST ID
3.1.5

Status
Passed

Notes
Minimus images and SBOM attestations are signed using the Sigstore toolchain and can be verified by Cosign to protect against the use of untrusted images.

Section 3.2 - 3.5 (Other Risks)

Additional checks

Sections 3.2 through 3.5 cover risks that are out of scope for the image level. They involve risks at the registry, orchestrator, host OS, and container runtime environment levels. Compliance must be configured and validated by operators in the deployed environment, registry, etc.


Status
Out of scope