DirectorySecurity AdvisoriesPricing
Sign in
Directory
kubescape-host-scanner logo

kubescape-host-scanner

packaged by Chainguard

Last changed
Request a free trial

Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.

Tags
Overview
Comparison
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Container for kubescape-host-scanner

Kubernetes host-sensor project. The host information provider for Kubescape

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/kubescape-host-scanner:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This image is a drop-in replacement for the upstream quay.io/kubescape/host-scanner image. Like upstream, the kube-host-sensor binary is installed at /usr/bin/kube-host-sensor and is the entrypoint, the working directory is /root, and the RELEASE environment variable is set (empty by default).

The image runs as root (UID 0) by default. The host scanner reads node-level information (kernel, kubelet, CNI, and security hardening settings) from the host filesystem, which is mounted at /host_fs, so it is normally deployed as a privileged DaemonSet with hostPID (and hostIPC) enabled.

The host scanner is built with Go and licensed under the Apache License 2.0.

Getting Started

Deploy the host scanner as a standalone privileged DaemonSet with access to the node filesystem. The following manifest is modeled on the upstream deployment/host-scanner.yaml:

apiVersion: v1
kind: Namespace
metadata:
  name: kubescape
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: host-scanner
  namespace: kubescape
  labels:
    app: host-scanner
spec:
  selector:
    matchLabels:
      name: host-scanner
  template:
    metadata:
      labels:
        name: host-scanner
    spec:
      tolerations:
        - operator: Exists
      hostPID: true
      hostIPC: true
      automountServiceAccountToken: false
      containers:
        - name: host-sensor
          image: cgr.dev/ORGANIZATION/kubescape-host-scanner:latest
          securityContext:
            privileged: true
            allowPrivilegeEscalation: true
            readOnlyRootFilesystem: true
          ports:
            - name: scanner
              containerPort: 7888
              protocol: TCP
          volumeMounts:
            - name: host-filesystem
              mountPath: /host_fs
          startupProbe:
            httpGet:
              path: /readyz
              port: 7888
            failureThreshold: 30
            periodSeconds: 1
          livenessProbe:
            httpGet:
              path: /healthz
              port: 7888
            periodSeconds: 10
      volumes:
        - name: host-filesystem
          hostPath:
            path: /
            type: Directory

Save the manifest as host-scanner.yaml and apply it:

kubectl apply -f host-scanner.yaml
kubectl -n kubescape rollout status daemonset/host-scanner

Once running, the host scanner serves its HTTP API on port 7888.

This image does not include a shell or curl, so you cannot query the API from inside the pod. Instead, forward the port to your workstation:

kubectl -n kubescape port-forward pod/<host-scanner-pod> 7888:7888

Then, in another terminal, query the API from your workstation:

curl -s http://localhost:7888/healthz
curl -s http://localhost:7888/kernelVersion
curl -s http://localhost:7888/CNIInfo
curl -s http://localhost:7888/linuxSecurityHardening

Alternatively, run the same curl commands against the pod IP from a host or pod that can reach it.

Configuration

  • Port: 7888 (HTTP API). The upstream image does not declare EXPOSE.
  • Host filesystem: mount the node root filesystem at /host_fs so the scanner can collect host information.

Documentation and Resources

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.

Licenses

Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:

  • MIT

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement

Compliance

Chainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.

SLSA compliance at Chainguard

This image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.

PCI DSS at Chainguard

Category
Application

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.