Scanning STACKIT with Aikido
Aikido fully supports protecting workloads on STACKIT through specific integrations. A native integration may be added in the future, but you can already achieve full coverage by combining:
Container image scanning for STACKIT registry or any other OCI-compatible registry
Kubernetes cluster scanning for STACKIT Managed Kubernetes or self-managed clusters
Kubernetes cluster image scanning for STACKIT Managed Kubernetes or self-managed clusters
Virtual machine scanning via the Local VM Scanner on STACKIT instances
Features
Container image scanning
STACKIT’s container registry and most third-party registries you use from STACKIT are OCI-compatible, so they can be scanned using Aikido.
Create a read-only or pull-only user in STACKIT registry: https://docs.stackit.cloud/products/developer-platform/container-registry/getting-started/getting-started-with-container-registry/#log-in-to-the-container-registry
Follow the OCI guide below to configure container image scanning
Kubernetes cluster scanning
If you use STACKIT Managed Kubernetes or run your own Kubernetes clusters on STACKIT VMs, you can connect them as generic Kubernetes clusters.
Kubernetes cluster image scanning
If you use STACKIT Managed Kubernetes or run your own Kubernetes clusters on STACKIT VMs, you can scan the images of running containers with Kubernetes image scanning.
Virtual Machine scanning
To scan Virtual Machines on STACKIT, use the Local VM Scanner. It inspects packages, system dependencies and configuration directly on the instance.
You can roll this out centrally using your usual automation tooling (e.g. Ansible, Terraform-provisioned scripts, or cloud-init) so that new STACKIT instances are automatically enrolled.
Last updated
Was this helpful?