Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IAST Security Controls #27699

Open
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

jandro996
Copy link
Member

@jandro996 jandro996 commented Feb 19, 2025

What does this PR do? What is the motivation?

  • Add IAST security controls documentation
  • Update supported IAST vulnerability list with vulnerability codes

Merge instructions

Merge readiness:

  • Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then add the following PR comment:

/merge

Additional notes

@jandro996 jandro996 added WORK IN PROGRESS No review needed, it's a wip ;) Do Not Merge Just do not merge this PR :) labels Feb 19, 2025
Copy link
Contributor

github-actions bot commented Feb 19, 2025

@github-actions github-actions bot added the Architecture Everything related to the Doc backend label Feb 19, 2025
The following table lists the supported vulnerability types as secure marks for each language:

| **Type** | **Java** | **Node** | **.NET** | **Python** |
|----------|---------|--------|------|--------|
Copy link
Member

Choose a reason for hiding this comment

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

I think we should just update the table here: https://github.com/DataDog/documentation/blob/master/content/en/security/code_security/iast/_index.md#overview to include the vuln IDs (separate PR 🙏), and link it from here. Avoiding the mainteinance of these two tables, that will inevitably go out of sync.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done

@jandro996 jandro996 requested a review from smola February 27, 2025 12:43
@jandro996 jandro996 force-pushed the alejandro.gonzalez/security-controls-java branch from 904c2c7 to 558fdec Compare February 27, 2025 14:19
@jandro996 jandro996 force-pushed the alejandro.gonzalez/security-controls-java branch from d2ff74c to 227bd86 Compare March 7, 2025 07:46
@jandro996 jandro996 removed WORK IN PROGRESS No review needed, it's a wip ;) Do Not Merge Just do not merge this PR :) labels Mar 7, 2025
@jandro996 jandro996 marked this pull request as ready for review March 7, 2025 07:55
@jandro996 jandro996 requested a review from a team as a code owner March 7, 2025 07:55
@joepeeples joepeeples added the editorial review Waiting on a more in-depth review label Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Architecture Everything related to the Doc backend editorial review Waiting on a more in-depth review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants