Skip to content

security(coredns): disposition the required DNS bind capability #3061

Description

@devantler

🤖 Generated by the Agentic Engineer

Outcome

Disposition the three scanner findings caused by CoreDNS binding the required DNS service port without weakening the rest of the repository scan.

Parent

First control-family slice of #2787.

Current evidence

  • Checkov reports CKV_K8S_25 once on the Docker CoreDNS Deployment.
  • Trivy reports KSV-0022 and KSV-0117 once each on the same Deployment.
  • The pinned distroless CoreDNS image runs as UID/GID 65532 and its binary carries the file capability needed for port 53; the container needs only NET_BIND_SERVICE in its bounding set and drops all other capabilities.

Acceptance criteria

  • Add a resource-scoped Checkov disposition for CKV_K8S_25 with the verified port-53 reason.
  • Add path-scoped Trivy dispositions for KSV-0022 and KSV-0117 on only the CoreDNS Deployment.
  • Keep the same checks active for every other repository path.
  • Reproduce the CI-equivalent counts: Checkov 9 to 8 and Trivy 110 to 108.
  • Both local and production workload validations remain green.

Out of scope

CPU limit, trusted-registry, and other remaining CoreDNS findings stay in #2787 for separate disposition or remediation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status
    👀 In Review

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions