Score yourself honestly

Take the Test: How Secure Is Your Container?

0 Yes out of 10

# Question Yes / No

Does your container run as a non-root user with privilege escalation blocked at runtime?

Yes No

Have you dropped all Linux capabilities your application doesn't explicitly need?

Yes No

Does your production image use a JRE rather than a full JDK?

Yes No

Is your base OS under 10 MB with no package manager in the runtime layer?

Yes No

Have you scanned your images for CVEs in the last 30 days?

Yes No

Do you go beyond CVSS scores, checking whether vulnerable code is actually reachable in your workload?

Yes No

Do you have a Software Bill of Materials (SBOM) for your container image?

Yes No

Is your base image from a vendor committed to patching CVEs on a defined SLA?

Yes No

Are your base images pinned by digest rather than tag?

Yes No

Can you verify your base image came from the expected publisher with signed attestation?

Yes No

0 Yes out of 10

0/10 answered 10 left

Start the test

Your result will appear here.

Click Yes or No for each question. The matching outcome will highlight automatically.

Go to Hardened Images

Current score Not enough data yet

8-10 Yes

Use hardened images to maintain it without overhead.

5-7 Yes

You have exploitable gaps that attackers actively look for.

4 or fewer Yes

Your containers are a significant production risk. Action required.

Secure your container at the base image level

Near-zero CVE container images, minimized attack surface, no package managers, SBOM, image signing, and SLA-backed CVE remediation.

Near-zero CVE images No package managers SBOM Image signing SLA-backed remediation