diff --git a/content/en/data_security/agent.md b/content/en/data_security/agent.md index 1860fa5aeec..07cc3e5b4a8 100644 --- a/content/en/data_security/agent.md +++ b/content/en/data_security/agent.md @@ -72,7 +72,8 @@ Datadog's Vulnerability Management program includes regular assessments of suppo Regarding its Container Agent specifically, Datadog performs regular vulnerability static analysis on both its general availability (GA) and release candidate (RC) releases. The Datadog Container Agent can be found in public registries as mentioned in [Docker Agent][10], and additionally, Datadog Agent source code is open source. This empowers customers to perform vulnerability scanning with their preferred tooling based on a cadence that meets their unique needs. This provides the required visibility for customers inclined to monitor the Datadog Agent for potential vulnerabilities. -If you believe you've discovered a bug in Datadog's security, see [Report An Issue][11]. To submit a vulnerability inquiry on a specific product as an existing customer, reach out to [Datadog Support][12] through your standard support process. If submitting a support ticket through the Datadog website, set the `Product type` field to `Vulnerability Inquiry on Datadog Product`. +If you believe you've discovered a bug in Datadog's security, see [Report An Issue][11]. +To check the status of a specific CVE, see the [Public Artifact Vulnerabilities Page][19]. For additional information, contact [Datadog Support][12] through your standard support process. When submitting a support ticket through the Datadog website, set the `Product type` field to `Vulnerability Inquiry on Datadog Product`. ## Running as an unprivileged user @@ -227,3 +228,4 @@ Only applicable metrics are emitted. For example, if DBM is not enabled, none of [16]: https://keys.datadoghq.com/DATADOG_RPM_KEY_B01082D3.public [17]: https://keys.datadoghq.com/DATADOG_RPM_KEY_4F09D16B.public [18]: https://keys.datadoghq.com/DATADOG_APT_KEY_06462314.public +[19]: /data_security/guide/public_artifact_vulnerabilities/ diff --git a/content/en/data_security/guide/_index.md b/content/en/data_security/guide/_index.md index 489f4ca3525..d6fe9ebd657 100644 --- a/content/en/data_security/guide/_index.md +++ b/content/en/data_security/guide/_index.md @@ -10,7 +10,8 @@ cascade: --- -{{< whatsnext desc="Deprecation notices:" >}} +{{< whatsnext desc="Guides:" >}} + {{< nextlink href="data_security/guide/public_artifact_vulnerabilities" >}}Public Artifact Vulnerabilities{{< /nextlink >}} {{< nextlink href="data_security/guide/tls_deprecation_1_2" >}}TLS < 1.2 deprecation notice{{< /nextlink >}} {{< nextlink href="data_security/guide/tls_cert_chain_of_trust" >}}Changes to Datadog's TLS certificate chain of trust{{< /nextlink >}} {{< nextlink href="data_security/guide/tls_ciphers_deprecation" >}}TLS ciphers deprecation notice{{< /nextlink >}} diff --git a/content/en/data_security/guide/public_artifact_vulnerabilities.md b/content/en/data_security/guide/public_artifact_vulnerabilities.md new file mode 100644 index 00000000000..cd124fe81ac --- /dev/null +++ b/content/en/data_security/guide/public_artifact_vulnerabilities.md @@ -0,0 +1,85 @@ +--- +title: Public Artifact Vulnerabilities +--- + +## Overview + +The Public Artifact Vulnerabilities page lets you view vulnerability and response information for Datadog's publicly available artifacts and libraries. It is the canonical place to look up: + +- Which vulnerabilities affect a given artifact (by image/version) +- Which artifacts are affected by a given CVE +- Status, justification, impact, and action statements for each vulnerability + +This feature is in beta. + +## How to access + +The Public Artifact Vulnerabilities page is accessible through the Help page under **Public Artifact Vulnerabilities**. + +![Help page with Public Artifact Vulnerabilities link](/images/data_security/public_artifact_vulnerabilities/help-page.png) + +![Public Artifact Vulnerabilities page](/images/data_security/public_artifact_vulnerabilities/public-artifact-vulnerabilities-page.png) + +## Two ways to use the page + +### 1. Look up by image and version (artifact-centric) + +Use this when you want to see all vulnerabilities for a specific artifact and version (for example, the Datadog Agent image version 7.52.0). + +- **Image**: Choose an artifact from the **Image** dropdown (for example, agent, cluster-agent, synthetic-private-location-worker). The list is built from available public artifacts. +- **Version**: Choose a **Version** for that image. Versions are sorted with newest first. + +The table loads and shows one row per vulnerability affecting that image/version. + +**Table columns (by image/version):** + +| Column | Purpose | +|--------|---------| +| Severity | Severity of the vulnerability (for example, Critical, High, Medium, Low, and Info). | +| Vulnerability | CVE or vulnerability identifier and name. | +| Platform | Platform(s) the statement applies to (for example, Linux, Windows). The platform column also shows the list of variants affected by the CVE (for example, fips, jmx, and servercore). | +| Status | Current status: for example, Not affected, Affected, Fixed, and Under investigation. | +| Additional Information | More information on the status of the CVE and justification of the status if needed. For example, if the status is component_not_present, this column explains why the CVE does not affect the artifact and how that conclusion was reached. Some statuses do not have additional information (for example, Under investigation means the impact of the CVE is still under analysis). | + +You can use the search/filter box above the table to filter these rows by keyword. + +![Look up by image and version](/images/data_security/public_artifact_vulnerabilities/by-image-version.png) + +### 2. Look up by CVE (CVE-centric) + +Use this when you have a CVE ID and want to see which artifacts/versions are affected and the status for each. + +1. In the search box at the top of the table, enter one or more CVE IDs (for example, `CVE-2024-1234` or `CVE-2024-1234, CVE-2024-5678` for multiple). +2. Click **Find CVE in artifacts**. + +The table switches to CVE mode and shows one row per (CVE, artifact, version, status) combination. + +**Table columns (by CVE):** + +| Column | Purpose | +|--------|---------| +| CVE | The CVE ID. | +| Artifact Name | Name of the artifact (for example, agent, library name). | +| Version | Version of the artifact. | +| Platform | Platform(s) for this row (for example, Linux, Windows). | +| Status | Status for this CVE/artifact/version (for example, Not affected, Affected, Fixed, and Under investigation). | +| Additional Information | More information on the status of the CVE and justification of the status if needed. | + +After a CVE search, the table filter is cleared so all returned rows are visible. You can type in the search box again to filter the current result set. + +![Look up by CVE](/images/data_security/public_artifact_vulnerabilities/by-cve.png) + +## Available artifacts (images) + +The **Image** dropdown is populated from the list of tracked public artifacts. If you do not see an artifact you expect, contact [Datadog Support][1] to request that it be added. + +## Options and actions on the page + +| Option or action | Description | +|------------------|-------------| +| **Search / global filter** | Filter table rows by any text. In "by image/version" mode, the same search box is used before clicking **Find CVE in artifacts** to run a CVE lookup. | +| **Find CVE in artifacts** | Runs a CVE lookup using the current search box value (supports comma-separated CVE IDs). Only relevant when you want to look up by CVE. | +| **Pagination** | Use the table pagination to move through large result sets (for example, 50 rows per page). | +| **Resizable columns** | You can resize column widths for readability. | + +[1]: /help diff --git a/static/images/data_security/public_artifact_vulnerabilities/by-cve.png b/static/images/data_security/public_artifact_vulnerabilities/by-cve.png new file mode 100644 index 00000000000..99ce4094e9f Binary files /dev/null and b/static/images/data_security/public_artifact_vulnerabilities/by-cve.png differ diff --git a/static/images/data_security/public_artifact_vulnerabilities/by-image-version.png b/static/images/data_security/public_artifact_vulnerabilities/by-image-version.png new file mode 100644 index 00000000000..a52659ce935 Binary files /dev/null and b/static/images/data_security/public_artifact_vulnerabilities/by-image-version.png differ diff --git a/static/images/data_security/public_artifact_vulnerabilities/help-page.png b/static/images/data_security/public_artifact_vulnerabilities/help-page.png new file mode 100644 index 00000000000..41dd2146189 Binary files /dev/null and b/static/images/data_security/public_artifact_vulnerabilities/help-page.png differ diff --git a/static/images/data_security/public_artifact_vulnerabilities/public-artifact-vulnerabilities-page.png b/static/images/data_security/public_artifact_vulnerabilities/public-artifact-vulnerabilities-page.png new file mode 100644 index 00000000000..0cee4e17186 Binary files /dev/null and b/static/images/data_security/public_artifact_vulnerabilities/public-artifact-vulnerabilities-page.png differ