Compliance monitoring · Live now · Open source

elf-owl.
Kubernetes, continuously observed.

Read-only, push-only compliance agent with eBPF runtime security monitoring for CIS Kubernetes v1.8 detection. Kernel-native visibility, zero enforcement, signed and encrypted evidence.

46
Automated CIS controls
9
Manual references
0
Enforcement surface
AES-256
Evidence encryption
What is elf-owl?

Minimal observer. Maximum evidence.

elf-owl is a minimal compliance observer that detects CIS Kubernetes v1.8 violations using cilium/ebpf kernel monitoring. The agent runs as a read-only DaemonSet with zero enforcement capability, collecting and pushing signed, encrypted evidence to the Owl SaaS platform in a secure, one-way outbound architecture.

Visibility
Kernel-native at scale

Monitors process exec, network connections, DNS queries, file ops, and Linux capabilities directly from the kernel.

Automation
CIS K8s automation

46 automated control mappings detect violations across processes, containers, networking, and RBAC.

Safety
Safe by design

Read-only + push-only. Zero enforcement, no inbound command channels. Perfect for regulated industries.

Data flow

Simple, safe, scalable pipeline.

Single-direction data flow. No inbound commands. No cluster modifications. No enforcement hooks. Pure observability with cryptographic guarantees.

01 · Kernel events
cilium/ebpf

Process · Network · DNS · File · Capability

02 · Enrichment
K8s metadata

Container ID · Pod · Node · RBAC context

03 · Rule engine
CIS control

Matching & evaluation

04 · Evidence
Sign / Encrypt

HMAC + AES · buffer & batch

05 · Owl SaaS
TLS 1.3+ push

One-way, outbound only

→ one-way flow · no inbound channels · no cluster mutations
Invariant 01 · Read-only
Zero enforcement capability
No code path can modify cluster state.
Invariant 02 · Push-only
Outbound TLS only, no inbound
No listening sockets, no command channel.
Invariant 03 · Safe environment
Cannot modify cluster state
RBAC scoped to read-only resources.
Invariant 04 · Signed evidence
HMAC-SHA256 proves integrity
Tamper-evident batches for auditors.
Invariant 05 · Encrypted data
AES-256-GCM in transit
Confidentiality guarantees end-to-end.
Capabilities

Compliance monitoring without overhead.

Cloud-native compliance monitoring that installs in minutes and stays out of the way.

eBPF security monitoring

Process exec, network connections, DNS queries, file operations, and Linux capability checks — all instrumented with kernel-level precision.

CIS compliance detection

46 automated control mappings detect privileged containers, root execution, and network policy violations. 9 manual references flag policy-heavy controls.

Kubernetes integration

In-cluster metadata enrichment with pod namespaces, labels, and node info. Container ID to pod mapping and RBAC context scoring built in.

Evidence protection

HMAC-SHA256 signing for integrity, AES-256-GCM encryption for confidentiality, gzip batching, and automatic retry logic.

Observability & health

Health endpoint exposing uptime and monitor status. Prometheus metrics track violations and push latency. Structured logging for audit trails.

Cloud-native deployment

DaemonSet with Helm charts and Kustomize overlays. Read-only RBAC, minimal permissions, zero enforcement ensure safe rollouts.

Problems elf-owl solves

From audit burden to audit confidence.

Continuous, cryptographically-attestable evidence — no manual reviewer overhead.

Compliance audit burden

Automated detection eliminates manual reviewer overhead

Automated detection of 46 CIS controls. Signed, encrypted evidence provides immutable audit trails for SOC 2, ISO 27001, and PCI-DSS assessments.

Real-world example

A fintech firm reduces audit response time from 2 weeks to 2 hours with automated violation reports and evidence logs.

Runtime drift detection

Catches what configuration management can't

eBPF detects process anomalies, capability abuse, and file access patterns. Flags deviations from policy intent with pod-level precision.

Real-world example

A healthcare provider catches an app container attempting to execute setuid binaries and logs evidence for immediate investigation.

Evidence chain of custody

Read-only + push-only eliminates tampering concerns

Cryptographic signing ensures auditors trust the integrity of collected data end-to-end.

Real-world example

A regulated environment passes unannounced audits by proving through signed logs that no compliance controls were ever disabled or bypassed.

Quick start

Deploy in minutes with Helm or Kustomize.

Ship as a read-only DaemonSet. No enforcement surface, no inbound channels — just evidence.

// helm install
helm install elf-owl ./deploy/helm \
  --namespace elf-owl-system \
  --create-namespace \
  --set clusterID=prod-us-east-1 \
  --set owlAPIEndpoint=https://owl-saas.example.com
// kubectl apply
kubectl apply -k deploy/kustomize/overlays/production/
Environment variables
OWL_CLUSTER_IDCluster identifier
OWL_NODE_NAMENode name (auto-populated)
OWL_API_ENDPOINTOwl SaaS endpoint URL
OWL_JWT_TOKENJWT token for authentication
OWL_LOG_LEVELLog level (debug, info, warn, error)
API reference

Health & metrics, out of the box.

Standard endpoints for integration with your monitoring stack.

GET /health
{
  "agent_version": "0.1.0",
  "uptime": "1h23m45s",
  "status": "healthy",
  "events_processed": 1523,
  "violations_found": 42,
  "monitors": {
    "process": true,
    "network": true,
    "dns": true,
    "file": true,
    "capability": true
  }
}
GET /metrics
  • elf_owl_events_processed_total
    Total events processed by the agent
  • elf_owl_violations_found_total
    Total CIS violations detected
  • elf_owl_events_buffered
    Current evidence buffer depth
  • elf_owl_push_latency_seconds
    Push operation latency histogram
  • elf_owl_enrichment_errors_total
    Errors during K8s/container correlation
  • elf_owl_host_events_discarded_total
    Host events discarded (kubernetes_only mode)
CIS Kubernetes compliance

46 automated controls. 9 manual references.

elf-owl maps and detects compliance against CIS Kubernetes v1.8 benchmarks. Automated controls leverage eBPF and K8s API queries; manual controls are flagged for auditor review.

Automated controls

Detect privileged containers, root execution, Linux capability abuse, root filesystem writes, default ServiceAccount usage, and NetworkPolicy violations through eBPF and K8s metadata.

  • CIS 4.5.1 · Privileged container detection
  • CIS 4.5.2 · Root user execution detection
  • CIS 4.5.3 · Linux capability usage
  • CIS 4.1.1 · Default ServiceAccount detection
  • CIS 4.6.1 · Default deny NetworkPolicy
Manual controls

API server, kubelet, and etcd configuration controls that require node-level access and human auditor review. elf-owl flags these for manual remediation.

  • CIS 1.1–1.5 · API server configuration
  • CIS 4.2 · Kubelet configuration
  • · 7 policy-driven controls for auditor review

See config/rules/cis-controls.yaml and docs/remediation.md for complete mappings.