Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 56.1
edited by Boris Folgmann
on 2025/09/03 14:28
Change comment: There is no comment for this version
To version 25.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 09:14
Change comment: Edited comment

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.borisfolgmannt-systemscom
1 +xwiki:XWiki.miladafshar-jahanshahit-systemscom
Content
... ... @@ -1,34 +3,38 @@
1 -[[image:logo-dependency-track.YzQAjtqS_Z2pMQkR.webp||alt="Grafana Icon Logo PNG vector in SVG, PDF, AI, CDR format" data-xwiki-image-style-alignment="end" height="52" width="190"]]
2 -
3 3  {{toc/}}
4 4  
3 +[[image:logo-dependency-track.YzQAjtqS_Z2pMQkR.webp||alt="Grafana Icon Logo PNG vector in SVG, PDF, AI, CDR format" data-xwiki-image-style-alignment="end" height="52" width="190"]]
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. It creates and manages a software bill of materials (SBOM) for projects. The tool continuously checks dependencies for known vulnerabilities. It also tracks license compliance of open-source components. Teams gain visibility and control over their software supply chain. Helps integrate security into DevOps/CI-CD pipelines efficiently.
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 Deptrack:
12 12  
13 13  [[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
14 14  
15 -= Accessing Dependency-Track =
15 +[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
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 +[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
18 18  
19 += Accessing Dependency-Track =
20 +
19 19  == Preconditions in DevOps portal to access Dependency-Track ==
20 20  
21 -1. A DepTrack 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.
23 +1. A Dependency-Track license must be assigned to the user
24 +1. Dependency-Track must be added to the tool list of the project
23 23  
24 24  (% class="box warningmessage" %)
25 25  (((
26 26  ⚠ **Note**
27 -Unlike other tools, login is only possible if the user has a valid license and is assigned a role in at least one Dependency-Track project.
29 +Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat
28 28  )))
29 29  
30 -After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service tool chain, can be accessed via the DevOps Portal or directly through the Depdency-Track URL.
31 31  
33 +
34 +After completing the preconditions, a project in Dependency-Track, which is part of the DevOps-as-a-Service toolchain, can be accessed via the DevOps Portal or directly through a URL.
35 +
32 32  == Via DevOps Portal ==
33 33  
34 34  Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile:
... ... @@ -38,9 +38,8 @@
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. To resolve this issue, please log out and then log in again. 
42 -For some reason, you may need to click more than one time on the OpenID button or go to the login page ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session.
43 -\\[[image:login1.png||alt="Untitled2.png" data-xwiki-image-style-border="true" height="297" width="650"]]
45 +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:
46 +\\[[image:login1.png||alt="Untitled2.png" height="250" width="600"]]
44 44  )))
45 45  
46 46  == Via Direct URL ==
... ... @@ -48,68 +48,57 @@
48 48  You can also access Dependency-Track directly using the following link format:
49 49  [[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/projects>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]] where <customer> is the id of your DevOps-as-a-Service instance.
50 50  
51 -If you are not already logged in to another tool in the tool chain or the DevOps portal, then you have to log in using your configured SSO credentials.
54 +If you are not already logged in to another tool in the toolchain or the DevOps portal, then you have to login using your configured SSO credentials.
52 52  
53 53  
54 -= Projects =
57 += Users, Projects and Roles =
55 55  
56 -After creating a DevOps project in the portal, a Dependency-Track project is automatically created. The type of the new project is** Collection Project**. Subprojects which keep the real SBOM scan results are later created as children of this collection project. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
59 +* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
57 57  
58 -For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
61 +⚠ **Note**
62 +Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
59 59  
60 -== Integration with Jenkins ==
64 +* When Dependency-Track is added as a tool to an existing or new project, a corresponding subwiki is automatically created. Users assigned to the project in the DevOps Portal are then added to the subwiki with the roles defined in the configuration : 
65 +** Role mapping: (((
66 +|=Project Role in DevOps Portal|=Permissions in XWiki
67 +|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
68 +|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
69 +|Developer|(% colspan="1" %)Similar to Master
70 +|Viewer|Read-only access. Can only view content, no edits or comments allowed
61 61  
62 -The [[Jenkins Shared Library>>url:https://prd.sdc.t-systems.net/xwiki/wiki/devopsaas/view/Jenkins/Jenkins%20Shared%20Library/]] will automatically create SBOM (Software Bill of Materials) files for maven projects and upload them to Dependency-Track.
63 -
64 -[[image:1756907509490-678.png]]
65 -
66 -A new Dependency-Track sub project is automatically created on the fly.
67 -
68 -Currently, this option is only available for Maven projects.
69 -
70 -
71 -= Users and Roles =
72 -
73 -* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API).
74 -
75 -(% class="box warningmessage" %)
76 -(((
77 -
72 +A detailed description of the XWiki role model can be found [[here>>https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Access%20Rights/Permission%20types/]]
78 78  )))
79 79  
80 -* Users assigned to a project in the DevOps Portal are automatically added to the matching Dependency-Track projects with the roles as shown below:(((
81 -|=Project Role in DevOps Portal|=Permissions in Dependency-Track
82 -|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
83 -|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
84 -|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
85 -|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
86 -)))
87 -
88 88  = Main Features =
89 89  
90 -== Auditing Basics ==
77 +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.
91 91  
92 -(% class="wikigeneratedid" %)
93 -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.
79 +== Collaborative Content Editing ==
94 94  
95 -(% class="wikigeneratedid" %)
96 -You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency-Track documentation for deeper insights.
81 +* WYSIWYG and wiki syntax editors
82 +* Version control and history tracking
83 +* Inline and structured content editing
84 +* Commenting and annotations
97 97  
98 -== Impact Analysis ==
86 +== Advanced Page & Document Management ==
99 99  
100 -(% class="wikigeneratedid" %)
101 -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.
88 +* Hierarchical page structure (nested pages)
89 +* Templates for creating structured documents
90 +* Tags, categories, and metadata support
91 +* File attachments and preview
102 102  
103 -(% class="wikigeneratedid" %)
104 -You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency-Track documentation for deeper insights.
93 +== Powerful Search and Navigation ==
105 105  
106 -== Analysis States ==
95 +* Full-text search (Solr-based)
96 +* Faceted search filters
97 +* Page index, breadcrumbs, and navigation panels
107 107  
108 -(% class="wikigeneratedid" %)
109 -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.
99 +== Macros and Widgets ==
110 110  
111 -(% class="wikigeneratedid" %)
112 -You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency-Track documentation for deeper insights.
101 +* Built-in and custom macros (charts, galleries, diagrams)
102 +* Embedding of rich media (videos, iframes, etc.)
103 +* Markdown and LaTeX support
113 113  
114 114  
106 +
115 115  
1756907509490-678.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.borisfolgmannt-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -5.4 KB
Content
XWiki.XWikiComments[0]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.miladafshar-jahanshahit-systemscom
Comment
... ... @@ -1,0 +1,13 @@
1 +[[https:~~/~~/docs.dependencytrack.org/>>url:https://docs.dependencytrack.org/]]
2 +
3 +Optionales Tool: aktivieren als Project Admin für das Projekt, zuweisen von Lizenzen als Portal Admin an die entsprechenden User
4 +
5 +Im Gegensatz zu anderen Tools ist ein Login nur dann möglich, wenn der User eine Lizenz hat und in mindestens einem DepTrack Projekt eine Rolle hat  ~-~-> Done
6 +
7 +Dashboard -> DepTrack Login Seite  ~-~-> DOne
8 +
9 +Pilotkunden Preview ist
10 +
11 +Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
12 +
13 +Collection Project und Unterprojekte
Date
... ... @@ -1,0 +1,1 @@
1 +2025-09-03 08:45:10.589
© 2018-2025 T-Systems International GmbH