Skip to Content

Changes for page Dependency-Track

Last modified by Milad Afshar-Jahanshahi on 2025/09/03 14:31
From version 23.3
edited by Milad Afshar-Jahanshahi
on 2025/09/03 09:12
Change comment: There is no comment for this version
To version 40.3
edited by Milad Afshar-Jahanshahi
on 2025/09/03 13:21
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  
... ... @@ -14,15 +14,21 @@
14 14  
15 15  [[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
16 16  
17 -[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
18 -
19 19  = Accessing Dependency-Track =
20 20  
21 +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.
22 +
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  
28 +(% class="box warningmessage" %)
29 +(((
30 +⚠ **Note**
31 +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.
32 +)))
33 +
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 ==
... ... @@ -46,54 +46,55 @@
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 48  
49 -= Users, Projects and Roles =
57 += Projects =
50 50  
51 -* 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 +== Dependency-Track Jenkins Integration ==
52 52  
53 -⚠ **Note**
54 -Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
61 +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.
55 55  
56 -* 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 : 
57 -** Role mapping: (((
58 -|=Project Role in DevOps Portal|=Permissions in XWiki
59 -|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
60 -|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
61 -|Developer|(% colspan="1" %)Similar to Master
62 -|Viewer|Read-only access. Can only view content, no edits or comments allowed
63 63  
64 -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/]]
65 -)))
64 +== Collection Project ==
66 66  
67 -= Main Features =
66 +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.
67 +For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
68 68  
69 -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.
69 += Users and Roles =
70 70  
71 -== Collaborative Content Editing ==
71 +* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
72 72  
73 -* WYSIWYG and wiki syntax editors
74 -* Version control and history tracking
75 -* Inline and structured content editing
76 -* Commenting and annotations
73 +(% class="box warningmessage" %)
74 +(((
75 +⚠ **Note**
76 +Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
77 +)))
77 77  
78 -== Advanced Page & Document Management ==
79 +* 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 : 
80 +** Role mapping: (((
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 +)))
79 79  
80 -* Hierarchical page structure (nested pages)
81 -* Templates for creating structured documents
82 -* Tags, categories, and metadata support
83 -* File attachments and preview
88 += Main Features =
84 84  
85 -== Powerful Search and Navigation ==
90 +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.
86 86  
87 -* Full-text search (Solr-based)
88 -* Faceted search filters
89 -* Page index, breadcrumbs, and navigation panels
92 +(% class="wikigeneratedid" id="HCollaborativeContentEditing" %)
93 +Auditing Basics
90 90  
91 -== Macros and Widgets ==
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. docs.dependencytrack.org +1
92 92  
93 -* Built-in and custom macros (charts, galleries, diagrams)
94 -* Embedding of rich media (videos, iframes, etc.)
95 -* Markdown and LaTeX support
98 +(% class="wikigeneratedid" %)
99 +Impact Analysis
96 96  
101 +(% class="wikigeneratedid" %)
102 +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. docs.dependencytrack.org
97 97  
104 +(% class="wikigeneratedid" %)
105 +3. Analysis States 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. docs.dependencytrack.org +1
98 98  
107 +
99 99  
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