# Cis Docker 4.6

> Ensure that HEALTHCHECK instructions have been added to container images

- Skill: `cyberstrikeus/cis-docker-4-6` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cyberstrikeus/cis-docker-4-6`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberstrikeus/cis-docker-4-6/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: cyberstrikeus (https://skillmd.com/u/cyberstrikeus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberstrikeus/cis-docker-4-6

---


# 4.6 Ensure that HEALTHCHECK instructions have been added to container images (Manual)

## Profile Applicability

- Level 1 - Docker - Linux

## Description

You should add the `HEALTHCHECK` instruction to your Docker container images in order to ensure that health checks are executed against running containers.

## Rationale

An important security control is that of availability. Adding the `HEALTHCHECK` instruction to your container image ensures that the Docker engine periodically checks the running container instances against that instruction to ensure that containers are still operational.

Based on the results of the health check, the Docker engine could terminate containers which are not responding correctly, and instantiate new ones.

## Impact

None.

## Audit Procedure

You should run the command below to ensure that Docker images have the appropriate `HEALTHCHECK` instruction configured.

```bash
docker inspect --format='{{ .Config.Healthcheck }}' <IMAGE>
```

## Remediation

You should follow the Docker documentation and rebuild your container images to include the `HEALTHCHECK` instruction.

## Default Value

By default, `HEALTHCHECK` is not set.

## References

1. https://docs.docker.com/engine/reference/builder/#healthcheck

## CIS Controls

### v8

**16.12 Implement Code-Level Security Checks**

Apply static and dynamic analysis tools within the application life cycle to verify that secure coding practices are being followed.

### v7

**5.2 Maintain Secure Images**

Maintain secure images or templates for all systems in the enterprise based on the organization's approved configuration standards. Any new system deployment or existing system that becomes compromised should be imaged using one of those images or templates.