opentelemetry
Warn
Audited by Socket on Sep 18, 2026
1 alert found:
AnomalyAnomalyexamples/values-daemonset.yaml
LOWAnomalyLOW
examples/values-daemonset.yaml
No malicious behavior is evident in this declarative OpenTelemetry Collector configuration. The principal risks are unauthenticated host-exposed OTLP endpoints, unencrypted HTTP export to Prometheus and Loki, potentially excessive nodes/proxy RBAC access, and propagation of all pod labels into telemetry. Restrict receiver access with network policies and authentication, use TLS for exporters, minimize RBAC permissions, and verify that the logsCollection preset supplies the referenced filelog receiver.
Confidence: 97%Severity: 62%
Audit Metadata