The container platform runtime must isolate security functions from non-security functions.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-233125SRG-APP-000233-CTR-000585SV-233125r961131_ruleCCI-001084medium
Description
The container platform runtime must be configured to isolate those services used for security functions from those used for non-security functions. This separation can be performed using environment variables, labels, network segregation, and kernel groups.
STIGDate
Container Platform Security Requirements Guide2025-09-10

Related Frameworks

4 paths across 3 frameworks
SCF2 mappings
END-16Restrict Access To Security Functions
0.50
  • DISA · V2R4 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • Secure Controls Framework · 2026.2 · scf_strm · related
SEA-04.1Security Function Isolation
0.50
  • DISA · V2R4 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • Secure Controls Framework · 2026.2 · scf_strm · related
NIST 800-531 mapping
SC-3
1.00
  • DISA · V2R4 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
CCI1 mapping
CCI-001084
1.00
  • DISA · V2R4 · disa_xccdf · related

Details

Check Text (C-233125r961131_chk)

Verify container platform runtime configuration settings to determine whether container services used for security functions are located in an isolated security function such as a separate environment variables, labels, network segregation, and kernel groups. If security-related functions are not separate, this is a finding.

Fix Text (F-36029r600863_fix)

Configure the container platform runtime to isolate security functions from non-security functions.