Secret validation docs update #32768
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Preview links (active after the
|
iadjivon
reviewed
Nov 11, 2025
content/en/security/code_security/secret_scanning/secret_validation.md
Outdated
Show resolved
Hide resolved
iadjivon
approved these changes
Nov 11, 2025
Contributor
iadjivon
left a comment
iadjivon
left a comment
There was a problem hiding this comment.
Added a small non-blocking suggestion and approved.
…ation.md Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com>
Taiki-San
reviewed
Nov 12, 2025
Contributor
Taiki-San
left a comment
Taiki-San
left a comment
There was a problem hiding this comment.
Two minor suggestions. Haven't double checked the list but it looks good
content/en/security/code_security/secret_scanning/secret_validation.md
Outdated
Show resolved
Hide resolved
|
|
||
| For secret types with validation available, Datadog displays the validation status in the explorer as "Active" or "Inactive". You can also filter or query detections by their Validation Status. | ||
|
|
||
| For some secret types, Datadog uses static validation methods, such as computing a checksum, to confirm that a detected secret is not a false positive. Static validation results are not displayed and all references to "validation" in the explorer correspond to live validation results. |
Contributor
There was a problem hiding this comment.
Suggested change
| For some secret types, Datadog uses static validation methods, such as computing a checksum, to confirm that a detected secret is not a false positive. Static validation results are not displayed and all references to "validation" in the explorer correspond to live validation results. | |
| For some secret types, Datadog may also use static validation methods, such as computing a checksum, to confirm that a detected secret is not a false positive. Static validation results are not displayed and all references to "validation" in the explorer correspond to live validation results. |
…ation.md Co-authored-by: Taiki <emile.spir@datadoghq.com>
dussault-antoine
pushed a commit
that referenced
this pull request
Nov 13, 2025
* adding secrets validation file * adding secrets validation to nav * updating page * update tags * updating wording based on guide * updating wording again * Update content/en/security/code_security/secret_scanning/secret_validation.md Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com> * Update content/en/security/code_security/secret_scanning/secret_validation.md Co-authored-by: Taiki <emile.spir@datadoghq.com> --------- Co-authored-by: Michelle Sun <michelle.sun@daatadoghq.com> Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com> Co-authored-by: Taiki <emile.spir@datadoghq.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
This PR introduces a new page into the Secret Scanning documentation, which is a new product in Code Security. The new page describes how validation works for Secret Scanning.
Merge instructions
Merge readiness:
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