Changes for page Dependency-Track

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Dependency-Track
	1	+Dependency Track

Content

...	...	@@ -1,3 +1,5 @@
	1	+STILL UNDER CONSTRUCTION
	2	+
1	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	2
3	3	{{toc/}}
...	...	@@ -4,29 +4,44 @@
4	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.
	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
11		-There are several useful resources available to get started with Dependency-Track:
	13	+There are several useful resources available to get started with Deptrack:
12	12
13	13	[[Dependency-Track Documentation>>https://docs.dependencytrack.org/]]
14	14
	17	+[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
	18	+
	19	+[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
	20	+
15	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.
	23	+(% class="box warningmessage" %)
	24	+(((
	25	+Pilotkunden Preview ist
	26	+)))
18	18
19	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.
	30	+1. A Dependency-Track license must be assigned to the user
	31	+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.
	36	+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
	39	+
	40	+
	41	+
	42	+
	43	+
	44	+
	45	+
	46	+
30	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.
31	31
32	32	== Via DevOps Portal ==
...	...	@@ -38,8 +38,7 @@
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 or To resolve this issue, please log out and then log in again.
42		-For some reason, you may need to click more than one option in OpenID or trigger the login section ([[https:~~/~~/deptrack-<customer~>.devops.t-systems.net/>>https://<customer>.devops.t-systems.net/xwiki/wiki/<pkey>/view]]login) to access the new session.
	58	+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:
43	43	\\[[image:login1.png||alt="Untitled2.png" height="250" width="600"]]
44	44	)))
45	45
...	...	@@ -51,64 +51,64 @@
51	51	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 =
55	55
56		-After creating a DevOps project in the portal, a Dependency-Track project is automatically created.
	71	+== Dependency-Track Jenkins Interaction ==
57	57
58		-== Dependency-Track Jenkins Integration ==
	73	+Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
59	59
60		-When using sdcPipeline(), Maven projects automatically generate a Software Bill of Materials (SBOM) and are pushed to Dependency-Track project. This process is fully automated through the provided pipeline library. Currently, this option is only available for Maven projects.
61	61
	76	+== Collection Project und Unterprojekte ==
62	62
63		-== Collection Project ==
	78	+TODO
64	64
65		-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.
66		-For more details, see the [[Collection Projects>>https://docs.dependencytrack.org/usage/collection-projects/]] section in the Dependency-Track documentation.
	80	+= Users, Projects and Roles =
67	67
68		-= Users and Roles =
69		-
70	70	* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
71	71
72		-(% class="box warningmessage" %)
73		-(((
74	74	⚠ **Note**
75		-Projects in the DevOps portal are mapped to the corresponding project in Dependency-Track.
76		-)))
	85	+Projects in the DevOps portal are mapped to the corresponding subwikis in Dependency-Track.
77	77
78		-* 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:
	87	+* 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 :
79	79	** Role mapping: (((
80		-|=Project Role in DevOps Portal|=Permissions in Dependency-Track
81		-|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
82		-|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
83		-|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
84		-|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
	89	+|=Project Role in DevOps Portal|=Permissions in XWiki
	90	+|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
	91	+|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
	92	+|Developer|(% colspan="1" %)Similar to Master
	93	+|Viewer|Read-only access. Can only view content, no edits or comments allowed
	94	+
	95	+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/]]
85	85	)))
86	86
87	87	= Main Features =
88	88
89		-== Auditing Basics ==
	100	+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.
90	90
91		-(% class="wikigeneratedid" %)
92		-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.
	102	+== Collaborative Content Editing ==
93	93
94		-(% class="wikigeneratedid" %)
95		-You can explore the [[Auditing Basics>>https://docs.dependencytrack.org/triage/auditing-basics/]] section in the Dependency-Track documentation for deeper insights.
	104	+* WYSIWYG and wiki syntax editors
	105	+* Version control and history tracking
	106	+* Inline and structured content editing
	107	+* Commenting and annotations
96	96
97		-== Impact Analysis ==
	109	+== Advanced Page & Document Management ==
98	98
99		-(% class="wikigeneratedid" %)
100		-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.
	111	+* Hierarchical page structure (nested pages)
	112	+* Templates for creating structured documents
	113	+* Tags, categories, and metadata support
	114	+* File attachments and preview
101	101
102		-(% class="wikigeneratedid" %)
103		-You can explore the [[Impact Analysis >>https://docs.dependencytrack.org/usage/impact-analysis/]]section in the Dependency-Track documentation for deeper insights.
	116	+== Powerful Search and Navigation ==
104	104
105		-== Analysis States ==
	118	+* Full-text search (Solr-based)
	119	+* Faceted search filters
	120	+* Page index, breadcrumbs, and navigation panels
106	106
107		-(% class="wikigeneratedid" %)
108		-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.
	122	+== Macros and Widgets ==
109	109
110		-(% class="wikigeneratedid" %)
111		-You can explore the [[Analysis States>>https://docs.dependencytrack.org/triage/analysis-states/]] section in the Dependency-Track documentation for deeper insights.
	124	+* Built-in and custom macros (charts, galleries, diagrams)
	125	+* Embedding of rich media (videos, iframes, etc.)
	126	+* Markdown and LaTeX support
112	112
113	113
	129	+
114	114