An illustration featuring a crane lifting several server racks with Kubernetes and Keycloak logos. The background includes large digital storage units. Labels on the racks display data strings and the name Upwind.

Pinpoint Vulnerability Origins With Complete Visibility into Container Image Layers

Denise Ashur February 21, 2024

Pinpoint Vulnerability Origins With Complete Visibility into Container Image Layers

We are excited to release an important new capability – container image layer visibility.

A Docker build consists of a series of ordered build instructions. A layer, or image layer, is a change in an image, or an intermediate image. Every command specified (FROM, RUN, COPY, etc.) in a Dockerfile causes the previous image to change, thus creating a new layer.

This new capability provides a detailed breakdown of each container image by:

  • Highlighting specific image layers
  • Identifying image changes between layers
  • Pinpointing the introduction layer for every package

Understanding and tracking container image layers is crucial for identifying when and where vulnerabilities were first introduced and can also be used to discover package drifts related to packages installed outside the base image layer.

layers-details-1-1024x661

In addition to layer visibility and the ability to pinpoint vulnerabilities origins, you can also use this capability for:

1. Streamlined scans of large images, leveraging our ability to break the scan per layer

2. More efficient scans that only scan the last layer

3. Faster and easier scanning for your organization

Use this capability for increased transparency into your running container images, helping you rapidly identify and track how image layers introduce or resolve vulnerabilities and how this impacts your overall cloud security.

Contents

Further Reading

snowflake-hero

Upwind Now Secures Snowflake from AI Down to the Storage Underneath It

Ask a security team where the company's most sensitive data lives and they'll say Snowflake without pausing. Ask who can reach it and the room goes quiet, because that answer belongs to the data team. It isn't negligence, it's vocabulary. Snowflake speaks in roles, grants, warehouses and schemas. Your cloud security program speaks in IAM,…
What IAM Sees That You Don't

What IAM Sees That You Don’t

Every IAM policy you write depends on condition keys - they're the precision layer that turns "can call S3" into "can call S3 only from our VPC, using our identity, on resources we own." They're the backbone of least-privilege, data perimeters, and SCP guardrails. But here's the thing: for every request, the IAM engine assembles…
Let Me Speak to Your Manager (Account)

Let Me Speak to Your Manager (Account)

The management account is the most privileged account in any AWS Organization. It controls SCPs, creates and deletes member accounts, manages IAM Identity Center, and is itself exempt from SCPs. Getting its 12-digit account ID is the first step in targeting it. The documented way to get it is organizations:DescribeOrganization - but security-conscious environments restrict…
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Threat RSS
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Main RSS