Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 23.2
edited by Milad Afshar-Jahanshahi
on 2025/09/03 08:51
Change comment: There is no comment for this version
To version 33.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 12:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,12 @@
1 -{{toc/}}
1 +STILL UNDER CONSTRUCTION
2 2  
3 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 4  
5 +{{toc/}}
6 +
5 5  = Introduction =
6 6  
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.
9 +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  
... ... @@ -18,11 +18,29 @@
18 18  
19 19  = Accessing Dependency-Track =
20 20  
23 +Dependency-Track is integrated into the DOAAS toolchain, but for now it’s only offered in the Pilotkunden Preview. To get started, a few prerequisites need to be in place.
24 +
21 21  == Preconditions in DevOps portal to access Dependency-Track ==
22 22  
23 23  1. A Dependency-Track license must be assigned to the user
24 24  1. Dependency-Track must be added to the tool list of the project
25 25  
30 +(% class="box warningmessage" %)
31 +(((
32 +⚠ **Note**
33 +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.
34 +)))
35 +
36 +
37 +
38 +
39 +
40 +
41 +
42 +
43 +
44 +
45 +
26 26  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.
27 27  
28 28  == Via DevOps Portal ==
... ... @@ -45,10 +45,17 @@
45 45  
46 46  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.
47 47  
48 -⚠ **Note**
49 -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.
50 -
51 51  
69 +
70 +== Dependency-Track Jenkins Interaction ==
71 +
72 +Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
73 +
74 +
75 +== Collection Project und Unterprojekte ==
76 +
77 +TODO
78 +
52 52  = Users, Projects and Roles =
53 53  
54 54  * Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
... ... @@ -59,7 +59,7 @@
59 59  * 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 : 
60 60  ** Role mapping: (((
61 61  |=Project Role in DevOps Portal|=Permissions in XWiki
62 -|Admin|View, comment, edit, and delete pages
89 +|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
63 63  |Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
64 64  |Developer|(% colspan="1" %)Similar to Master
65 65  |Viewer|Read-only access. Can only view content, no edits or comments allowed
... ... @@ -69,7 +69,7 @@
69 69  
70 70  = Main Features =
71 71  
72 -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.
99 +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.
73 73  
74 74  == Collaborative Content Editing ==
75 75  
XWiki.XWikiComments[0]
Comment
... ... @@ -2,9 +2,9 @@
2 2  
3 3  Optionales Tool: aktivieren als Project Admin für das Projekt, zuweisen von Lizenzen als Portal Admin an die entsprechenden User
4 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
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 6  
7 -Dashboard -> DepTrack Login Seite
7 +Dashboard -> DepTrack Login Seite  ~-~-> DOne
8 8  
9 9  Pilotkunden Preview ist
10 10  
© 2018-2025 T-Systems International GmbH