Changes for page Dependency-Track

Summary

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

Details

Page properties

Content

...	...	@@ -6,7 +6,7 @@
6	6
7	7	= Introduction =
8	8
9		-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.
10	10
11	11	[[Vendor Page>>https://dependencytrack.org/]]
12	12
...	...	@@ -16,14 +16,9 @@
16	16
17	17	[[Impact Analysis>>https://docs.dependencytrack.org/usage/impact-analysis/]]
18	18
19		-[[Collection-projects>>https://docs.dependencytrack.org/usage/collection-projects/]]
20		-
21	21	= Accessing Dependency-Track =
22	22
23		-(% class="box warningmessage" %)
24		-(((
25		-Pilotkunden Preview ist
26		-)))
	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.
27	27
28	28	== Preconditions in DevOps portal to access Dependency-Track ==
29	29
...	...	@@ -33,16 +33,9 @@
33	33	(% class="box warningmessage" %)
34	34	(((
35	35	⚠ **Note**
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
	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.
37	37	)))
38	38
39		-
40		-
41		-
42		-
43		-
44		-
45		-
46	46	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.
47	47
48	48	== Via DevOps Portal ==
...	...	@@ -66,17 +66,19 @@
66	66	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.
67	67
68	68
	57	+= Projects =
69	69
70		-== Dependency-Track Jenkins Interaction ==
	59	+== Dependency-Track Jenkins Integration ==
71	71
72		-Nur sdcPipeline() wird unterstützt, nur maven (bisher), alles automatisch
	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.
73	73
74	74
75		-== Collection Project und Unterprojekte ==
	64	+== Collection Project ==
76	76
77		-TODO
	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.
78	78
79		-= Users, Projects and Roles =
	69	+= Users and Roles =
80	80
81	81	* Projects, users and their roles in projects are managed in the DevOps Portal, the corresponding functions in Dependency-Track are disabled (UI and API)
82	82
...	...	@@ -85,11 +85,11 @@
85	85
86	86	* 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 :
87	87	** Role mapping: (((
88		-|=Project Role in DevOps Portal|=Permissions in XWiki
89		-|Admin| POLICY_VIOLATION_ANALYSIS,''VIEW_POLICY_VIOLATION,''VIEW_PORTFOLIO,'VIEW_VULNERABILITY,''VULNERABILITY_ANALYSIS'
90		-|Master|(% colspan="1" %)Can view, comment, and edit pages, but cannot delete content
91		-|Developer|(% colspan="1" %)Similar to Master
92		-|Viewer|Read-only access. Can only view content, no edits or comments allowed
	78	+|=Project Role in DevOps Portal|=Permissions in  Dependency-Track
	79	+|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	80	+|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	81	+|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
	82	+|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
93	93
94	94	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/]]
95	95	)))