Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 53.3
edited by Boris Folgmann
on 2025/09/03 14:15
Change comment: There is no comment for this version
To version 12.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 08:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.borisfolgmannt-systemscom
1 +xwiki:XWiki.miladafshar-jahanshahit-systemscom
Content
... ... @@ -1,118 +1,119 @@
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"]]
1 +[[https:~~/~~/docs.dependencytrack.org/>>https://docs.dependencytrack.org/]]
2 2  
3 -{{toc/}}
3 +Optionales Tool: aktivieren als Project Admin für das Projekt, zuweisen von Lizenzen als Portal Admin an die entsprechenden User
4 4  
5 -= Introduction =
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
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 +Dashboard -> DepTrack Login Seite
8 8  
9 -[[Vendor Page>>https://dependencytrack.org/]]
9 +Pilotkunden Preview ist
10 10  
11 -There are several useful resources available to get started with Dependency-Track:
11 +Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
12 12  
13 -[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
13 +Collection Project und Unterprojekte
14 +\\~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~#~##
14 14  
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.
18 18  
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.
19 +{{toc/}}
23 23  
24 -(% class="box warningmessage" %)
25 -(((
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.
28 -)))
21 +[[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"]]
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.
23 += =
31 31  
32 -== Via DevOps Portal ==
25 += =
33 33  
34 -Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile:
27 += Introduction =
35 35  
36 -[[image:deptrack.png||alt="Deptrack -Tile" data-xwiki-image-style-border="true" height="211" width="459"]]
29 +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.
37 37  
38 -(% class="box warningmessage" %)
39 -(((
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"]]
44 -)))
31 +[[Vendor Page>>https://dependencytrack.org/]]
45 45  
46 -== Via Direct URL ==
33 +There are several useful resources available to get started with Deptrack:
47 47  
48 -You can also access Dependency-Track directly using the following link format:
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.
35 +[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
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.
37 +[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
52 52  
39 += Accessing XWiki =
53 53  
54 -= Projects =
41 +== Preconditions in DevOps portal to access XWiki ==
55 55  
56 -After creating a DevOps project in the portal, a Dependency-Track project is automatically created.
43 +1. A XWiki license must be assigned to the user
44 +1. XWiki must be added to the tool list of the project
57 57  
58 -== Dependency-Track Jenkins Integration ==
46 +After completing the preconditions, a project in XWiki, which is part of the DevOps-as-a-Service toolchain, can be accessed via the DevOps Portal or directly through a URL.
59 59  
60 -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.
48 +== Via DevOps Portal ==
61 61  
62 -[[image:1756907509490-678.png]]
50 +Go to the DevOps Portal Homepage and click on the link //Project Wiki// in the XWiki tile:
63 63  
64 -A new Dependency-Track sub project is automatically created on the fly. Currently, this option is only available for Maven projects.
52 +[[image:Untitled33.png||alt="XWiki-Tile" data-xwiki-image-style-border="true" height="211" width="459"]]
65 65  
54 +⚠ **Note**
55 +If you are still unable to access your project in XWiki, 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:
56 +\\[[image:Untitled2.png||height="185" width="825"]]
66 66  
67 -== Collection Project ==
58 +== Via Direct URL ==
68 68  
69 -In Dependency-Track, these Maven builds are organized under a **Collection Project**. Subprojects (for example, individual modules of a Maven project) are created as children of the DevOps portal project. This makes it easier to see aggregated metrics, such as vulnerabilities and license compliance, without having to open each subproject individually.
70 -For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
60 +You can also access XWiki directly using the following link format:
61 +[[https:~~/~~/<customer~>.devops.t-systems.net/xwiki/wiki/<pkey~>/view>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]] where <customer> is the id of your DevOps-as-a-Service instance and <pkey> is the project key in lowercase letters.
71 71  
72 -= Users and Roles =
63 +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.
73 73  
74 -* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
65 +⚠ **Note**
66 +Access to the main wiki at [[https:~~/~~/<customer~>.devops.t-systems.net/xwiki>>https://<customer>.devops.t-systems.net/xwiki]] is forbidden due to security restrictions and therefore this page cannot be viewed.
67 +
75 75  
76 -(% class="box warningmessage" %)
77 -(((
69 += Users, Projects and Roles =
70 +
71 +* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in XWiki are disabled (UI and API)
72 +
78 78  ⚠ **Note**
79 -Projects in the DevOps portal are mapped to the corresponding project in Dependency-Track.
80 -)))
74 +Projects in the DevOps portal are mapped to the corresponding subwikis in XWiki.
81 81  
82 -* 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: 
76 +* When XWiki 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 : 
83 83  ** Role mapping: (((
84 -|=Project Role in DevOps Portal|=Permissions in Dependency-Track
85 -|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
86 -|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
87 -|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
88 -|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
78 +|=Project Role in DevOps Portal|=Permissions in XWiki
79 +|Admin|View, comment, edit, and delete pages
80 +|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
81 +|Developer|(% colspan="1" %)Similar to Master
82 +|Viewer|Read-only access. Can only view content, no edits or comments allowed
83 +
84 +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/]]
89 89  )))
90 90  
91 91  = Main Features =
92 92  
93 -== Auditing Basics ==
89 +Inside DevOps-as-a-Service, XWiki is mainly used for writing specifications and documentations. See below for a list of the main features of XWiki.
94 94  
95 -(% class="wikigeneratedid" %)
96 -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 +== Collaborative Content Editing ==
97 97  
98 -(% class="wikigeneratedid" %)
99 -You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency-Track documentation for deeper insights.
93 +* WYSIWYG and wiki syntax editors
94 +* Version control and history tracking
95 +* Inline and structured content editing
96 +* Commenting and annotations
100 100  
101 -== Impact Analysis ==
98 +== Advanced Page & Document Management ==
102 102  
103 -(% class="wikigeneratedid" %)
104 -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.
100 +* Hierarchical page structure (nested pages)
101 +* Templates for creating structured documents
102 +* Tags, categories, and metadata support
103 +* File attachments and preview
105 105  
106 -(% class="wikigeneratedid" %)
107 -You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency-Track documentation for deeper insights.
105 +== Powerful Search and Navigation ==
108 108  
109 -== Analysis States ==
107 +* Full-text search (Solr-based)
108 +* Faceted search filters
109 +* Page index, breadcrumbs, and navigation panels
110 110  
111 -(% class="wikigeneratedid" %)
112 -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.
111 +== Macros and Widgets ==
113 113  
114 -(% class="wikigeneratedid" %)
115 -You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency-Track documentation for deeper insights.
113 +* Built-in and custom macros (charts, galleries, diagrams)
114 +* Embedding of rich media (videos, iframes, etc.)
115 +* Markdown and LaTeX support
116 116  
117 117  
118 +
118 118  
1756907509490-678.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.borisfolgmannt-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -5.4 KB
Content
deptrack.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.miladafshar-jahanshahit-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -14.2 KB
Content
login1.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.miladafshar-jahanshahit-systemscom
Size
... ... @@ -1,1 +1,0 @@
1 -25.5 KB
Content
© 2018-2025 T-Systems International GmbH