STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Mirantis Kubernetes Engine Security Technical Implementation Guide

V-260914

CAT II (Medium)

Audit logging must be enabled on MKE.

Rule ID

SV-260914r966099_rule

STIG

Mirantis Kubernetes Engine Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-001464CCI-000018CCI-001403CCI-001404CCI-001405CCI-000169CCI-000172CCI-000135CCI-002234

Discussion

Enabling audit logging on MKE enhances security, supports compliance efforts, provides user accountability, and offers valuable insights for incident response and operational management. It is an essential component of maintaining a secure, compliant, and well-managed Kubernetes environment. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.

Check Content

Check auditing configuration level for MKE nodes and controller:

Log in to the MKE web UI and navigate to admin >> Admin Settings >> Logs & Audit Logs.

If "AUDIT LOG LEVEL" is not set to "Request", this is a finding.

If "DEBUG LEVEL" is set to "ERROR", this is a finding.

Fix Text

Log in to the MKE web UI and navigate to admin >> Admin Settings >> Logs & Audit Logs.

In the "Configure Audit Log Level" section, select "Request"

In the "Configure Global Log Level" section, select "INFO" or "DEBUG". 
Note: The recommended setting is "INFO".

Click "Save".