Image Slimming
Does the fix reduce attack surface (smaller base, removed tools)?
Measures AI models on remediating vulnerabilities in container images and binary artifacts — including base image selection, layer-level patches, and SBOM-driven fixes.
Each model response is judged on these dimensions by an LLM-as-Judge calibrated against expert annotations.
Does the fix reduce attack surface (smaller base, removed tools)?
Does the proposed image actually resolve the flagged CVEs?
Are the Dockerfile changes deterministic and cache-friendly?
Does the model correctly identify which SBOM component carries the CVE?
Is signature/provenance preserved in the proposed remediation?
An illustrative case to show how the model is presented with a problem and how its response is scored.
Container image ghcr.io/acme/api:1.4 ships glibc 2.31 with CVE-2024-2961.
Propose a Dockerfile change that fixes the CVE while preserving runtime behavior. Justify base image choice.
Switch base from debian:bullseye-slim to debian:bookworm-slim (glibc 2.36). Validate runtime libs. Rebuild with cosign signing in CI.
Models that suggest "alpine" without verifying glibc-dependent runtime behavior are penalized.
All Remediation Labs benchmarks evolve through three versions, increasing in difficulty and realism.
Models are given the raw security finding and asked to recommend a remediation. No environment context provided.
Models receive the finding plus relevant system, code, and policy context. Evaluated on contextual reasoning quality.
Models must produce a remediation that can be safely executed end-to-end — code patches, IaC changes, runbook steps — with verification.
Get model leaderboards, scoring methodology, dataset details, and roadmap access — or discuss generating proprietary remediation datasets for your environment.
Or email us directly at info@remediationlabs.com