Skip to content

Update Security Findings schema reference: add base_image, reachable-risk fields, severity-override metadata#37553

Open
filipelteixeira wants to merge 1 commit into
masterfrom
filipelteixeira/schema-update-0e00fb51
Open

Update Security Findings schema reference: add base_image, reachable-risk fields, severity-override metadata#37553
filipelteixeira wants to merge 1 commit into
masterfrom
filipelteixeira/schema-update-0e00fb51

Conversation

@filipelteixeira

@filipelteixeira filipelteixeira commented Jun 16, 2026

Copy link
Copy Markdown

What does this PR do?

Updates the public Security Findings schema reference page for this week's schema batch.

Note: crates.io (Ecosystem) is not enumerated on this reference page, so it produces no doc change.

⚠️ Reviewer note: this generated diff also removes the "## Linking to findings" prose section that exists on main. That section is not part of the schema batch. It should be restored before merge (the doc generator does not preserve that manually-added section).

Siblings PRs

https://github.com/DataDog/logs-backend/pull/141150
https://github.com/DataDog/web-ui/pull/319889
https://github.com/DataDog/dd-source/pull/469951

Generated by

Generated by the Security Finding Schema Tool.

cc @DataDog/k9-finding-schema-governance

@filipelteixeira filipelteixeira changed the title Update Security Findings schema reference page Update Security Findings schema reference: add base_image, reachable-risk fields, severity-override metadata Jun 16, 2026
@filipelteixeira filipelteixeira marked this pull request as ready for review June 17, 2026 08:21
@filipelteixeira filipelteixeira requested a review from a team as a code owner June 17, 2026 08:21

@buraizu buraizu left a comment

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.

Left some feedback. Also, I'm not seeing these changes reflected in the build preview:
https://docs-staging.datadoghq.com/filipelteixeira/schema-update-0e00fb51/security/guide/findings-schema/

Do you happen to know if that's expected in this case?

<tr>
<td><code>unreachable_at</code></td>
<td>integer</td>
<td><strong>Path:</strong> <code>@risk_details.is_function_reachable.evidence.unreachable_at</code><br>Timestamp in milliseconds (UTC) at which the finding will transition to unreachable if the vulnerable function has not been called.</td>

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
<td><strong>Path:</strong> <code>@risk_details.is_function_reachable.evidence.unreachable_at</code><br>Timestamp in milliseconds (UTC) at which the finding will transition to unreachable if the vulnerable function has not been called.</td>
<td><strong>Path:</strong> <code>@risk_details.is_function_reachable.evidence.unreachable_at</code><br>Timestamp in milliseconds (UTC) at which the finding transitions to an unreachable state if the vulnerable function is not called.</td>

{{% /tab %}}
{{< /tabs >}}

## Linking to findings

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.

Looks like this section should be restored, per the reviewer note in the PR description:

⚠️ Reviewer note: this generated diff also removes the "## Linking to findings" prose section that exists on main. That section is not part of the schema batch. It should be restored before merge (the doc generator does not preserve that manually-added section).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants