Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,9 @@
- link: "https://www.datadoghq.com/blog/datadog-container-image-view/"
tag: "Blog"
text: "Enhance your troubleshooting workflow with Container Images in Datadog Container Monitoring"
- link: "/security/cloud_security_management/setup/ci_cd/#link-dockerfile-to-vulnerabilities"
tag: "Documentation"
text: "Link a Dockerfile to vulnerabilities detected in production"
---

## Overview
Expand Down Expand Up @@ -102,6 +105,16 @@

{{< img src="infrastructure/containerimages/image_layer_vulnerabilities.png" alt="A list of vulnerabilities associated with each layer of an image" width="100%">}}

## Trace production vulnerabilities to source code

When a CVE is detected on a running container image, Datadog can link it directly to the Dockerfile and commit that introduced the vulnerable package. This closes the gap between a production alert and the code change that caused it, giving developers the context they need to remediate at the source rather than chasing package versions across registries.

Check notice on line 110 in content/en/security/cloud_security_management/vulnerabilities/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength

Suggestion: Try to keep your sentence length to 25 words or fewer.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When a CVE is detected on a running container image, Datadog can link it directly to the Dockerfile and commit that introduced the vulnerable package. This closes the gap between a production alert and the code change that caused it, giving developers the context they need to remediate at the source rather than chasing package versions across registries.
When Datadog detects a CVE on a running container image, it can link the CVE directly to the Dockerfile and commit that introduced the vulnerable package. This closes the gap between a production alert and the code change that caused it, giving developers the context they need to remediate at the source rather than chasing package versions across registries.

Hopefully clarifies what "it" in "can link it directly" refers to?


To enable this code-to-cloud mapping, add OCI image annotations to your container images at build time. Datadog uses these annotations to display a preview of the Dockerfile inside the Container Image Vulnerabilities panel and to surface the exact repository, commit, and file path associated with the vulnerability.

Check notice on line 112 in content/en/security/cloud_security_management/vulnerabilities/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength

Suggestion: Try to keep your sentence length to 25 words or fewer.

{{< img src="security/vulnerabilities/csm-vm-dockerfile-panel.png" alt="The Container Image Vulnerabilities panel showing a Dockerfile preview linked to a detected CVE" width="100%">}}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This image seems to have gotten compressed somehow, so it's a bit blurry. It also shows a lot of the Ui, so it's hard to see which part is the relevant part of the page. I can help you make a more cropped version if you send me the URL, or maybe we don't need an image here?


To set up source linking, see [Link Dockerfile to vulnerabilities][22] in the CI/CD container image scanning guide.

## Automation and Jira integration
Make Cloud Security Vulnerabilities part of your daily workflow by setting up [security notification rules][17] and [automation pipelines (in Preview)][20]:
- Get alerted upon detection of an exploitable vulnerability for your scope
Expand Down Expand Up @@ -142,6 +155,7 @@
[19]: https://app.datadoghq.com/security/catalog/libraries
[20]: https://www.datadoghq.com/product-preview/security-automation-pipelines/
[21]: /security/cloud_security_management/setup/ci_cd
[22]: /security/cloud_security_management/setup/ci_cd/#link-dockerfile-to-vulnerabilities

## Further reading

Expand Down
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Docs don't use dark images, so you're good to remove this file 🙂

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading