Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 43.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:29
Change comment: There is no comment for this version
To version 8.1
edited by Milad Afshar-Jahanshahi
on 2025/09/03 08:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,113 +1,115 @@
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, 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.
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 Deptrack:
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 toolchain, but for now it’s only offered in the Pilotkunden Preview. 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
22 -1. Dependency-Track must be added to the tool list of the project
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 toolchain, can be accessed via the DevOps Portal or directly through a URL.
23 += Introduction =
31 31  
32 -== Via DevOps Portal ==
25 +XWiki is an open-source platform for creating, managing, and collaborating on structured and unstructured content. It functions as a powerful wiki engine with advanced features like version control, rights management, scripting, and extensible applications. XWiki enables users to build knowledge bases, documentation platforms, or collaborative intranets, all within a customizable and web-based environment.
33 33  
34 -Go to the DevOps Portal Homepage and click on the link //Project// in the Project Vulnerabilities tile:
27 +[[Vendor Page>>https://www.xwiki.org/xwiki/bin/view/Main/WebHome]]
35 35  
36 -[[image:deptrack.png||alt="Deptrack -Tile" data-xwiki-image-style-border="true" height="211" width="459"]]
29 +There are several useful resources available to get started with XWiki:
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 or To resolve this issue, please log out and then log in again:
42 -\\[[image:login1.png||alt="Untitled2.png" height="250" width="600"]]
43 -)))
31 +[[XWiki Documentation>>https://www.xwiki.org/xwiki/bin/view/Documentation/]]
44 44  
45 -== Via Direct URL ==
33 +[[XWikiTutorials>>https://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/GettingStarted/]]
46 46  
47 -You can also access Dependency-Track directly using the following link format:
48 -[[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 += Accessing XWiki =
49 49  
50 -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.
37 +== Preconditions in DevOps portal to access XWiki ==
51 51  
39 +1. A XWiki license must be assigned to the user
40 +1. XWiki must be added to the tool list of the project
52 52  
53 -= Projects =
42 +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.
54 54  
55 -== Dependency-Track Jenkins Integration ==
44 +== Via DevOps Portal ==
56 56  
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.
46 +Go to the DevOps Portal Homepage and click on the link //Project Wiki// in the XWiki tile:
58 58  
48 +[[image:Untitled33.png||alt="XWiki-Tile" data-xwiki-image-style-border="true" height="211" width="459"]]
59 59  
60 -== Collection Project ==
50 +⚠ **Note**
51 +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:
52 +\\[[image:Untitled2.png||height="185" width="825"]]
61 61  
62 -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.
63 -For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
54 +== Via Direct URL ==
64 64  
65 -= Users and Roles =
56 +You can also access XWiki directly using the following link format:
57 +[[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.
66 66  
67 -* 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 +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.
68 68  
69 -(% class="box warningmessage" %)
70 -(((
71 71  ⚠ **Note**
72 -Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
73 -)))
62 +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.
63 +
74 74  
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 : 
65 += Users, Projects and Roles =
66 +
67 +* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in XWiki are disabled (UI and API)
68 +
69 +⚠ **Note**
70 +Projects in the DevOps portal are mapped to the corresponding subwikis in XWiki.
71 +
72 +* 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 : 
76 76  ** Role mapping: (((
77 -|=Project Role in DevOps Portal|=Permissions in Dependency-Track
78 -|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
79 -|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
80 -|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
81 -|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
74 +|=Project Role in DevOps Portal|=Permissions in XWiki
75 +|Admin|View, comment, edit, and delete pages
76 +|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
77 +|Developer|(% colspan="1" %)Similar to Master
78 +|Viewer|Read-only access. Can only view content, no edits or comments allowed
79 +
80 +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/]]
82 82  )))
83 83  
84 84  = Main Features =
85 85  
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.
85 +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.
87 87  
88 -== Auditing Basics ==
87 +== Collaborative Content Editing ==
89 89  
90 -(% class="wikigeneratedid" %)
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.
89 +* WYSIWYG and wiki syntax editors
90 +* Version control and history tracking
91 +* Inline and structured content editing
92 +* Commenting and annotations
92 92  
93 -(% class="wikigeneratedid" %)
94 -You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency‑Track documentation for deeper insights.
94 +== Advanced Page & Document Management ==
95 95  
96 -== Impact Analysis ==
96 +* Hierarchical page structure (nested pages)
97 +* Templates for creating structured documents
98 +* Tags, categories, and metadata support
99 +* File attachments and preview
97 97  
98 -(% class="wikigeneratedid" %)
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 +== Powerful Search and Navigation ==
100 100  
101 -(% class="wikigeneratedid" %)
102 -You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency‑Track documentation for deeper insights.
103 +* Full-text search (Solr-based)
104 +* Faceted search filters
105 +* Page index, breadcrumbs, and navigation panels
103 103  
104 -== Analysis States ==
107 +== Macros and Widgets ==
105 105  
106 -(% class="wikigeneratedid" %)
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 +* Built-in and custom macros (charts, galleries, diagrams)
110 +* Embedding of rich media (videos, iframes, etc.)
111 +* Markdown and LaTeX support
108 108  
109 -(% class="wikigeneratedid" %)
110 -You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency‑Track documentation for deeper insights.
111 111  
112 112  
113 113  
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
XWiki.XWikiComments[0]
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.miladafshar-jahanshahit-systemscom
Comment
... ... @@ -1,13 +1,0 @@
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,1 +1,0 @@
1 -2025-09-03 08:45:10.589
© 2018-2025 T-Systems International GmbH