You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/security/code_security/dev_tool_int/_index.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@ disable_toc: false
4
4
5
5
---
6
6
7
-
{{< whatsnext desc="You can integrate Code Security with several types of tools and receive real-time feedback on the quality and security of your code as it's written." >}}
7
+
{{< whatsnext desc="You can integrate Code Security with several types of tools throughout the developer workflow. Pull request comments and gates require setup of Datadog's integrations with your source code provider(s)." >}}
Copy file name to clipboardExpand all lines: content/en/security/code_security/dev_tool_int/ide_plugins/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ disable_toc: false
8
8
9
9
## Overview
10
10
11
-
[Code Security][1] integrates directly with integrated development environment (IDE) tools to provide real-time feedback on the quality and security of your first-party code as it's being written.
11
+
[Code Security][1] integrates directly with integrated development environment (IDE) tools to provide real-time feedback on the security and quality of your code. IDE integrations are supported for SAST, SCA, and IAST.
12
12
13
13
{{< whatsnext desc="See the documentation for information about the following integrations:">}}
Copy file name to clipboardExpand all lines: content/en/security/code_security/dev_tool_int/pull_request_comments/_index.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ You can configure PR comments at the organization or repository level in [Reposi
26
26
**Note**: PR comments are not PR checks. To set up checks, see [Quality Gates][10].
27
27
28
28
## Prerequisites
29
-
- You must have the Datadog source code integration for your provider enabled. PR comments are supported for [GitHub][2], [GitLab][8], and Azure DevOps repositories ([in Preview][9]).
29
+
- You must have the Datadog source code integration for your provider enabled. PR comments are supported for [GitHub][2], [GitLab][8], and [Azure DevOps][9] repositories.
30
30
- Your repositories must have the relevant Code Security product(s) enabled. To enable Code Security in-app, navigate to the [**Code Security** Settings page][4].
31
31
32
32
## Set up pull request comments
@@ -77,16 +77,16 @@ If you already have a GitHub App connected to Datadog, update it. Otherwise, cre
77
77
{{% /tab %}}
78
78
{{% tab "GitLab" %}}
79
79
80
-
See the [GitLab Source Code][8] setup instructions to connect GitLab to Datadog.
80
+
See the [GitLab Source Code][8] setup instructions to connect GitLab repositories to Datadog.
81
81
82
82
[8]: /integrations/gitlab-source-code/
83
83
84
84
{{% /tab %}}
85
85
{{% tab "Azure DevOps" %}}
86
86
87
-
Azure DevOps for Code Security is in Preview. [Request access to join the Preview][9].
87
+
See the [Azure Source Code][8] setup instructions to connect Azure repositories to Datadog.
Copy file name to clipboardExpand all lines: content/en/security/code_security/software_composition_analysis/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Datadog SCA uses a curated proprietary database. The database is sourced from Op
23
23
{{% security-products/sca-supported-lang %}}
24
24
25
25
SCA supports both static and runtime dependency detection:
26
-
- For **static detection**, you can scan from your CI/CD pipelines or from Datadog's infrastructure. See [static setup][1] to get started.
26
+
- For **static detection**, you can scan your repositories from your CI/CD pipelines or directly from Datadog's infrastructure. See [static setup][1] to get started.
27
27
- For **runtime detection**, you can enable SCA on services instrumented with Datadog APM. See [runtime setup][2] to get started.
Copy file name to clipboardExpand all lines: content/en/security/code_security/software_composition_analysis/setup_static/_index.md
+3-45Lines changed: 3 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,56 +91,14 @@ See the [GitLab source code setup instructions][1] to connect GitLab to Datadog.
91
91
{{% /tab %}}
92
92
{{% tab "Azure DevOps" %}}
93
93
94
-
<divclass="alert alert-danger">
95
-
Repositories from Azure DevOps are supported in closed Preview. Your Azure DevOps organizations must be connected to a Microsoft Entra tenant. <ahref="https://www.datadoghq.com/product-preview/azure-devops-integration-code-security/">Join the Preview</a>.
96
-
</div>
97
-
98
-
Before you can begin installation, request access to the closed Preview using the form above. After being granted access, see the following instructions to complete the setup process.
99
-
100
-
**Note:** Azure DevOps Server is not supported.
101
-
102
-
### Create and register a Microsoft Entra app
103
-
If you are an admin in your Azure portal, you can configure Entra apps to connect your tenant to Datadog.
104
-
105
-
1. Navigate to [Code Security setup][1].
106
-
2. In **Activate scanning for your repositories**, click **Manage Repositories**.
107
-
3. Select **CI Pipelines**.
108
-
4. Select the scan types you want to use.
109
-
5. Select **Azure DevOps** as your source code management provider.
110
-
6. If this is your first time connecting an Azure DevOps organization to Datadog, click **Connect Azure DevOps Account**.
111
-
7. When connecting a Microsoft Entra tenant for the first time you will need to go to your [Azure Portal][2] to register a new application. During this creation process, ensure the following:
112
-
1. You select **Accounts in this organizational directory only (Datadog, Inc. only - Single tenant)** as the account type.
113
-
2. Set the redirect URI to **Web** and paste the URI given to you in the instructions.
114
-
8. Copy the values for **Application (client) ID** and **Directory (tenant) ID** and paste them into Datadog.
115
-
9. In the Azure Portal for your app registration, navigate to **Manage > Certificates & secrets** and switch to **Client secrets**.
116
-
10. Click **New client secret** and create a secret with your desired description and expiration values.
117
-
11. Copy and paste the string in the **Value** column for your new secret, paste it into Datadog, and click **Create Configuration** to complete connecting your Entra tenant to Datadog.
118
-
13. Add one or more Azure DevOps organizations by pasting the organization slug into Datadog and then adding your Service Principal as a user by going to **Organization settings > Users > Add users**.
119
-
1. Your Service Principal will need the **Basic** access level and at least the **Project Contributor** security group.
120
-
14. Click **Submit Organization**.
121
-
122
-
### Configure project service hooks
123
-
124
-
To enable all Code Security features in Azure DevOps, you'll need to use a [Datadog API key][3] to configure service hooks for your projects.
125
-
126
-
First, set your environment variables (note: the Datadog UI will fill these values out for you):
127
-
```shell
128
-
export AZURE_DEVOPS_TOKEN="..."# Client Secret Value
129
-
export DD_API_KEY="..."# Datadog API Key
130
-
```
131
-
132
-
Then, replace the placeholders in the script below with your [Datadog Site][5] and Azure DevOps organization name to configure the necessary service hooks on your organization's projects:
Copy file name to clipboardExpand all lines: content/en/security/code_security/static_analysis/_index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ To get started, go to the [**Code Security** setup page][12] or see the [Setup d
38
38
## Integrate into the development lifecycle
39
39
40
40
### Source code management
41
-
{{< whatsnext desc="During code reviews, Datadog can automatically flag Static Code Analysis violations in pull requests by adding inline review comments on the relevant line(s) of code. When applicable, Datadog also provides suggested fixes that can be applied directly in the pull request." >}}
41
+
{{< whatsnext desc="During code reviews, Datadog can automatically flag Static Code Analysis violations in pull requests by adding inline review comments on the relevant line(s) of code. This is supported for GitHub, GitLab, and Azure DevOps repositories (cloud-hosted). When applicable, Datadog also provides suggested fixes that can be applied directly in the pull request." >}}
@@ -65,7 +65,7 @@ Click on a violation to open a side panel that contains information about the sc
65
65
66
66
The content of the violation is shown in tabs:
67
67
68
-
-**Details**: A description of the violation and the lines of code that caused it. To see the offending code snippet, configure the relevant source code integration for your provider (GitHub[4], GitLab[5]).
68
+
-**Details**: A description of the violation and the lines of code that caused it. To see the offending code snippet, configure the relevant source code integration for your provider ([GitHub][4], [GitLab][5], Azure[6]).
69
69
-**Remediation**: One or more code fixes that can resolve the violation, with options for remediation.
70
70
-**Event**: JSON metadata regarding the violation.
71
71
@@ -74,7 +74,7 @@ For a subset of SAST vulnerabilities, Bits AI can review the context of the find
74
74
75
75
For each finding, you can provide Bits AI with feedback on its assessment.
Copy file name to clipboardExpand all lines: content/en/security/code_security/static_analysis/setup/_index.md
+4-48Lines changed: 4 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,6 @@ algolia:
20
20
To set up Datadog SAST in-app, navigate to [**Security** > **Code Security**][1].
21
21
22
22
## Select where to run Static Code Analysis scans
23
-
24
23
### Scan with Datadog-hosted scanning
25
24
26
25
You can run Datadog Static Code Analysis (SAST) scans directly on Datadog infrastructure. Supported repository types include:
@@ -64,64 +63,21 @@ When installing a GitHub App, the following permissions are required to enable c
64
63
{{% /tab %}}
65
64
{{% tab "GitLab" %}}
66
65
67
-
See the [GitLab source code setup instructions][1] to connect GitLab to Datadog. Both GitLab.com and Self-Managed instances are supported.
66
+
See the [GitLab source code setup instructions][1] to connect GitLab repositories to Datadog. Both GitLab.com and Self-Managed instances are supported.
68
67
69
68
[1]: /integrations/gitlab-source-code/#setup
70
69
71
70
{{% /tab %}}
72
71
{{% tab "Azure DevOps" %}}
73
72
74
-
<divclass="alert alert-danger">
75
-
Repositories from Azure DevOps are supported in closed Preview. Your Azure DevOps organizations must be connected to a Microsoft Entra tenant. <ahref="https://www.datadoghq.com/product-preview/azure-devops-integration-code-security/">Join the Preview</a>.
76
-
</div>
77
-
78
-
Before you can begin installation, request access to the closed Preview using the form above. After being granted access, see the following instructions to complete the setup process.
79
-
80
-
**Note:** Azure DevOps Server is not supported.
81
-
82
-
### Create and register a Microsoft Entra app
83
-
If you are an admin in your Azure portal, you can configure Entra apps to connect your tenant to Datadog.
84
-
85
-
1. Go to [Code Security setup][1].
86
-
2. In **Activate scanning for your repositories**, click **Manage Repositories**.
87
-
3. Select **CI Pipelines**.
88
-
4. Select the scan types you want to use.
89
-
5. Select **Azure DevOps** as your source code management provider.
90
-
6. If this is your first time connecting an Azure DevOps organization to Datadog, click **Connect Azure DevOps Account**.
91
-
7. When connecting a Microsoft Entra tenant for the first time you will need to go to your [Azure Portal][2] to register a new application. During this creation process, ensure the following:
92
-
1. You select **Accounts in this organizational directory only (Datadog, Inc. only - Single tenant)** as the account type.
93
-
2. Set the redirect URI to **Web** and paste the URI given to you in the instructions.
94
-
8. Copy the values for **Application (client) ID** and **Directory (tenant) ID** and paste them into Datadog.
95
-
9. In the Azure Portal for your app registration, navigate to **Manage > Certificates & secrets** and switch to **Client secrets**.
96
-
10. Click **New client secret** and create a secret with the description and expiration values you want to use.
97
-
11. Copy and paste the string in the **Value** column for your new secret.
98
-
12. Paste the secret into Datadog and click **Create Configuration** to complete the connection between your Entra tenant and Datadog.
99
-
13. Add one or more Azure DevOps organizations by pasting the organization slug into Datadog and then adding your Service Principal as a user by going to **Organization settings > Users > Add users**.
100
-
1. Your Service Principal will need the **Basic** access level and at least the **Project Contributor** security group.
101
-
14. Click **Submit Organization**.
102
-
103
-
### Configure project service hooks
104
-
105
-
To enable all Code Security features in Azure DevOps, you'll need to use a [Datadog API key][3] to configure service hooks for your projects.
106
-
107
-
First, set your environment variables (note: the Datadog UI will fill these values out for you):
108
-
```shell
109
-
export AZURE_DEVOPS_TOKEN="..."# Client Secret Value
110
-
export DD_API_KEY="..."# Datadog API Key
111
-
```
112
-
113
-
Then, replace the placeholders in the script below with your [Datadog Site][5] and Azure DevOps organization name to configure the necessary service hooks on your organization's projects:
0 commit comments