Inquiry Regarding Container Image Vulnerabilities and Best Practices

Anonymous
2023-08-07T16:30:48.7733333+00:00

We are currently in the process of developing a container utilizing the latest version of "mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2019". We have also experimented with specific versions such as "mcr.microsoft.com/dotnet/framework/aspnet:4.8-20230711-windowsservercore-ltsc2019" and "mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2022" from 2022. Through the use of the "Container registry images should have vulnerability findings resolved (powered by Qualys)" tool, we have conducted vulnerability scans on these images and have encountered a number of vulnerabilities.

Our challenge arises from a client's policy that restricts the use of images with a certain level of vulnerabilities. Despite utilizing the latest Microsoft images and integrating our own developed application, our client has expressed concerns about the detected vulnerabilities and their potential impact on security.

We understand that Microsoft continuously updates and improves its images to address security vulnerabilities. However, as we integrate our application with the latest Microsoft images, we are left wondering about the appropriate steps to take in addressing these vulnerabilities. Shouldn't the latest Microsoft images already encompass the necessary security fixes? What guidance can we provide to our client in light of these concerns?

Our application is a simple data processing tool that includes a web API developed by our team. Access to this API is exclusively secured through HTTPS, and authentication to the API is facilitated through a token generated by Azure AD app registration.

We appreciate your time and expertise in this matter. Your guidance on how to effectively manage and address vulnerabilities within our container images, as well as how to best communicate with our client, would be highly valuable to us.

Thank you for your attention, and we look forward to your response.

Best regards,
Roberto
User's image

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
508 questions
Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,448 questions
Windows for business | Windows Server | Devices and deployment | Configure application groups
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2023-08-09T15:42:23.59+00:00

    Thank you very much for your response, Limitless Technology

    Before posting the question here, we spent several days searching for a solution on Google. We also asked questions to both ChatGPT AI and Bing AI, but unfortunately, we did not find any answers to our problem.

    We were already familiar with the tools you mentioned, and they seem to be more focused on scanning images, particularly for Linux rather than Windows containers. However, our concern is not just about image scanning but rather about who and how the vulnerability is resolved, especially when we are basing our container on a container provided by Microsoft.

    We meticulously reviewed vulnerability by vulnerability, and it appears that there is no specific "Remediation" applied to "Windows Server 2019 Datacenter," which is the targeted system for the said container.

    At this point, our assumption is that by using the latest version of Microsoft's container each month, the available patches for "Windows Server 2019 Datacenter" might have already been applied, although this remains speculative as no patches for it are currently evident.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.