AWS scanning adds native support for Red Hat Hardened Images
InspectorScan can gate hardened images during builds, while ECR Basic scanning continues vulnerability checks after they reach the registry.
AWS has added support for Red Hat Hardened Images to two native container-security paths: the InspectorScan API used in build pipelines and Basic scanning in Amazon Elastic Container Registry. The integration lets teams scan Red Hat’s minimized runtime images without moving vulnerability analysis outside their existing AWS workflow.
What changed
The InspectorScan API accepts a software bill of materials generated from container images, archives or compiled binaries and returns a vulnerability report with NVD and CVSS scoring. Development teams can call it during a CI/CD build and use the result as a gate before an image reaches a registry.
ECR Basic scanning covers the later stage. It can scan an image automatically when it is pushed to Amazon ECR or on demand, then surface findings in the ECR console and through Amazon EventBridge. Used together, the two services provide a pre-registry check and continued detection for stored images.
Red Hat says both paths now recognize its Hardened Images catalog. That catalog contains nearly 60 core images and more than 150 variants built with a reduced package set to limit attack surface and vulnerability noise.
Who is affected
The change is aimed at application and security teams already using ECR or AWS-native build automation. It removes the need for a separate scanning path solely because the base image comes from Red Hat’s hardened catalog.
The images come in three variants. The default runtime image omits a shell and package manager. A builder variant restores development tools for multi-stage builds, with the resulting binary copied into a cleaner runtime image. A FIPS variant uses validated cryptographic modules when it runs on a FIPS-enabled host cluster.
What teams should do
Teams using InspectorScan can add an image or SBOM scan before the registry push and set a policy for findings that should block promotion. Teams relying on ECR should verify whether automatic scan-on-push is enabled and route EventBridge findings into their existing remediation workflow.
The integration does not make an image vulnerability-free. It does make Red Hat’s minimized images visible to the same AWS controls used for other build and registry artifacts, reducing the operational exception that teams would otherwise have to maintain.
sources
comments · 0