Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 51.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 14:07
Change comment: There is no comment for this version
To version 44.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Dependency-Track
1 +Dependency Track
Content
... ... @@ -4,22 +4,22 @@
4 4  
5 5  = Introduction =
6 6  
7 -Dependency-Track is an open-source Software Composition Analysis (SCA) tool that helps organizations manage and secure their software supply chain. It automatically generates and maintains a Software Bill of Materials (SBOM) for projects and the continuously monitors dependencies for known vulnerabilities. In addition, it tracks license compliance of open-source components, giving teams greater visibility and control. By integrating seamlessly into DevOps and CI/CD pipelines, Dependency-Track makes it easier to embed security throughout the development lifecycle.
7 +Dependency Track is an open-source Software Composition Analysis (SCA) tool that helps organizations manage and secure their software supply chain. It automatically generates and maintains a Software Bill of Materials (SBOM) for projects, continuously monitoring dependencies for known vulnerabilities. In addition, it tracks license compliance of open-source components, giving teams greater visibility and control. By integrating seamlessly into DevOps and CI/CD pipelines, Dependency-Track makes it easier to embed security throughout the development lifecycle.
8 8  
9 9  [[Vendor Page>>https://dependencytrack.org/]]
10 10  
11 -There are several useful resources available to get started with Dependency-Track:
11 +There are several useful resources available to get started with Dependency Track:
12 12  
13 13  [[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
14 14  
15 15  = Accessing Dependency-Track =
16 16  
17 -Dependency-Track is integrated into the DevOps-as-a-Service tool chain, but for now it is only available to pilot customers. To get started, a few prerequisites need to be in place.
17 +Dependency-Track is integrated into the DevOps-as-a-Service toolchain, but for now it is only available to pilot customers. To get started, a few prerequisites need to be in place.
18 18  
19 19  == Preconditions in DevOps portal to access Dependency-Track ==
20 20  
21 -1. A Dependency-Track license must be assigned to the user by a Portal Admin.
22 -1. Deptrack must be added to the tool list of the project by a Project Admin or Portal Admin.
21 +1. A Dependency-Track license must be assigned to the user
22 +1. Dependency-Track must be added to the tool list of the project
23 23  
24 24  (% class="box warningmessage" %)
25 25  (((
... ... @@ -38,8 +38,7 @@
38 38  (% class="box warningmessage" %)
39 39  (((
40 40  ⚠ **Note**
41 -If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions or To resolve this issue, please log out and then log in again. 
42 -For some reason, you may need to click more than one option in OpenID or trigger the login section ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session.
41 +If you are still unable to access your project in Dependency-Track, it may be because you are logged in with an old session that still uses outdated permissions or To resolve this issue, please log out and then log in again:
43 43  \\[[image:login1.png||alt="Untitled2.png" height="250" width="600"]]
44 44  )))
45 45  
... ... @@ -53,11 +53,9 @@
53 53  
54 54  = Projects =
55 55  
56 -After creating a DevOps project in the portal, a Dependency-Track project is automatically created.
57 -
58 58  == Dependency-Track Jenkins Integration ==
59 59  
60 -When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency-Track project. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects.
57 +When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency-Track. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects.
61 61  
62 62  
63 63  == Collection Project ==
... ... @@ -72,10 +72,10 @@
72 72  (% class="box warningmessage" %)
73 73  (((
74 74  ⚠ **Note**
75 -Projects in the DevOps portal are mapped to the corresponding project in Dependency-Track.
72 +Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
76 76  )))
77 77  
78 -* When Dependency-Track is added as a tool to an existing or new project, a corresponding Dependency-Track project is automatically created. Users assigned to the project in the DevOps Portal are then added to it with the roles defined in the configuration: 
75 +* When Dependency-Track is added as a tool to an existing or new project, a corresponding Dependency Track project is automatically created. Users assigned to the project in the DevOps Portal are then added to it with the roles defined in the configuration : 
79 79  ** Role mapping: (((
80 80  |=Project Role in DevOps Portal|=Permissions in Dependency-Track
81 81  |Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
... ... @@ -86,29 +86,31 @@
86 86  
87 87  = Main Features =
88 88  
86 +Inside DevOps-as-a-Service, deptrack is mainly used for writing specifications and documentations. See below for a list of the main features of XWiki.
87 +
89 89  == Auditing Basics ==
90 90  
91 91  (% class="wikigeneratedid" %)
92 -Dependency-Track offers a robust auditing workflow: you can triage findings on individual projects, add comments, and record analysis decisions. The platform logs a complete audit trail for each action. Users with the VULNERABILITY_ANALYSIS permission can perform these audits, and audit histories are visible to anyone with the VIEW_VULNERABILITY permission.
91 +Dependency‑Track offers a robust auditing workflow: you can triage findings on individual projects, add comments, and record analysis decisions. The platform logs a complete audit trail for each action. Users with the VULNERABILITY_ANALYSIS permission can perform these audits, and audit histories are visible to anyone with the VIEW_VULNERABILITY permission.
93 93  
94 94  (% class="wikigeneratedid" %)
95 -You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency-Track documentation for deeper insights.
94 +You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency‑Track documentation for deeper insights.
96 96  
97 97  == Impact Analysis ==
98 98  
99 99  (% class="wikigeneratedid" %)
100 -Dependency-Track enables organizations to assess how a vulnerability affects their environment. If a vulnerability is published in a supported datasource (e.g., NVD, GitHub Advisories, OSS Index, VulnDB), the platform dynamically identifies all affected projects. This allows you to answer: "What is affected?" and "Where am I affected?" at a glance.
99 +Dependency‑Track enables organizations to assess how a vulnerability affects their environment. If a vulnerability is published in a supported datasource (e.g., NVD, GitHub Advisories, OSS Index, VulnDB), the platform dynamically identifies all affected projects. This allows you to answer: "What is affected?" and "Where am I affected?" at a glance.
101 101  
102 102  (% class="wikigeneratedid" %)
103 -You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency-Track documentation for deeper insights.
102 +You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency‑Track documentation for deeper insights.
104 104  
105 105  == Analysis States ==
106 106  
107 107  (% class="wikigeneratedid" %)
108 -Dependency-Track tracks the status of findings through their lifecycle via "analysis states". These help teams understand whether findings are new, under review, suppressed, or resolved. You can reference the Analysis States section in the documentation for full details on available statuses and workflows.
107 +Dependency‑Track tracks the status of findings through their lifecycle via "analysis states". These help teams understand whether findings are new, under review, suppressed, or resolved. You can reference the Analysis States section in the documentation for full details on available statuses and workflows.
109 109  
110 110  (% class="wikigeneratedid" %)
111 -You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency-Track documentation for deeper insights.
110 +You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency‑Track documentation for deeper insights.
112 112  
113 113  
114 114  
© 2018-2025 T-Systems International GmbH