Skip to content

Conversation

maycmlee
Copy link
Contributor

What does this PR do? What is the motivation?

Merge instructions

  • Replaces "sensitive data issues" with "sensitive data findings"
  • Renames the doc Investigate Sensitive Data Issues with Investigate Sensitive Data Findings
  • Adds an alias
  • Updates an image

Merge readiness:

  • Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

@maycmlee maycmlee requested a review from a team as a code owner October 15, 2025 15:20
@github-actions github-actions bot added the Images Images are added/removed with this PR label Oct 15, 2025
@maycmlee maycmlee changed the title Replace sensitive data issues with findings [DOCS-12228] Replace sensitive data issues with findings Oct 15, 2025
@estherk15 estherk15 self-assigned this Oct 15, 2025
Copy link
Contributor

@estherk15 estherk15 left a comment

Choose a reason for hiding this comment

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

Wasn't sure if "sensitive data findings" was the full feature name, feel free to ignore if it doesn't make sense!

[Sensitive Data Scanner][24] can help prevent sensitive data leaks and limit non-compliance risks by discovering, classifying, and optionally redacting sensitive data. It can scan for sensitive data in your telemetry data, such as application logs, APM spans, RUM events, and events from Event Management. It can also scan for sensitive information within your cloud storage resources.

After you [set up Sensitive Data Scanner][25], use the Summary page to see details of sensitive data issues that have been identified, so that you can triage, investigate, and remediate the issues.
After you [set up Sensitive Data Scanner][25], use the Findings page to see details of sensitive data findings that have been identified, so that you can triage, investigate, and remediate the findings.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
After you [set up Sensitive Data Scanner][25], use the Findings page to see details of sensitive data findings that have been identified, so that you can triage, investigate, and remediate the findings.
After you [set up Sensitive Data Scanner][25], use the Findings page to see details of detected sensitive data. From there, you can triage, investigate, and remediate the findings.

Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
@maycmlee maycmlee merged commit 337a0a2 into may/replace-summary-with-findings Oct 15, 2025
13 of 14 checks passed
@maycmlee maycmlee deleted the may/replace-issues-with-findings branch October 15, 2025 20:54
maycmlee added a commit that referenced this pull request Oct 16, 2025
* replace summary with findings

* update image

* update images

* [DOCS-12228] Replace sensitive data issues with findings (#32200)

* updates and image

* Apply suggestions from code review

Co-authored-by: Esther Kim <esther.kim@datadoghq.com>

---------

Co-authored-by: Esther Kim <esther.kim@datadoghq.com>

* update image

---------

Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Images Images are added/removed with this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants