OpenControls Logo

STIG Viewer

STIGViewer Support

Kubernetes must remove old components after updated versions have been installed.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-242442CNTR-K8-002700SV-242442r961677_ruleCCI-002647medium
Description
Previous versions of Kubernetes components that are not removed after updates have been installed may be exploited by adversaries by allowing the vulnerabilities to still exist within the cluster. It is important for Kubernetes to remove old pods when newer pods are created using new images to always be at the desired security state.
STIGDate
Kubernetes Security Technical Implementation Guide2025-05-16

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (43) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

BCD-05Contingency Plan Root Cause Analysis (RCA) & Lessons Learned
1.00
CFG-02Secure Baseline Configurations
1.00
CPL-03Control Conformity Monitoring
1.00
CPL-03.2Functional Review Of Security, Compliance & Resilience Controls
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00

+33 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

SI-4System Monitoring
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.14.6
1.00
3.14.7
1.00
CCI1 mapping
CCI-002647
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (16) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.AE-02
1.00
DE.AE-03
1.00
DE.CM-01
1.00
DE.CM-06
1.00
DE.CM-09
1.00
ID.IM-01
1.00
ID.IM-02
1.00
ID.IM-03
1.00
ID.RA-01
1.00
PR.DS-01
1.00

+6 more (top 10 by confidence shown)

Who does this work

20 NICE work roles and 13 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-242442r961677_chk)

To view all pods and the images used to create the pods, from the Control Plane, run the following command: kubectl get pods --all-namespaces -o jsonpath="{..image}" | \ tr -s '[[:space:]]' '\n' | \ sort | \ uniq -c Review the images used for pods running within Kubernetes. If there are multiple versions of the same image, this is a finding.

Fix Text (F-45675r863906_fix)

Remove any old pods that are using older images. On the Control Plane, run the command: kubectl delete pod podname (Note: "podname" is the name of the pod to delete.)