Home / AuraCore / Kubernetes Security

Containers come and go. Backdoors on the node stay.

Kubernetes security and container security at runtime, with AuraCore on Linux and FreeBSD.

The image scan checks what you ship. It doesn't see what happens on the node three weeks later. AuraCore checks your nodes, Docker hosts, and servers in production for backdoors and acts only through signed commands.

Kubernetes security doesn't end at the image. An attacker who gets into a pod through a vulnerable application looks for the way down to the node and digs in there: in SSH keys, cron jobs, and systemd units. AuraCore by Identiqa checks these host-level persistence points continuously on Linux, FreeBSD, virtual machines, Kubernetes, and Docker.

Where the image scan stops.

Four layers on which a cluster can be attacked. Most teams check the top one. The three below it, rarely.

BUILD
Image and registry

Known vulnerabilities in packages, checked before rollout.

IMAGE SCAN
RUNTIME
Pods and containers

Traces an attacker leaves in the running container.

AURACORE
NODE
Worker node and Docker host

authorized_keys, cron jobs, systemd units, sudoers, setuid binaries, and open sockets.

AURACORE
BOOT
Hardware and startup

Each node is verified at startup through Secure Boot and TPM 2.0 attestation. AuraCore then talks to it only over mTLS.

AURACORE

From the pod to the node.

Once an attacker gets into a container, the host is the next target. Access there survives every new deployment.

Without runtime checks

  1. Vulnerable application
  2. Pod taken over
  3. Escape to the node
  4. SSH key planted
  5. Pod redeployed, access stays

The new image is clean. The node underneath still belongs to the attacker.

With AuraCore

  1. Vulnerable application
  2. Pod taken over
  3. Escape to the node
  4. SSH key planted
  5. AuraCore detects the change
  6. Node isolated by signed command

The backdoor doesn't go unnoticed, and the node is off the network.

Illustrative, simplified.

Your security agent shouldn't be the way in.

Many agents on servers open a root-level remote command channel. If the vendor's management plane is taken over, that channel is open to the attacker on every system at once. AuraCore has no open shell. It runs only signed commands from a closed command list.

A mesh of verified nodes.

AuraCore ties your existing systems into a verified network and shows what runs there.

AuraCore console: world map of sites with their links, and the Aura panel on the right
AURACORE MESH · TPM 2.0 ATTESTATION · SIGNED WORKLOAD ACTIONS

AuraCore maps your sites and the links between them. On the right, Aura answers questions about your fleet.

Linux & FreeBSDBare metal, virtual machines, Kubernetes, Docker
6 host-level pointswhere attackers persist, checked continuously
Secure Boot + TPM 2.0Every node is verified at startup
No shellSigned commands from a closed list only

What changes on your nodes.

The node is checked, not just the image

AuraCore continuously checks the hosts under your containers for authorized_keys, cron jobs, systemd units, sudoers rules, setuid binaries, and open sockets.

CONTINUOUS PERSISTENCE CHECK

Findings trigger action

When AuraCore detects a backdoor or a critical vulnerability, it isolates the system or, after a dry run, applies a signed update.

ISOLATE · DRY RUN · UPDATE

Your cluster stays as it is

AuraCore runs on the systems you already operate. It needs no new servers and no rebuild.

LINUX · FREEBSD · VM · K8S · DOCKER

Your stateful data is backed up

AuraLink keeps the backups of your databases and stateful data locked in your own rack, so you can recover cleanly after an incident.

AURALINK

Common questions

Does AuraCore replace our image scanner?

No, it complements it. The image scan checks before rollout whether an image contains known vulnerabilities. AuraCore checks afterward, in production, whether someone has planted a backdoor on nodes, on hosts, or in containers.

Do we need new servers or a rebuilt cluster?

No. AuraCore runs on the systems you already operate: Linux, FreeBSD, virtual machines, Kubernetes, and Docker.

What does AuraCore do when it finds a backdoor?

It isolates the affected system or, after a dry run, applies a signed security update. If you want to observe first, run AuraCore in read-only mode: it then reports to your SIEM and informs your SOC without acting itself.

In your rack. On the cloud contract you already have.

We size Identiqa to your infrastructure and sites. Buy directly through Identiqa or on your existing agreement with Amazon Web Services, Google Cloud, or Microsoft Azure.

Architecture briefing & advisory