Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Logging Operator
Cyber Security

Logging Operator

← Back to Glossary
By NHI Mgmt Group Updated November 19, 2026 Domain: Cyber Security

A Kubernetes controller that defines and manages log pipelines through custom resources. It coordinates collection, filtering, aggregation, and forwarding so teams can route workload logs to one or more destinations with consistent policy. In practice, it reduces manual wiring and gives platform teams a repeatable way to operate cluster logging.

What a logging operator does

A logging operator is a Kubernetes controller that manages log pipelines through custom resources. It gives platform teams a repeatable way to define how logs are collected, filtered, aggregated, and forwarded, instead of wiring those paths by hand across each cluster or workload.

That controller pattern matters because logging in Kubernetes is rarely a single hop. Logs often need enrichment, routing, buffering, and destination-specific handling, and those behaviours must stay consistent as namespaces, clusters, and applications change.

Why Kubernetes logging needs an operator pattern

The operator model turns logging into declarative infrastructure. Teams express the desired pipeline state in custom resources, and the controller reconciles the cluster toward that state. This reduces drift, supports standard policy, and makes logging easier to operate across many workloads and environments.

It also fits the way Kubernetes platforms are usually run. When cluster operators need to change log destinations, add filters, or standardise collection rules, they can update the resource definition rather than reconfiguring each node or application individually.

How log pipelines are usually structured

A logging operator typically sits above the underlying collectors and forwarders. It may manage inputs from containers or nodes, apply parsing or filtering rules, aggregate streams, and send output to storage, search, or observability platforms.

Because the operator defines policy as code, it becomes the control point for log routing decisions. That makes it useful for separating platform-level defaults from application-specific requirements, while still preserving a common operating model across the cluster.

What makes this control useful in practice

For platform teams, the key benefit is consistency. A well-managed logging operator helps ensure that logs are not silently dropped, duplicated, or sent to the wrong destination when teams deploy new services or alter cluster layout.

It also improves operational transparency. With one reconciled definition for the pipeline, teams can reason about where logs go, which filters apply, and which parts of the stack own collection versus forwarding.

Risk and Threat Considerations

Logging operators reduce configuration sprawl, but they also centralise a sensitive control plane. If the pipeline definition is wrong, logs can be lost, over-collected, or routed to a destination that weakens confidentiality or incident visibility.

Failure mechanism: Misconfiguration, excessive privilege on the operator, or broken pipeline logic can suppress security-relevant events, expose sensitive log content, or create blind spots during investigation.

Impact: Teams may miss detection signals, lose audit evidence, or leak secrets and personal data that were never meant to leave the cluster.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-8 — Audit Log ManagementLogging operators define how audit and event logs are collected and routed.
Recommendation — Centralise log collection and review to preserve audit coverage across clusters.
NIST SP 800-53 Rev 5AU-2 — Audit EventsThe operator determines which events are captured and forwarded for auditing.
AU-6 — Audit Record Review, Analysis, and ReportingReliable forwarding and filtering support usable log review and analysis.
CM-6 — Configuration SettingsThe operator enforces declarative pipeline configuration across the cluster.
Recommendation — Define required audit events and ensure the operator preserves them end to end. Route logs so analysts can review and correlate security events consistently. Manage logging pipeline settings as controlled configuration and review changes.
ISO/IEC 27001:2022A.8.15 — LoggingLogging operators implement and standardise logging controls in infrastructure.
Recommendation — Specify logging requirements and keep operator-managed pipelines aligned to them.

Practitioner Guidance

What to watch for: Treat the operator as part of the cluster's security control surface, not just an observability convenience. Changes to custom resources should be reviewed with the same care as other policy-bearing infrastructure, especially when they alter filtering, forwarding, or retention behaviour.

Governance implication: Ownership should be explicit, because the operator often determines which logs exist for security review and which systems receive them. The logging design should be validated against the operational need for integrity, retention, and access control, not only against delivery success.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org